I don't think that "negative slide" is a term that is actually used: A "slide" is a positive transparent image, and a "negative" is a normal photographic negative.
On 2/26/07, Olaf Meeuwissen <[email protected]> wrote: > > Giuseppe Sacco <[email protected]> writes: > > > While updating the Italian translation for sane, I found this new string > > for the epson2 backend: "Negative Slide". While I could probably > > translate it without problem, I wonder what a negative slide is. What is > > the difference between a normal film and a negative slide? > > The opposite of a positive slide ;-) > > Seriously, there are two types of transparencies: negative and > positive. The latter may be better known as a "dia", usually > mounted in a frame and shown with a projector. > > Hope this helps, > -- > Olaf Meeuwissen EPSON AVASYS Corporation, SE1 > FSF Associate Member #1962 sign up at http://member.fsf.org/ > GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 > Penguin's lib! -- I hack, therefore I am -- LPIC-2 > > -- > sane-devel mailing list: [email protected] > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to [email protected] > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070304/1e4c7178/attachment.html From [email protected] Tue Mar 6 11:22:06 2007 From: [email protected] (Volker Barth) Date: Tue Mar 6 10:22:51 2007 Subject: [sane-devel] 3 mins delay at xscanimage startup due to querying hpiod Message-ID: <[email protected]> Dear all, I recently bought my first scanner (Canon Lide 25), which is reported to work with the plustek backend. I'm running Kubuntu Dapper and have the most recent ubuntu binary packages 'libsane' and 'sane' installed. My problem is that when I start xscanimage it takes 3:10 minutes until the GUI shows up, which is quite a while. After setting SANE_DEBUG_XSCANIMAGE to 4 I found that it stays all the time in the [init] section. Meanwhile, the syslog gives the following messages: scanimage: unable to open /var/run/hplip/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 84 when xscanimage is being started and when [init] has finished and the GUI shows up: xscanimage: unable to connect hpiod socket 50000: Connection timed out: prnt/hpijs/hplip_api.c 703 xscanimage: ProbeDevices(): unable to send message: Bad file descriptor Because of the first message I tried to start the hpiod daemon and hplip, although I did not understand why a Canon scanner on the plustek backend might require this daemon... The syslog told me: hpiod: 0.9.7 accepting connections at 45490... When starting xscanimage anew, the only improvement was that the first message complaining about the missing hpiod.port disappeared, but the rest remained very similar (after 190 seconds of waiting): xscanimage: unable to connect hpiod socket 45490: Connection timed out: prnt/hpijs/hplip_api.c 703 xscanimage: ProbeDevices(): unable to send message: Bad file descriptor This behaviour does not change even when I start xscanimage as root. In any case, after the GUI shows up, the scanner works apparently without problems, so it's only the looong delay that puzzles me. My questions: - Why does xscanimage (or the KDE frontend kooka, or xsane, which I all tried as well) try to connect to hpiod when there is apparently no device present that depends on this daemon? - Is there a way to stop xscanimage to query the hpiod socket, or at least to shorten the time it tries to connect to it? - Do you think that compiling sane from source offers a chance to circumvent this problem (e.g. because there is an option to build sane without querying hpiod)? Thanks for your help and suggestions. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal f?r Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
