[sane-devel] Cannot run xsane 0.84 and 0.85 with the current CVS backends 1.0.7

2002-04-19 Thread Christian Fughe
Hi, On Thu, 18 Apr 2002, Henning Meier-Geinitz wrote: > I have just committed a fix to CVS, so please test it. I testet it. That's it! Xsane is 100% operative now, at least for me. Thank you for the fast fix, Christian Fughe

[sane-devel] Cannot run xsane 0.84 and 0.85 with the current CVS backends 1.0.7

2002-04-18 Thread Henning Meier-Geinitz
[I'm forwarding parts of a private mail sent to me with consent of the author:] On Thu, Apr 18, 2002 at 03:28:00AM +0200, Christian Fughe wrote: > > That means, with the non-CVS version of sane it worked with xsane? > > Yes! So it's a problem of the client-side, probably the net backend. > > By

[sane-devel] Cannot run xsane 0.84 and 0.85 with the current CVS backends 1.0.7

2002-04-17 Thread Henning Meier-Geinitz
Hi, On Tue, Apr 16, 2002 at 10:55:18PM +0200, Christian Fughe wrote: > 1.) Xsane-0.85 shows garbled text in place of German umlauts in the menus > and messages. Same here, but only happens for me with the lincense dialog when started for the first time. Looks like a problem with UTF-8. If I d

[sane-devel] Cannot run xsane 0.84 and 0.85 with the current CVS backends 1.0.7

2002-04-16 Thread Christian Fughe
Hello, First, here is what just works fine for me: 1.) Stock xsane-0.84.tar.gz with sane-backends-1.0.7.tar.gz from 20 Mar 2002. The mustek backend is patched according the email from Henning on 4 Apr 2002 to make color scan available. 2.) The current CVS sane-backends, if used by scan