[sane-devel] Scanjet 4C - newbie with linux and sane scanning
On Mon, 18 Oct 2004 11:48:08 -0600 "Dr. Jones" wrote: > I am writing to get some help and pointers and to hopefully avoid > the pitfalls. ... > Any suggestions other than to dive in and try it on my machine? If the default kernel doesn't support your SCSI card you will need to find or compile one that does. Knowing what chipset it uses will help there. Once your card is recognised you have to set appropriate permissions on the device files so non-root users can use the scanner. Once you have got your SCSI configured properly it should be easy. Just apt-get install xsane and you're good to go. If it doesn't go start by reading man sane-scsi and sane-hp then post your logs and other details here. Martin
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
Oi, I got the above-mentioned scanners for some days for testing. Unfortunately without the Windows CDs. Can someone send me the firmware files for them (*.bin) files? The firmware file in Epson's IScan package seems not to work, too old or so. XSane segfaults with it. Thanks. Till
[sane-devel] update net.tex for sane1 documentation
--=-xv5kleSaPGSbmUmx0lXI Content-Type: multipart/mixed; boundary="=-JRc1KVGyz2RW6C1OPppe" --=-JRc1KVGyz2RW6C1OPppe Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Here's a patch to add RPC codes and a short explanation of transferred data to net.tex, with this the document is IMHO much more readable since now you actually know what data is on the wire :) johannes --=-JRc1KVGyz2RW6C1OPppe Content-Disposition: attachment; filename=net.tex.patch Content-Type: text/x-patch; name=net.tex.patch; charset=ISO-8859-15 Content-Transfer-Encoding: base64 SW5kZXg6IG5ldC50ZXgNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvY3Zzcm9vdC9zYW5lL3NhbmUt YmFja2VuZHMvZG9jL25ldC50ZXgsdg0KcmV0cmlldmluZyByZXZpc2lvbiAxLjINCmRpZmYgLXUg LXIxLjIgbmV0LnRleA0KLS0tIG5ldC50ZXgJMjAgTm92IDIwMDAgMTg6NDk6MTYgLTAwMDAJMS4y DQorKysgbmV0LnRleAkxOCBPY3QgMjAwNCAxODoxOToxMSAtMDAwMA0KQEAgLTE0Miw4ICsxNDIs MTQgQEANCiBjbGllbnQgc2lkZSAodGhlIG5ldHdvcmsgYmFja2VuZCktLS1hIHNlcnZlciBpcyBy ZXN0cmljdGVkIHRvDQogYW5zd2VyaW5nIHJlcXVlc3QgYnkgdGhlIGNsaWVudC4NCiANCitUaGUg ZGF0YSB0cmFuc2ZlcnJlZCBmcm9tIHRoZSBjbGllbnQgdG8gdGhlIHNlcnZlciBpcyBjb21wcm9t aXNlZCBvZg0KK3RoZSBSUEMgY29kZSAoYXMgYSBcY29kZXtTQU5FXF9XT1JEfSksIGZvbGxvd2Vk IGJ5IHRoZSBhcmd1bWVudHMgaW4gdGhlDQorb3JkZXIgbGlzdGVkLiBUaGUgc2VydmVyIHJlcGx5 IGNvbnNpc3RzIG9ubHkgb2YgdGhlIGRhdGEgZ2l2ZW4gYmVsb3cuDQorDQogXHN1YnNlY3Rpb257 XGNvZGV7XGRlZm57U0FORVxfTkVUXF9JTklUfX19DQogDQorUlBDIENvZGU6IDANCisNCiBUaGlz IFJQQyBlc3RhYmxpc2hlcyBhIGNvbm5lY3Rpb24gdG8gYSBwYXJ0aWN1bGFyIFNBTkUgbmV0d29y ayBkYWVtb24uDQogSXQgbXVzdCBiZSB0aGUgZmlyc3QgY2FsbCBpbiBhIFNBTkUgbmV0d29yayBz ZXNzaW9uLiAgVGhlIHBhcmFtZXRlcg0KIGFuZCByZXBseSBhcmd1bWVudHMgZm9yIHRoaXMgY2Fs bCBhcmUgc2hvd24gaW4gdGhlIHRhYmxlIGJlbG93Og0KQEAgLTE4MSw2ICsxODcsOCBAQA0KIA0K IFxzdWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVcX05FVFxfR0VUXF9ERVZJQ0VTfX19DQogDQor UlBDIENvZGU6IDENCisNCiBUaGlzIFJQQyBpcyB1c2VkIHRvIG9idGFpbiB0aGUgbGlzdCBvZiBk ZXZpY2VzIGFjY2Vzc2libGUgYnkgdGhlIFNBTkUNCiBkYWVtb24uDQogXGJlZ2lue2NlbnRlcn0N CkBAIC0yMDAsNiArMjA4LDggQEANCiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9O RVRcX09QRU59fX0NCiANCitSUEMgQ29kZTogMg0KKw0KIFRoaXMgUlBDIGlzIHVzZWQgdG8gb3Bl biBhIGNvbm5lY3Rpb24gdG8gYSByZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0N CiBcYmVnaW57dGFidWxhcn17bGx9DQpAQCAtMjI0LDYgKzIzNCw4IEBADQogDQogXHN1YnNlY3Rp b257XGNvZGV7XGRlZm57U0FORVxfTkVUXF9DTE9TRX19fQ0KIA0KK1JQQyBDb2RlOiAzDQorDQog VGhpcyBSUEMgaXMgdXNlZCB0byBjbG9zZSBhIGNvbm5lY3Rpb24gdG8gYSByZW1vdGUgU0FORSBk ZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCiBcYmVnaW57dGFidWxhcn17bGx9DQpAQCAtMjQwLDYg KzI1Miw4IEBADQogDQogXHN1YnNlY3Rpb257XGNvZGV7XGRlZm57U0FORVxfTkVUXF9HRVRcX09Q VElPTlxfREVTQ1JJUFRPUlN9fX0NCiANCitSUEMgQ29kZTogNA0KKw0KIFRoaXMgUlBDIGlzIHVz ZWQgdG8gb2J0YWluIHtcZW0gYWxsXC99IHRoZSBvcHRpb24gZGVzY3JpcHRvcnMgZm9yIGENCiBy ZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCkBAIC0yNjcsNiArMjgxLDggQEAN CiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9ORVRcX0NPTlRST0xcX09QVElPTn19 fQ0KIA0KK1JQQyBDb2RlOiA1DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBjb250cm9sIChpbnF1 aXJlLCBzZXQsIG9yIHNldCB0byBhdXRvbWF0aWMpIGENCiBzcGVjaWZpYyBvcHRpb24gb2YgYSBy ZW1vdGUgU0FORSBkZXZpY2UuDQogXGJlZ2lue2NlbnRlcn0NCkBAIC0zMTgsNiArMzM0LDggQEAN CiANCiBcc3Vic2VjdGlvbntcY29kZXtcZGVmbntTQU5FXF9ORVRcX0dFVFxfUEFSQU1FVEVSU319 fQ0KIA0KK1JQQyBDb2RlOiA2DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBvYnRhaW4gdGhlIHNj YW4gcGFyYW1ldGVycyBvZiBhIHJlbW90ZSBTQU5FDQogZGV2aWNlLg0KIFxiZWdpbntjZW50ZXJ9 DQpAQCAtMzM3LDYgKzM1NSw4IEBADQogDQogXHN1YnNlY3Rpb257XGNvZGV7XGRlZm57U0FORVxf TkVUXF9TVEFSVH19fQ0KIA0KK1JQQyBDb2RlOiA3DQorDQogVGhpcyBSUEMgaXMgdXNlZCB0byBz dGFydCBpbWFnZSBhY3F1aXNpdGlvbiAoc2Nhbm5pbmcpLg0KIFxiZWdpbntjZW50ZXJ9DQogXGJl Z2lue3RhYnVsYXJ9e2xsfQ0KQEAgLTM4Nyw2ICs0MDcsOCBAQA0KIA0KIFxzdWJzZWN0aW9ue1xj b2Rle1xkZWZue1NBTkVcX05FVFxfQ0FOQ0VMfX19DQogDQorUlBDIENvZGU6IDgNCisNCiBUaGlz IFJQQyBpcyB1c2VkIHRvIGNhbmNlbCB0aGUgY3VycmVudCBvcGVyYXRpb24gb2YgYSByZW1vdGUg U0FORQ0KIGRldmljZS4NCiBcYmVnaW57Y2VudGVyfQ0KQEAgLTQwNSw2ICs0MjcsOCBAQA0KIFxz dWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVcX05FVFxfQVVUSE9SSVpFfX19XGxhYmVse3NlYzph dXRob3JpemF0aW9ufQ0KIFxpbmRleHtuZXR3b3JrIGF1dGhvcml6YXRpb259DQogDQorUlBDIENv ZGU6IDkNCisNCiBUaGlzIFJQQyBpcyB1c2VkIHRvIHBhc3MgYXV0aG9yaXphdGlvbiBkYXRhIGZy b20gdGhlIG5ldCBjbGllbnQgdG8gdGhlDQogbmV0IHNlcnZlci4NCiBcYmVnaW57Y2VudGVyfQ0K QEAgLTQ0MCw2ICs0NjQsOCBAQA0KIA0KIA0KIFxzdWJzZWN0aW9ue1xjb2Rle1xkZWZue1NBTkVc X05FVFxfRVhJVH19fQ0KKw0KK1JQQyBDb2RlOiAxMA0KIA0KIFRoaXMgUlBDIGlzIHVzZWQgdG8g ZGlzY29ubmVjdCBhIG5ldCBjbGllbnQgZnJvbSBhIG5ldCBzZXJ2ZXIuICBUaGVyZQ0KIGFyZSBu byByZXF1ZXN0IG9yIHJlcGx5IGFyZ3VtZW50cyBpbiB0aGlzIGNhbGwuICBBcyBhIHJlc3VsdCBv ZiB0aGlzDQo= --=-JRc1KVGyz2RW6C1OPppe-- --=-xv5kleSaPGSbmUmx0lXI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -BEGIN PGP SIGNATURE- Comment: Johannes Berg (SIP Solutions) iQIVAwUAQXQJaKVg1VMiehFYAQIZuQ//fN3X4utoVGDvLMMoK/8GrDl4JJgzpmIO 20U11mc7emWrqEoJGxAw9yRWHG4qgVayqI/aXu3Kq3Rqin7WTlzUwV/Xe2+bdYqL BjeFzM7qEWxTexxkw5/eCADb/++Hb
[sane-devel] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
Hi, On Mon, Oct 18, 2004 at 09:03:55AM -0700, Susheel Yadav wrote: > Some good news on the Microtek Scanmaker 5600 front - > with Karsten's and Bertrik's help, I have been able to > decode the usb protocol for setting/reading status, > setting scan window and other scan parameters etc. > Using javax-usb, I have been able to read image data > through bulk transfer. I will start developing the > sane backend very soon. As a template, I plan to use > the sm3600 usb code. Good news. But please don't use direct calls to libusb as done in sm3600. Instead use the sanei_usb_* functions that are provided by sanei/sanei_usb.c. If backends use direct calls to libusb, they can't be used with other USB access methods and every backend muste be changed if e.g. a new USB access library is to be supported by SANE. > I have a couple of questions regarding sane > integration: > 1. Once I have the raw image data, what do I do with > it? In the SANE backend, you implement the function sane_read() which is called by the frontend to get the data from the backend. > 2. How do I process the raw image data to create > usable image? Depending on the scanner you may need to do line calibration (correction of the brightness difference of every single CCD/CIS pixel) and/or line distance correction (in color mode). More intelligent scanners do that internally, however. After that you process the image data to be compatible with the SANE protocol (see SANE standard) and return it by sane_read(). > 3. Is there any common core sane code to handle the > raw image data like saving it in different formats? That's done by the frontend. As a backend author you don't need to care about that. Bye, Henning
[sane-devel] I have the Epson Perfection 2480 and 2580 for testing
You can download them from EPSON's web site: http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? BV_UseBVCookie=yes&oid=41623&infoType=Overview http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? BV_UseBVCookie=yes&oid=41624&infoType=Overview On Oct 18, 2004, at 2:29 PM, Till Kamppeter wrote: > Oi, > > I got the above-mentioned scanners for some days for testing. > Unfortunately without the Windows CDs. Can someone send me the firmware > files for them (*.bin) files? The firmware file in Epson's IScan > package > seems not to work, too old or so. XSane segfaults with it. > > Thanks. > >Till > > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Re: Scanner Problems
On Monday 18 October 2004 05:59, Jason Anderson wrote: > I'm talking about version 1.0.14, I think it's CVS, but I don't know. = And > yep, I need to turn it 180 just to properly scan it. Which is the SANE version, that used to work? I'm pretty sure, that you w= on't find any other version that did it the other way. When opening the scanne= r, the sensor home position is on that side, where the button is located.=20 Ciao, Gerhard > > > Hi, > > > > On Sun, Oct 17, 2004 at 01:16:06PM -0500, Jason Anderson wrote: > > > I've just got a CanoScan N650U. When I use the current backends, > > > > With current backends you mean the version from CVS? > > > > > however, the darn picture is upside down! I don't know why, either= =2E > > > > What's the last version of sane-backends that worked? > > > > "Upside down" means that if you turn around (180=B0) the image that i= s > > to be scanned the result will be ok? > > > > Bye, > > Henning
[sane-devel] Scanjet 4C - newbie with linux and sane scanning
I am writing to get some help and pointers and to hopefully avoid the pitfalls. I have been running debian 3.0 a while now, but have yet to hook up my scanner, which now resides on an older windows machine. It uses the SCSI card interface, and works well on my win 98se box; but I want to eliminate Windows completely from my network here. Any suggestions other than to dive in and try it on my machine? I am thinking of just installing linux on my current 98se box...and then setting up SANE to handle the scanning, hoping that it's not too painful. I'd love to hear from others who use a ScanJet 4c device. Scott -- Dr. Scott S. Jones Hands-On Chiropractic IRC: irc.freenode.net #utah Yahoo: sanchiro12
[sane-devel] Xsane Crashes with Epson 4180 Scanner
Henning Meier-Geinitz writes: > Hi, > > On Fri, Oct 15, 2004 at 10:37:39AM +0900, Olaf Meeuwissen wrote: >> Karl Heinz Kremer writes: >> >> > It looks like this scanner does not "speak" the ESC/I protocol. At >> > least not any flavor that the EPSON backend supports. Maybe Olaf can >> > shed some light on this. >> >> I guess I could ;-) >> >> As the EPSON drivers say, this is a GT-F600. It does not speak ESC/I. >> It will be supported by iscan's epkowa backend in the near future (but >> first we'll get a release for a bunch of all-in-ones). > > I've added Perfection 4160 and GT-F600 as unsupported to our lists for > now (with some details from your mail). That's the Perfection 4180, but I see you've added it correctly in unsupported.desc. -- Olaf MeeuwissenEPSON KOWA Corporation, PF1 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] Need help analyzing USBSnoopy logs for Microtek Scanmaker 5600
Some good news on the Microtek Scanmaker 5600 front - with Karsten's and Bertrik's help, I have been able to decode the usb protocol for setting/reading status, setting scan window and other scan parameters etc. Using javax-usb, I have been able to read image data through bulk transfer. I will start developing the sane backend very soon. As a template, I plan to use the sm3600 usb code. I have a couple of questions regarding sane integration: 1. Once I have the raw image data, what do I do with it? 2. How do I process the raw image data to create usable image? 3. Is there any common core sane code to handle the raw image data like saving it in different formats? Thanks! Susheel --- Susheel Yadav wrote: > Karsten, > Please go ahead and send me the documents. > > Bertrik, > Your analysis is right on! So all that huge chunk of > data in the beginning is just for calibration, and > data the towards the end is the image data. > > I will play around with those parameters and try to > get some image. After that I will need to know how > to > use the calibration data. > > Thanks a lot guys! > > --- Karsten Festag wrote: > > > Hi, > > > > I just looked curiously on the data and I think > > there are some similarities > > between the scsi based scanners driven by the > > microtek2 backend and the 5600: > > > > command 0x24 is used to setup the scan window, > > probably first a fixed window > > for calibration and second the actual scan window. > > > > command 0x28 0xnn 0x80 reads image information > > (width, height, bytes) > > command 0x28 0xnn 0x81 reads system status (Lamps > > on/off, buttons,) and 0x2a > > 0xnn 0x81 should set the status. > > command 0x28 0xnn 0x82 reads scanner attributes > > (resolution, width, heigt of > > the scan area...) > > > > Maybe a look at the microtek2 sources helps you. I > > also have some (quite old) > > documentation but it may help. Tell me if I shall > > send it to you (its an ugly > > MS Word file :-() > > > > Regards, > > > > Karsten > > > > > > On Wednesday 15 September 2004 21:57, Susheel > Yadav > > wrote: > > > Thanks a lot Bertrik for your analysis. I have > > figured > > > out some things - I have written those down in > the > > > last link on the web page. > > > > > > *request=0x24 value=0x00 data=0x45 bytes > > > The data transferred in this request did not > > change > > > even if I moved the scan area horizontally > keeping > > the > > > size constant. This makes me think that maybe it > > scans > > > the whole row and the software clips the image > > later. > > > What do you think? > > > > > > *request=0x26 value=0x00 data=0xef00 bytes > > > This happens before bulk transfers, and the data > > > returned in Nth step is sent to the scanner in > the > > > (N+1)th request. > > > > > > *The bulk transfer is followed by a small > transfer > > of > > > 0x40 bytes. This returns 0x10 bytes. The last > 0x30 > > > bytes sent always remain same, and the first > 0x10 > > > bytes are the ones that were returned from the > > > previous cycle. Could this signify the position > of > > the > > > next chunk of data? > > > > > > *request=0x28, 0x40, 0x83, 0x12 repeat and I > think > > > they are status check. The windows driver has a > > > scanner detector utility which when turned on, > > keeps > > > sending those packets. > > > > > > *request=0x28 value=0x83 > > > This request gets the data that is send back in > > some > > > 0x40 0x2a 0x81 requests. > > > > > > *request=0x29 seems to denote the end of > transfer > > > since there is no more bulk data after that. > > > > > > --- Bertrik Sikken wrote: > > > > Susheel Yadav wrote: > > > > > Hi, > > > > > I am trying to write the linux driver for > > Microtek > > > > > Scanmaker 5600 scanner. I used USBSnoopy to > > > > > > > > generate > > > > > > > > > these logs from VMWare/Win2k. I have > filtered > > out > > > > > > > > the > > > > > > > > > big bulk transfers. The log files are still > in > > > > > > > > ~200KB > > > > > > > > > range. I am providing a link below with the > > log > > > > > > > > files. > > > > > > > > > I have made some progress in identifying the > > > > > > > > status > > > > > > > > > check packets, and some pattern in the bulk > > > > > > > > transfers, > > > > > > > > > but I have no idea what those medium sized > > control > > > > > packets mean. I would appreciate any help. > > > > > > > > > > http://blanca.homelinux.com/usblogs/ > > > > > > > > > > Thank you very much! > > > > > > > > What medium sized control packets do you mean? > > > > > > > > > > > > I looked a bit at the logs and noticed 10 > unique > > > > patterns: > > > > > > > > * request=0x12, value=0x00: read version info? > > > > The data returned by this transfer contains > the > > > > strings > > > > "ScanMaker 5600 1.30" > > > > "NowV0.10NewV0.10" > > > > > > > > * request=0x24, value=0x00: write 0x45 bytes > of > > scan > > > > settings? > > > > This transfer contains numbers like 1200, 600, > > 300, > >
[sane-devel] Translation status
2004-10-17 kl. 23.54 skrev Martin Collins: > On Sun, 17 Oct 2004 22:58:24 +0200 > Johannes Berg wrote: > >> It is a type of "rastern". See >> http://www.pl32.com/tutorial/sraster/sraster.htm >> for an image. > > So it seems Fatting is the name of the inventor of a dither pattern, > like Bayer or Floyd Steinberg. No translation necessary. > > Martin > This is what is in there now. S=C3=A5 most translators have tried to = find a=20 translation... sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 =D0=B3=D1=80=D1= =83=D0=B1=20 Fatting" -- sane-backends-1.0.15-pre1/po/sane-backends.bg.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.bg.po:msgstr "8x8 =D1=84=D0=B8=D0= =BD=20 Fatting" -- sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub=C3=A9=20= zv=C3=BDrazn=C4=9Bn=C3=AD (fatting)" -- sane-backends-1.0.15-pre1/po/sane-backends.cs.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.cs.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 jemn=C3=A9=20= zv=C3=BDran=C4=9Bn=C3=AD (fatting)" -- sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov=20 fortykning" -- sane-backends-1.0.15-pre1/po/sane-backends.da.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.da.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 fin=20 fortykning" -- sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.de.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.de.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.de.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.es.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.es.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.es.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka=20 lihavointi" -- sane-backends-1.0.15-pre1/po/sane-backends.fi.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.fi.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 hieno=20 lihavointi" -- sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.fr.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.fr.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.fr.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana=20 grossa" -- sane-backends-1.0.15-pre1/po/sane-backends.it.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.it.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana fine" -- sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof=20 Aandikken" -- sane-backends-1.0.15-pre1/po/sane-backends.nl.po-#, fuzzy sane-backends-1.0.15-pre1/po/sane-backends.nl.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Fijn=20 Aandikken" -- sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:111 sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Coarse=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.no.po-#: .tmp/leo.c:112 sane-backends-1.0.15-pre1/po/sane-backends.no.po:msgid "8x8 Fine=20 Fatting" sane-backends-1.0.15-pre1/po/sane-backends.no.po-msgstr "" -- sane-backends-1.0.15-pre1/po/sane-backends.pt.po-#: .tmp/leo.c:111
[sane-devel] Translation status
On Mon, 18 Oct 2004 00:23:41 +0200 Mattias Ellert wrote: > This is what is in there now. S=E5 most translators have tried to find > a translation... > sane-backends-1.0.15-pre1/po/sane-backends.cs.po-msgstr "8x8 hrub=E9=20 > zv=FDrazn__n=ED (fatting)" > sane-backends-1.0.15-pre1/po/sane-backends.da.po-msgstr "8x8 grov=20 > fortykning" > sane-backends-1.0.15-pre1/po/sane-backends.fi.po-msgstr "8x8 raaka=20 > lihavointi" > sane-backends-1.0.15-pre1/po/sane-backends.it.po-msgstr "8x8 grana=20 > grossa" > sane-backends-1.0.15-pre1/po/sane-backends.nl.po-msgstr "8x8 Grof=20 > Aandikken" > sane-backends-1.0.15-pre1/po/sane-backends.sv.po-msgstr "8x8 grov=20 > f=F6rtjockning" I'm no linguist but it looks like mostly variations on "fat" or "fattening". I bet the guy is as skinny as a rake. Martin
