[sane-devel] OS/2 specific patch for sane-backends/backend/dll.c

2004-06-02 Thread 
On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote:

...
>> What do you think? Could this script be added to
>> sane-backends/
>> or 
>> sane-backends/backend/
>
>What about tools/? There is already a script called by the Makefile.
>You could call it from backend/Makefile if the install target is run
>on OS/2.

tools/ is fine.

>I'd change the license to just GPL. E.g. at the moment, nobody is
>allowed to use your script (only copy, distribute and modify it) :-)

Change it to what you think is best. I am not shure if a license is
necessary at all for such a short script, but I'm not a lawyer and
don't know if there are sane-project-specific rules for these things.

Ciao
Franz

[sane-devel] Fi-4120c duplex color

2004-06-02 Thread Oliver Schirrmeister 
Am Freitag 30 April 2004 16:44 schrieb Krzysztof Cieniuch:
> Hi,
>
> Is it possible to scan duplex in color with this scanner ?
> I've tried scanadf --rif=yes --duplex=both --resoluton=72 -d
> fujitsu:/dev/sg0
> but i've ended up with one properly scaned image and one
> totally black. Is this feature missing in fujitsu backend ?
> In what time if ever will be this functionality available in
> fujitsu backend ?
>

That was a bug in the fujitsu backend. I've fixed that, checkout the
latest version.

Oliver

[sane-devel] Fujitsu papersize problems, sane-backends-1.0.14

2004-06-02 Thread Lee Howard 
Hello.

I have a Fujitsu M4097Ddm and am using sane-frontends-1.0.12 and 
sane-backends-1.0.14.

I am having trouble when using the --papersize options other than 
A4/Letter.

If I do:

scanimage --source ADF --papersize Autodetect

or:

scanadf --source ADF --papersize Autodetect

I get:

sane_start: Invalid argument

If I use "--papersize Legal" then the scanning is performed, but the 
image files are only letter/A4 size; the image is truncated at the 
bottom.

I haven't tried any other options, but I would guess that all 
--papersize options other than letter/A4 will not result as expected.

Is this something that is a known bug?  Is it fixed in a development 
version?

I'd be happy to provide verbose debugging information if it will help.

Thanks.

Lee.