[sane-devel] ICC support for SANE

2009-05-29 Thread Olaf Meeuwissen
Julien BLACHE jb at jblache.org writes: [snip] There is no standard for scanner settings. Each model has different settings available, with the most common settings somewhat standardised and dubbed well-known options in SANE. That's all you've got to work with. And for all the

[sane-devel] ICC support for SANE

2009-05-29 Thread Julien BLACHE
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote: Hi, The (external) epkowa backend applies a colour correction profile to the external is the key ;) - machines that send data with samples 8 bits The epson, epson2 and epkowa backends can do 16 bit sample scans. Moreover, the SANE spec

[sane-devel] ICC support for SANE

2009-05-29 Thread Olaf Meeuwissen
Julien BLACHE jb at jblache.org writes: Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote: Hi, The (external) epkowa backend applies a colour correction profile to the external is the key ;) Thought you'd say that :-P But note that the epson2 backend may do the same in the next release.

[sane-devel] ICC support for SANE

2009-05-29 Thread Emmanuel Fust
Message du 29/05/09 09:56 De : Julien BLACHE A : sane-devel at lists.alioth.debian.org Copie ? : Objet : Re: [sane-devel] ICC support for SANE Olaf Meeuwissen wrote: Hi, The (external) epkowa backend applies a colour correction profile to the external is the key ;) - machines

[sane-devel] ICC support for SANE

2009-05-29 Thread Julien BLACHE
Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote: Hi, The (external) epkowa backend applies a colour correction profile to the external is the key ;) Thought you'd say that :-P He he. But note that the epson2 backend may do the same in the next release. Seriously, my point is that

[sane-devel] Epson PX700W/Artisan 700 network scanning

2009-05-29 Thread Dominik Wnek
part -- A non-text attachment was scrubbed... Name: scanning_sane1.0.21cvs.log Type: text/x-log Size: 41768 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090529/7c602947/attachment-0002.bin -- next part -- A non

[sane-devel] Epson PX700W/Artisan 700 network scanning

2009-05-29 Thread Alessandro Zummo
On Fri, 29 May 2009 12:18:05 +0200 Dominik Wnek dominalien at netscape.net wrote: I am attaching logs from sane 1.0.19, which is included in Ubuntu 9.04 and from sane 1.0.21cvs (snapshot from 2009.05.27). Both are from trying to scan over the network. Please let me know what else I can do to

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-05-29 Thread Alessandro Zummo
Hi, I have a couple of issues on the epson2 driver which can easily be resolved by using the warming up return code. Maybe we can have a new branch on the git repo as suggested by Alesh ? -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-05-29 Thread Alessandro Zummo
On Fri, 29 May 2009 15:04:53 +0200 Alessandro Zummo azummo-lists at towertech.it wrote: Hi, I have a couple of issues on the epson2 driver which can easily be resolved by using the warming up return code. Maybe we can have a new branch on the git repo as suggested by Alesh ? btw we

[sane-devel] Problem with HP ScanJet 4p and SCSI

2009-05-29 Thread David Brant
Hi Dieter I typed (and got) the following -- david at david-desktop:~$ scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-05-29 Thread m. allan noah
they are not enums in current git tree. allan On Fri, May 29, 2009 at 9:29 AM, Alessandro Zummo azummo-lists at towertech.it wrote: On Fri, 29 May 2009 15:04:53 +0200 Alessandro Zummo azummo-lists at towertech.it wrote: ?Hi, I have a couple of issues on the epson2 driver ?which can easily

[sane-devel] regarding SANE_STATUS_WARMING_UP

2009-05-29 Thread m. allan noah
well, lets re-open the discussion of the return codes. Julien had some reservations about this technique. I dont have a problem with it, as long as we formalize it in the standard exactly which status codes require retry. I also would like to add a generic 'SANE_STATUS_RETRY' for those cases where