[sane-devel] Last call for new backends
The hp5400 backend works ok with sane 1.0.11. The main functionality it=20 misses, is the 2400 dpi scan. We have not been working on it for one mont= h=20 due to lack a of spare time. SANE API I did not follow the changes that were made to the SANE API, if they exis= t, so=20 I don't know what the behaviour of the backend could be with 1.0.12 Transport protocol The last point I think of is that the communication with the scanner is m= ade=20 only through ioctl() function. To be SANE compliant, I suppose it would n= eed=20 to have more options than this one. I suppose this should not be a lot of= =20 work, but it is still too much for my own agenda. If someone would have time to integrate it into sane, it would be nice.=20 Integration would consist in : * port hp5400 Makefile into SANE compilation structure * verify hp5400 API is correct for SANE * support of others transport protocol=20 The latest source code is accessible via cvs at sourceforge : cvs -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/hp5400backend login= =20 cvs -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/hp5400backend co =20 hp5400/hp5400 I would be very pleased if someone would help us for the integration of t= he=20 hp5400 backend. Thank you, Thomas. Le Lundi 14 Avril 2003 20:18, Henning Meier-Geinitz a =E9crit : Hi, On Mon, Apr 14, 2003 at 07:48:14PM +0200, Till Kamppeter wrote: What about also including these backends (they are listed in sane/sane-backends/doc/descriptions-external/ in the current CVS snapshot): Noone of the maintainers of these backends asked for inckusion as far as I know. I hesitate to add a backend without an active maintainer. hp5400 No idea. ibm Not much used I guess at least the feedback I got was pretty minimal. But maybe the author got more. I'll have a look if it can be included without too much changes. lhii The webpage is gone and I haven't heard about this for years. Anyone using handscanners anymore? niash No idea. onetouch8600 I'm getting a connection closed or document contains no data from the server currently. primax That one may need some work to integrate it into sane as it currently compiles stand-alone. scanwit Seems to think the device is detected without checking? v4l2 Is v4l2 used at all? viceo IIRC, can't be added because of license trouble. Bye, Henning ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel
[sane-devel] Last call for new backends
Thomas Soumarmon souma...@nerim.net wrote: Hi, If someone would have time to integrate it into sane, it would be nice. Integration would consist in : * port hp5400 Makefile into SANE compilation structure * verify hp5400 API is correct for SANE * support of others transport protocol FYI I integrated your backend into the libsane-extras Debian package a week ago. The package is built using a stripped-down sane-backends source tree ; all I did is rename hp5400-sane.c to hp5400.c and hp5400.c to hp5400_stdalone.c (or similar), adjusting file references where needed. It built fine, and no problems were reported so far (somebody asked for its inclusion). JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org
[sane-devel] [XSane] some GUI idea.
Now I ever scan 135 film by XSane.I feel little incommodious. 1. Scan 135mm film alway need to prescan to get preview.I think pre scan is ever be uesd.But,preview window and man window is not same.I must move mouse point between preview window and man window to prescan or final scan in working.some time I change differance slide film,ten I should prescan ,but I ever to click scan button of main window subconscious.I look epson TAWIN interface,preview area is right on the main window. prescan button is close on final scan button.Can we copy TAWIN interface about this issue? 2.viewer window of final scan. do final scan , image is show in viewer window.Now version,viewer window is not smart.When I scan a film by big dpi,image width and hight become big,viewer window is too.viewer window widthly or hightly then my moniter,I can not see status bar of viewer ,so I zoom out image.when I choose zoom out, iamge become small, but viewer still bigly,I still can not see status bar,I only can adjuest viewer window manually. It is so incommodious.It is great if viewer can auto adjuest window width;hight when image zoom out. Thank you. - ¨C¤Ñ³£ Yahoo!©_¼¯ ¸Ó´«¤u§@¤F¶Ü? - À°§Aºâ¥X³Ì¦X¾Aªº¨D¾¤è¦V http://fate.yahoo.com.tw/
[sane-devel] Re: [linux-usb-devel] Why could not Xsane find my USB scanner? Sane-find-scanner, scanimage, xscanimage all can.
Hi, On Mon, Apr 14, 2003 at 04:59:01PM -0500, Peter Chen wrote: I'm using Redhat 9. I installed the most recent Sane CVS and then installed Xsane using its RPM for Redhat 8. When I ran Xsane, even as root, it always told me it could not find my Fujitsu fi-4120c scanner. What could be the reason? You are using two installations of sane-backends. XSane uses the one that came with your installation, scanimage uses the new one. Remove the sane-backends RPM that came with your distribution. There are a few other ways but basically you shouldn't have two versions of SANE at the same time. Search the sane-devel mailing list archive for more details. Bye, Henning
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 09:53:40AM +0200, Julien BLACHE wrote: FYI I integrated your backend into the libsane-extras Debian package a week ago. It built fine, and no problems were reported so far (somebody asked for its inclusion). It won't work on Debian/BSD oe Debian/Hurd because of the ioctls I guess :-) Bye, Henning
[sane-devel] Gradually increasing scan times
Karl O. Pinc wrote: [root@mofo xsane]# ( export SANEI_DEBUG_SANEI_SCSI=255; export SANE_DEBUG_HP=255; scanimage -d hp:/dev/sg3 | xloadimage stdin ) SANE_DEBUG_SANEI_SCSI=255, not SANEI_DEBUG. But the HP one is correct. So, now this hangs the box. It looks like the modem still works but X is hung along with the keyboard and mouse. I get 1 character from the keyboard when on a virtual console and then nothing after that. I'm inclined to let it lie at this point and just declare my scanner broken because I don't have more time to mess with it. Maybe upgrading all the software to a newer disto release with fix things. (Later.) Yes, there is something seriously broken, but I don't believe that it is the scanner. If your Linux box hangs in such a way, this looks more like a hardware problem (bad RAM for example) or a kernel bug. But a broken SCSI scanner should not be able to lock up your box, Abel
[sane-devel] Last call for new backends
--7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 15, 2003 at 09:53:40AM +0200, Julien BLACHE wrote: Thomas Soumarmon souma...@nerim.net wrote: =20 Hi, =20 If someone would have time to integrate it into sane, it would be nice.= =20 Integration would consist in : * port hp5400 Makefile into SANE compilation structure * verify hp5400 API is correct for SANE * support of others transport protocol=20 =20 FYI I integrated your backend into the libsane-extras Debian package a week ago. Very cool. Thanks for that. FWIW, the main problem it has is getting testers. On all the scanners we've tested (about 3 AFAIK) it works fine. It's never been tested on anything other than linux, or on anything than i386 for that matter. I'm almost expecting some endian-problems on other architectures but without an example I can't check. However, it don't hang or segfault, it doesn't break the scanner or make nasty noises. The image quality is good. If inclusion in a real release gets it the exposure it needs I'm all for it. My question is though, once it is included how do we update it? Do we continue externally and sync periodically or do we get commit access some other way? How does it work? The package is built using a stripped-down sane-backends source tree ; all I did is rename hp5400-sane.c to hp5400.c and hp5400.c to hp5400_stdalone.c (or similar), adjusting file references where needed. =20 It built fine, and no problems were reported so far (somebody asked for its inclusion). Good. We'll accept any patches that make it easier. Hey, maybe that's another user it worked for! :) Actually I notice sourceforge has logged 75 downloads and no bugs. Obviously it works good enough for most people (or it doesn't work at all). Have a nice day, --=20 Martijn van Oosterhout klep...@svana.org http://svana.org/kleptog/ the West won the world not by the superiority of its ideas or values or religion but rather by its superiority in applying organized violence. Westerners often forget this fact, non-Westerners never do. - Samuel P. Huntington --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+m9PWY5Twig3Ge+YRAkfUAJ4xlq25Se6r9fbFXwqpNDgFMkjZwACfe4cg W+SCJhX+H3LnUqXMrZSZOTo= =dYGW -END PGP SIGNATURE- --7AUc2qLy4jB3hD7Z--
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 08:31:40AM +0200, Thomas Soumarmon wrote: The hp5400 backend works ok with sane 1.0.11. The main functionality it misses, is the 2400 dpi scan. We have not been working on it for one month due to lack a of spare time. What about the license? Any reason not to use the SANE addition to GPL? Bye, Henning
[sane-devel] Last call for new backends
Hi, On Mon, Apr 14, 2003 at 07:48:14PM +0200, Till Kamppeter wrote: What about also including these backends (they are listed in sane/sane-backends/doc/descriptions-external/ in the current CVS snapshot): ibm I have added that backend to CVS now. Bye, Henning
[sane-devel] Last call for new backends
--xgyAXRrhYN0wYx8y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 15, 2003 at 11:18:26AM +0200, Henning Meier-Geinitz wrote: Direct hardware access like ioctl shouldn't be in the backends directly. I copied the basic access level from the hp3300 driver since the sanei stuff is not available to standalone programs. I imagine it wouldn't be too much work to fix, but it hasn't been done. What about libieee1284? I have seen some defines for that? Does the backend work with parport also? If yes, that'd need some work to only use libieee1284 if it's available. Hmm, ieee1284 is a parport protocol? Well, the scanner has a connector for it but I would have no idea about the format of the packets. How can you capture data going over a parallel cable? If someone would have time to integrate it into sane, it would be nice.= =20 Integration would consist in : * port hp5400 Makefile into SANE compilation structure * verify hp5400 API is correct for SANE * support of others transport protocol=20 =20 I'll check how much work it is. The Makefile can't be too bad since it's been included in Debian apparently. I would be very pleased if someone would help us for the integration of= the=20 hp5400 backend. As would I. --=20 Martijn van Oosterhout klep...@svana.org http://svana.org/kleptog/ the West won the world not by the superiority of its ideas or values or religion but rather by its superiority in applying organized violence. Westerners often forget this fact, non-Westerners never do. - Samuel P. Huntington --xgyAXRrhYN0wYx8y Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+m+CqY5Twig3Ge+YRAsrDAJ42kZFAcu9y56UtGEduS1Fh0CBU5QCg1lSd NQ9b3p+TCqOUfkFw/2dyGKA= =Yfj5 -END PGP SIGNATURE- --xgyAXRrhYN0wYx8y--
[sane-devel] Questions on dust-removal and infrared support on Nikon
Major A wrote: Although the new coolscan backend supports the IR-channel, I cannot get this combination working again. So I have two questions: Coolscan2 has a different way of transferring the IR image to the frontend. Read the sane-coolscan manpage for more information. Note that the R channel correction done by the coolscan backend is not available in coolscan2 (because it doesn't make sense to do it in the backend). I suggest you code that into the GIMP plugin. 2)One of the things the coolscan2-backend is trying to do is to incorporate dust-removal in the backend. I cannot find the status of this. If needed, I can do some testing on the LS2000. No, but there are plans for a meta-backend, but for the moment the only dust-removal code is in duster.c in Coolscan2 CVS on SourceForge. Please give it a try if you feel like hacking a bit. Andras After the remarks by Oliver and Andreas, I decided to try the stand-alone program for dust correction. Downloaded it, compiled it and tried to understand what it does. It seems that the duster program requires a separate file containing the IR-chanel. I could not find this option in any frontend. How do you make such a file? ljm -- (c) ljm @ xs4all . nl. No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Last call for new backends
Henning Meier-Geinitz henn...@meier-geinitz.de wrote: Hi, FYI I integrated your backend into the libsane-extras Debian package a week ago. It built fine, and no problems were reported so far (somebody asked for its inclusion). It won't work on Debian/BSD oe Debian/Hurd because of the ioctls I guess :-) None of these ports are mainline, nor targetted for release, so I do not really care :-) Should it break, we'd go ahead and fix it ;) JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org
[sane-devel] Last call for new backends
Martijn van Oosterhout klep...@svana.org wrote: Hi, If someone would have time to integrate it into sane, it would be nice. Integration would consist in : * port hp5400 Makefile into SANE compilation structure * verify hp5400 API is correct for SANE * support of others transport protocol FYI I integrated your backend into the libsane-extras Debian package a week ago. Very cool. Thanks for that. You're welcome. [...] Good. We'll accept any patches that make it easier. Hey, maybe that's another user it worked for! :) Yep, the scanner was an HP5470c USB. You can fetch the source package I use to build libsane-extras on ftp://ftp.debian.org/debian/pool/main/s/sane-backends-extras/sane-backends-extras_1.0.10.3.tar.gz Basically, you need to add hp5400 to the list of backends in backend/Makefile.in, and add a dependency for libsane-hp5400.la on sanei_config2.lo. With that done, the file backend/hp5400.c will be picked up and built (that's why I had to rename hp5400-sane.c). JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org
[sane-devel] Re: Gradually increasing scan times
On Mon, Apr 14, 2003 at 01:15:30PM -0500, Karl O. Pinc wrote: [...] That was very helpful. Turns out that many of the backend librarires did not have softlinks to the *.so.1 from the *.so.1.0.11 files. Rpms from contrib.redhat.com: [kop@mofo kop]$ rpm -qa | grep sane sane-frontends-1.0.10-1 xsane-0.90-1 xsane-gimp-0.82-3.1 sane-backends-1.0.11-1 [...] That's odd. On my system(s), the symlinks get installed properly. I'd be interested to hear more about this, as I built those RPMs (except the xsane-gimp one, which seems to be old). Cheerio, Thomas -- - Thomas Ribbrockhttp://www.ribbrock.org You have to live on the edge of reality - to make your dreams come true!
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 07:41:43PM +1000, Martijn van Oosterhout wrote: FWIW, the main problem it has is getting testers. On all the scanners we've tested (about 3 AFAIK) it works fine. It's never been tested on anything other than linux, or on anything than i386 for that matter. I'm almost expecting some endian-problems on other architectures but without an example I can't check. Endianess problems should only occur if you scan 16 bit images and access them as u_int16 mixed with u_int8. Or with any other data type 8 bits sent to the scanner directly. My question is though, once it is included how do we update it? Do we continue externally and sync periodically or do we get commit access some other way? How does it work? Ask Petter Reinhodtsen for write access to the SANE CVS server: http://www.student.uit.no/~pere/linux/sane/cvs-server.html Bye, Henning
[sane-devel] External Adapters
--JgQwtEuHJzHdouWu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The HP5400 scanner has the possibility to add a document feeder or a slide adapter. However there don't appear to be any standard options dealing with these. I was pondering the negative option but that's really not appropriate since it deals with colour correction and that's really quite orthogonal. Any ideas? --=20 Martijn van Oosterhout klep...@svana.org http://svana.org/kleptog/ the West won the world not by the superiority of its ideas or values or religion but rather by its superiority in applying organized violence. Westerners often forget this fact, non-Westerners never do. - Samuel P. Huntington --JgQwtEuHJzHdouWu Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+m/TvY5Twig3Ge+YRAr5bAJ9ImDPTT1JchCv5Wr/nxQcghD9VfgCguui1 9m1sUquveaYi6Vd6wdd0ChU= =bpym -END PGP SIGNATURE- --JgQwtEuHJzHdouWu--
[sane-devel] Last call for new backends
snip What about libieee1284? I have seen some defines for that? Does the backend work with parport also? If yes, that'd need some work to only use libieee1284 if it's available. backend does not work with parport. I don't know if the communication pro= tocol=20 would fit anyway. The defines you saw are remains from the template backe= nd=20 used. Bye, Thomas.
[sane-devel] Last call for new backends
--IDYEmSnFhs3mNXr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 15, 2003 at 11:47:10AM +0200, Henning Meier-Geinitz wrote: Hi, =20 On Tue, Apr 15, 2003 at 08:31:40AM +0200, Thomas Soumarmon wrote: The hp5400 backend works ok with sane 1.0.11. The main functionality it= =20 misses, is the 2400 dpi scan. We have not been working on it for one mo= nth=20 due to lack a of spare time. =20 What about the license? Any reason not to use the SANE addition to GPL? Oh. I'd looked at the license in packaged into /usr/share/doc/sane and it just said GPLv2. Now the source says: Backend libraries are protected by the GNU General Public License (see file COPYING), but as an exception, it is permissible to link against such a library without affecting the licensing status of the program that uses the libraries. For details, see the copyright notice at the head of the backend files (e.g., backend/dll.c). Isn't that just the LGPL? Anyway, I have no objections but obviously this needs to be organised properly and agreed to by people. Is it actually a requirement though? It doesn't appear to be so. --=20 Martijn van Oosterhout klep...@svana.org http://svana.org/kleptog/ the West won the world not by the superiority of its ideas or values or religion but rather by its superiority in applying organized violence. Westerners often forget this fact, non-Westerners never do. - Samuel P. Huntington --IDYEmSnFhs3mNXr+ Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+nADoY5Twig3Ge+YRAqeWAJ0b8pX3VTmbzj6tBw25hF5E72lYeQCfYjjn /3QprgqLh2PoJTceo59MCms= =HxFF -END PGP SIGNATURE- --IDYEmSnFhs3mNXr+--
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 07:41:43PM +1000, Martijn van Oosterhout wrote: Good. We'll accept any patches that make it easier. Hey, maybe that's another user it worked for! :) Ok, I'm currently working on the backend. What are the vendor/device ids of these scanners? Currently I use # HP 5400C usb 0x03F0 0x1005 # HP 5470C usb 0x03F0 0x1105 What I have done until now: - Update the sane Makefile and dll.conf - Get it compiling: gcc may accept variable initializers, other compilers won't - rename hp5400_sane.c to hp5400.c - rename hp5400_scanner.c to hp5400_sanei.c - rename hp5400.c to hp5400_internal.c - Make sane_init accept usb vendor product lines - Fix some warnings - Add some DBGs - run it through indent What I want to do: - Add SANE headers (this is part of...) - Add sanei_usb support - Remove more compilation warnings - check for non-static symbols - Add manpage - Update documentation/AUTHORS/DESC Bye, Henning
[sane-devel] Questions on dust-removal and infrared support on Nikon
After the remarks by Oliver and Andreas, I decided to try the stand-alone program for dust correction. Downloaded it, compiled it and tried to understand what it does. It seems that the duster program requires a separate file containing the IR-chanel. I could not find this option in any frontend. How do you make such a file? Coolscan2 will generate one. See the sane-coolscan2 manual page for details. Andras === Major Andras e-mail: and...@users.sourceforge.net www:http://andras.webhop.org/ ===
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 08:31:40AM +0200, Thomas Soumarmon wrote: I would be very pleased if someone would help us for the integration of the hp5400 backend. There is a snapshot of sane-backends including the hp5400 backend: http://www.meier-geinitz.de/sane/snapshots/sane-backends-2003-04-15-2.tar.gz The code compiles on Linux/i386, Tru64, HPUX/Itanium, NetBSD/Alpha and FreeBSD/Alpha. There are still some compilation warnings. Please test. Make sure that the new configuration file is used, not the old one that may be already installed. Tell me where it breaks :-) I've added sanei_usb support and USB autodetection. Fixed some Linux/gcc specific stuff. Renamed files as mentioned in my other mail. Still todo: - manpage - AUTHORS/sane.man - Fix warnings - Testing Whom should I mention as author in AUTHORS? Who is maintaining the backend? Bye, Henning
[sane-devel] [XSane] some GUI idea.
Hello. 1. You can use ALT p for preview scan and CTRL ENTER for final scan. You can put the main window left to the preview window so that preview button and scan button are very close to another. 2. XSane calculates the size of the window so that it does not exceeds the size of the screen (- size of the task bar). When this does not work correct then the window manager that you use reports incorrect values. What window manager do you use? Oliver On Tuesday 15 April 2003 10:13, leolarrel wrote: Now I ever scan 135 film by XSane.I feel little incommodious. 1. Scan 135mm film alway need to prescan to get preview.I think pre scan is ever be uesd.But,preview window and man window is not same.I must move mouse point between preview window and man window to prescan or final scan in working.some time I change differance slide film,ten I should prescan ,but I ever to click scan button of main window subconscious.I look epson TAWIN interface,preview area is right on the main window. prescan button is close on final scan button.Can we copy TAWIN interface about this issue? 2.viewer window of final scan. do final scan , image is show in viewer window.Now version,viewer window is not smart.When I scan a film by big dpi,image width and hight become big,viewer window is too.viewer window widthly or hightly then my moniter,I can not see status bar of viewer ,so I zoom out image.when I choose zoom out, iamge become small, but viewer still bigly,I still can not see status bar,I only can adjuest viewer window manually. It is so incommodious.It is great if viewer can auto adjuest window width;hight when image zoom out. Thank you. - =A8C=A4=D1=B3=A3 Yahoo!=A9_=BC=AF =B8=D3=B4=AB=A4u=A7@=A4F=B6=DC? - =C0=B0=A7A=BA=E2=A5X=B3=CC=A6X=BEA=AA= =BA=A8D=C2=BE=A4=E8=A6V http://fate.yahoo.com.tw/ ___ Sane-devel mailing list sane-de...@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:oliver.ra...@rauch-domain.de
[sane-devel] External Adapters
Hi, On Tue, Apr 15, 2003 at 10:02:56PM +1000, Martijn van Oosterhout wrote: The HP5400 scanner has the possibility to add a document feeder or a slide adapter. However there don't appear to be any standard options dealing with these. I was pondering the negative option but that's really not appropriate since it deals with colour correction and that's really quite orthogonal. Option source. Not (yet) well-known, but used by quite some backends. Here is the definition from SANE2: The option source is used to select the scan source (e.g. Automatic Document Feeder). It defines a SANE_CONSTRAINT_STRING_LIST of type SANE_TYPE_STRING. Well known sources are: Flatbed, Transparancy Adapter and Automatic Document Feeder. Bye, Henning
[sane-devel] External Adapters
Martijn van Oosterhout wrote: The HP5400 scanner has the possibility to add a document feeder or a slide adapter. However there don't appear to be any standard options dealing with these. I was pondering the negative option but that's really not appropriate since it deals with colour correction and that's really quite orthogonal. Any ideas? What about using the option scan source, defined by the macro SANE_NAME_SCAN_SOURCE in include/sane/saneopts.h ? Abel
[sane-devel] Last call for new backends
Hi, On Tue, Apr 15, 2003 at 10:54:00PM +1000, Martijn van Oosterhout wrote: Oh. I'd looked at the license in packaged into /usr/share/doc/sane and it just said GPLv2. Now the source says: The file LICENSE that you quote is also installed to /usr/local/share/sane. COPYING contains the original text of the GPL. Backend libraries are protected by the GNU General Public License (see file COPYING), but as an exception, it is permissible to link against such a library without affecting the licensing status of the program that uses the libraries. For details, see the copyright notice at the head of the backend files (e.g., backend/dll.c). Isn't that just the LGPL? It's similar. As far as I know, when SANE was born, there was no LPGL. Anyway, I have no objections but obviously this needs to be organised properly and agreed to by people. Is it actually a requirement though? It doesn't appear to be so. I think currently all backends use GPL+SANE clause. Pure GPL may be critical if a distribution links to a non-GPL software. So if possible, I'd prefer to keep GPL+SANE clause for the backends. Bye, Henning
[sane-devel] Last call for new backends
Henning Meier-Geinitz wrote: if you intend to get a new backend into SANE 1.0.12 it's now time to tell us. Currently there are two backends on the TODO list: - Hewlett-Packard ScanJet 3300C / 3400C and 4300C (wip) http://sourceforge.net/projects/hp3300backend snip I'd like to hold off inclusion for now. Things to do still: * clean up historic cruft * figure out proper hp3400/4300 resolution and scan position setting (we have some work-arounds already) * implement analog frontend calibration (currently used fixed setting) * implement lamp timer to wait for warm-up before scan Those last two issues frequently cause colored vertical lines on the first scan. Regards, Bertrik Sikken
[sane-devel] Last call for new backends
Henning Meier-Geinitz wrote: Hi, if you intend to get a new backend into SANE 1.0.12 it's now time to tell us. Currently there are two backends on the TODO list: - Hewlett-Packard 4200c [...] http://fz.eryx.net/sane/#hp4200 What's the status of those? Are there any others that are intended to go in 1.0.12 (or later versions)? Last time I tested my version (http://fz.eryx.net/sane/#hp4200), it worked. However I don't have access to that scanner anymore, so I won't push for its inclusion. Frank.
[sane-devel] Problem linking shared objects under kylix
I'm using Linux Sane libsane.so, I ran kylix(bcb) not as root and added libsane.so (a symbolic link actually) to my project and included sane.h (one function is declared as extern sane_status sane_init(...) in this .h file), I could compile the project but could not make it, always telling me linker error. I'm using Redhat 9. I don't know if it's something wrong with my usage of shared objects or if this is a bug of kylix or wrong configuration of kylix? What should I do? Thanks
