| 1 |
On Wednesday, November 30, 2016 10:43:13 AM J. Roeleveld wrote: |
| 2 |
> On Tuesday, November 29, 2016 11:18:36 PM karl@××××××××.se wrote: |
| 3 |
> > Michael Mol: |
| 4 |
> > ... |
| 5 |
> > |
| 6 |
> > > xsane would have let me do it during the scan process if I'd thought of |
| 7 |
> > > it |
| 8 |
> > > then, but the scans are done, drives aren't there any more. Something |
| 9 |
> > |
| 10 |
> > ... |
| 11 |
> > |
| 12 |
> > If xsane solves your need why don't you just print your scans so xsane |
| 13 |
> > can do its job ? |
| 14 |
> |
| 15 |
> There has to be a way to do this without killing an entire forest... |
| 16 |
|
| 17 |
And big chunks of ink cartridges. The scans stretched the contrast so I can |
| 18 |
clearly read the drive labels through the translucent anti-static bags, which |
| 19 |
means a huge chunk of the image (what's outside the labels) is pure black. |
| 20 |
|
| 21 |
Which I could get around by spending fifteen minutes munging things in the Gimp |
| 22 |
before printing, but at that point, I may as well just transcribe things |
| 23 |
manually at that point. |
| 24 |
|
| 25 |
Looking for something reasonably simple to improve the general workflow. I'd |
| 26 |
have hoped something would have already been available on Linux; it'd be easy |
| 27 |
enough to copy the scans to my phone and feed them through Google Goggles for |
| 28 |
the desired output, but then I'm deliberately filtering company data through an |
| 29 |
outside entity. |
| 30 |
|
| 31 |
-- |
| 32 |
:wq |
Archives