Julien BLACHE <[EMAIL PROTECTED]> writes: > Olaf Meeuwissen <[EMAIL PROTECTED]> wrote: > > Hi, > >> Hi Julien. Sorry for not replying earlier. > > No problem :) > >>> Olaf, can you take a look at the patches in the BTS and comment? >> >> I'll do my best but I'm swamped at the moment. I don't think I'll be >> able to take a look before Thursday :-( > > Fine with me :) > >>> I'm all for applying the patches if they're OK with you; also can they >>> be ported over to the epson/epson2 backends?
I'm definitely not in favour of applying the epson4490-fixup.patch. As for the 16bit patches from Carl, I already mentioned[1] that I'd look at that. [1] http://lists.alioth.debian.org/pipermail/sane-devel/2008-June/022157.html Here is the scoop on the epson4490-fixup.patch: | - Added 4800 dpi resolution which is suppported but not reported by the | scanner. This will be automatically fixed when we release a new version of the plugin to work with iscan-2.11.0 and later. | - Re-enabled 400 dpi resolution. There was no comment as to why it had | been disabled in the first place but it works just fine on my 4490 | scanner... If something catches fire I'll be sure to revert this fix. That resolution was disabled to get ADF to work. Sorry for not adding a comment. | - Fixed an off by one error in the original filter_resolution() function. The array has the size in its first element (see the last line of the patch), as per requirement for SANE_CONSTRAINT_WORD_LIST. Instead of fixing an off by one error, you introduce one. | - Enabled resolutions <300 dpi. This makes for _much_ faster preview | scanning since 100 dpi is now available. These had been disabled because | they are not supported when the TPU/APD is in use. Worked around the | TPU/APD incompatibility with the lower resolutions by adding a hidden | OPT_FORCE_LIMIT_RESOLUTION option which updates the resolution list when | the TPU/APD is selected. (This is the bulk of the patch.) This will also be automatically fixed with a new version of the plugin for iscan-2.11.0 and later. So the burning question that will be on everyone's mind now is: WHEN will this new plugin be released? Honestly, I don't know (it not my call) but given how things are at the moment it will not be anytime real soon now. I hope we can get an updated version out sometime in autumn. >> I guess we should discuss the future of all these backends for EPSON >> ESC/I devices. Three backends for the same device is confusing to the >> user (and a PITA to maintain). > > TTBOMK we'll probably get rid of epson in favour of epson2 "soon", > then it'll be epson2 vs. epkowa and ... at that point that's Epson's > call to merge back epkowa in epson2. ACK. Hope this helps, -- Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
