[sane-devel] First try dutch translation
--HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, On Wed, Feb 26, 2003 at 11:02:19PM +0100, Martin Kho wrote: > Some time ago Henning Meier-Geinitz asked for translators. I saw that there > was no dutch-translation. So maybe the attached po-file will fill the gap. Well, in the meantime Bertrik Sikken provided a dutch translation that is in CVS. Sorry for that. Anyway. your translation is much more complete than his. Translated : 304 (54.3%) (of which 12 fuzzy ( 3.9%)) Not translated : 256 (45.7%) Total : 560 > Yann's script gives the following output: > > [.tmp/mustek.c:156](151) "Flatbed" What's the problem with translating this one? It just means that the image is scanned from the usual flatbed, not the transparency adapter or automatic document feeder. > Translated : 552 (98.4%) (of which 7 fuzzy ( 1.3%)) > Not translated :9 ( 1.6%) > Total : 561 Very good! > I hope that someone can check my translations and make necessary > corrections/additions. I don't speak Dutch so I can't comment. I'll attach the po file that's currently in CVS so maybe you can compare and select the better translation if they differ. Thanks for your work! Bye, Henning --HlL+5n6rz5pIUxbD Content-Type: application/octet-stream Content-Disposition: attachment; filename="sane-backends.nl.po.gz" Content-Transfer-Encoding: base64 H4sICKpFXT4AA3NhbmUtYmFja2VuZHMubmwucG8ArDxpjxu3kt/zKwgHb5+DHSnqQ9fsvsXO 4XGM+MjzTGLgIUBAqSmJVqu7Xx8jj3/9VpHdvJqtkbP5MhhRrGKxWFWsi/qe3Db1ekfqkmZV SmueZ2STl+T+6v0rsqLrPcsSkhc4Xn33PbnJi6eSb3c1eXnzAwknk0jO/KXMP7N1PYYp16ys S74n93wPwBfkv1dy4H+/5lnG6nGW/s+FgBx/d6i2PCEvXuA/VV3ify9aTKM3yeg3Vlaw7iWp aMZGLTEVCcaTcRD8nuHkDw+jm5IJske3tGaXAvNoEo7CKQmjy3j2n5NgMmknjz6yR171506W JIguw4me+5ZW9eih5UleXjq78m2qhcu2Dd2y0QOjh0sixt69efdK7wWoF6M3eVazDBZ5KoCS mn2pfyxSyrP/IusdLStW/+PXh7vRwp6LBG1YOXqVrfOEZ9tLsljxGud89/0lGdeH4kda1mz9 ByvSpooXzXh9GUwj+c22ni2+fMGRYCFHDjSYTpY4MgkUgkNT1WyPg8BCZySamCN/NNUKRsP5 RAFXa1bUJRvvLsPlvB3KaFGtaYbwsxa+OVBByGKqP/9RFGKJqBOLtzxjsBstHf86wscfj7w+ vd1YfpOyHMmYLeVHmJYHgi5jIISBaBopbDgW4dgkOkHY65I+wY5Spkl7XfLPVc3xmE4T126Y FVWOHIk7ao3DmVn0G8w1j6t3VrPzzmq2UOiQLDk3DOPeUNQfimP3kKOJcfTGOU/nNtNhnsv0 2OV4bJxCVYs9OdKynJw4lJs8zUt9ID+nrClPHUW4mCwd1k+XhuisLxfzoM/6aSfWB1pXTbXj NRWHFrfIDnxd5sAv3OQs8GhVHM5Dz8FEnZZqfi+DRU+v1pfzbmLH71FrnRF3JxeS70hXNLOE O8TBOJ6azIeV5oHF6WkwC11Wx7OgY/WrbEezNTuASdIMBwO3YjUrwSqd1oFwMW/NT5EdhPmY dYhv2YY2aV1prPc1zRJKSzB2wJU0PQP7YtKhu2c1SSRK8kjThlXiamOafLIGy1rmaTU2VJmt ygYsfdUtfcQ/YPMfcwBeMZYmj3qvlUnY+BnKFrbyh4swcERwNtUK1UphGLkiqGTNEsHJcqql zZLCSU8EO323RXAy9diGRSeuhghOpoMiGEWxJXBCCifdzpUIRsu5I4LdNlvlnwVacJVUBn2p DEJllVl+YHX5pE/yagMDz0vMMlICeENTviqFO6HRqEF2Gk08ddEwEBeQOEYyuN4JcsrFylgp 5Qr+qerHPAViE9ZOPbnYXHtPL95sQKjpKmXJBal3DIT+ka8ZOfI0BQrIuiMn6ejBSYqmMfkA n8sjr9gFAWxrzQTCK1KwEmAOAJxn6ZOJYcOBZtSTsh6bPtwpuqeLju4PiK1FTqodRX9mtM7L Erw/i/+nEc4mA4wQ1CKZLW6icdvbSppSfK23PSYPAAf4PNZjCz4aIN9swEUjYCEI+1LkVYMs 4QdgIOPITLJqeJqMeEYAZFPmB8SGxIDB2fBt07J3w1MAoQDcVCw5m4lzZYqvm7oGPHAGNfND S4cX7EC8VKryvjmA/wqbkMdY0gNQnzsCekWzmqby24rADmopl5mtTgb+SBveFBhdSTE7Z62f OSyxQ4bKRfVS7frGijCeZ7NoIlgxUeK0BadMI9yiPzYItNRmJAjDdnDec+8cIg0fz9FPC3sw 8WFXdN7mhJKtWgIEAcWlhisJZANcGGfR25yBbcjEKAFx2moiCB8X48cx2TuujkXNNFYMAsHV eB/R3rByD5I/CKrs2VVG03xLXlsY5CAjv52BSRnYN9kawrWKoVokrP0fBYPKJZDITlZubm5B NaxjhbV2OUyDGbCBlNItYGlhGTH2BBqb4VeIo4LzygcZpKV2Sw8HaoiQ/DgAFZtXOVyy6nxf IxjEyX07Jr7pjBAbxDz1aZEgprNgYLPqNhIk66Z8ZI4iJe380ZYhBN/C5QJjOfAnKel6V1ct lKJAhyNhPzYI+rFBfyjWJoln1LyF8TMvvYv1A1PlXJ+IdKZ9p3oo2Fn2dxN5fJww6jnfYey4 PSJy9Ac7KqD0hy0Ly7I49sTHl1mPLz0fMJj04r144eHLNOyNzDxheeRQrA7zLqX1iiWGBqZ0 LwY8ZCtTI/IUBVxr2fqJ/Jrx2ns1acBenmEaOgQpJb1q6hz8Xr4mt/m6ET78HWMJM0K/bkq1 BsVRs27By3rMmVcQF0rnfskrXvNHRu54etAo5TB7RJ8Hxz0olIl7z7bUg0IOn0Kh7+c7IBqu XLD2Ka2saIilBLdVFiQvxIWJM7zIIhtZOJ4eDoSuwAh4scrv8etM4W2X8qCfBktnIJw7A5E7 Y6aDYRnZBBNvHBMtfKNTrXv2F8vAMxoGavvv88zM0zDLe9HkT9wBJ1abxsrP/ImmG3C6GLki L3+C0JA8wIcfTor4tDOiesBljzagCv81eXmfb+qz8Icu+90NxWEP/w15+R6O+h6uYZY9s0Dk biBWHL6VHi9wI/4Sk2v6xEoD2S8UAmwQZedrzwruFuLYWeFaorgveElTzxLm92KCZ5HIXWTq LHIjkXgZ0y3km+NZK3bXmjlr3ZKXi+fW8s3pr6XDwQcM69oMDYgmW+8ycCu3T6ePNzb802OW 5jQhBa3BmYKDewZyOQh5fRpy5hx4OAsVgz6ad87HPPddONNZ1EOgswGl0HR91+Z+xZ/FLo5I Kfo1BH2GH5PS5uhDsYy1rfE7fujA+xw/jcJJC89CRcSvFUNXecMzkyVeJNrLPhR0XY+SvCZF ibFCaZj7dyBY/Ise9yDSwgRSeoB4rI9FfCOv2JOolFy9yfajz8xHEHxT29948Cgpu/n4QA45 +BS5ieMa03Liujp4z3kWOE5a5CYdPTlHH55Qm2m+3cHBZOAZPEnaRQR04oQM8XybH78VNrIW FolLWtVnQmvrb8oTeSlikn8E48lp8z/T1t4PvzgNP9f38c2tkQO79c5V+nQ1JUVewj6f8SDn wdQASeH4wLMt/AkRDaMk4C1De/XMbKUTV7HhasbeuUrowX3Vk8WH3uww6pxd5e7H3VWo3P14 OeT+TLqijJXyVZ6VSvlOIAqxwwMVJE3c2Gc+70p3KuU7m+t0rCfrGyysoprQL1vhwqV2/1qv HjalU/WY3niXJ8aZ4dBBjHh4tvBGybvWs/En0hR0PNHKX+ZF3pyWLpg/962WSNjnFguWPuCV qKJnrDJLD3ICROtYtwA3PIW4Zsd4MvYi1rWv+x0tC8Rlcg9d99rLvelMZ6pFysmXdRUFtFOX FqCZ6Z2121o7+EiN2ViROBWpWLnBhADfiqZuE9UmByAWEZvfW8sDFohReFuDEfEJ2+df4Vql BcSZlNZeFs0mgxuFf9lmw9ccYsNqaNfGHO+tAgsoFshrlRzgKuFFytcywZtvyMfX1+7l+yiu Kb59bNKEb7t0lZjoWSM0zplDOLBF1wZzqKUVmMPNud41fAPfg69DMrjBSOn3nABnPIBzZfk
[sane-devel] Alpha version for hp5400 backend
Thomas Soumarmon wrote: >Thanks to Martijn van Oosterhout, an alpha version of the SANE backend for >HP5400 scanners is available for download at >http://sourceforge.net/projects/hp5400backend > >As it is alpha code, it is buggy and of interest only for development >purposes. > >Feel free to test it and submit bug fixes, improvements > Did you know that sane (since version 1.0.9 or so) has its own USB interface? Using the sane usb functions should make the backend more platform independent (since it can choose to use libusb, the linux 'scanner' module and perhaps in the future even a bsd 'uscanner' module). These functions are specified in the header file sanei_usb.h You could for example add another file (say hp5400_saneiusb.c) that implements the exact same functions as hp5400_scanner.c, but using the functions from sanei_usb instead of reading/writing to the device files of the 'scanner' module. For the standalone tool you would still link hp5400_scanner.o and for the sane backend you would link hp5400_saneiusb.o In that case it would also be a good idea to move all functions that are not strictly related to data transport to one of the other source files. Kind regards, Bertrik
[sane-devel] Support for Alcatel Speed Touch ADSL internet scanner?
Oi, I have run "sane-find-scanner" on a machine with the Alcatel Speed Touch USB ADSL Modem connected: [root@majax root]# sane-find-scanner -q found USB scanner (vendor=0x04b8, product=0x0112) at /dev/usb/scanner0 found USB scanner (vendor=0x04b8, product=0x011d) at /dev/usb/scanner1 found USB scanner (vendor=0x04b8, product=0x0801) at /dev/usb/scanner2 found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:001:004 found USB scanner (vendor=0x04b8 [EPSON], product=0x011d [EPSON Scanner]) at libusb:001:010 found USB scanner (vendor=0x04b8 [EPSON], product=0x0801 [USB MFP]) at libusb:001:012 found USB scanner (vendor=0x06b9 [ALCATEL], product=0x4061 [Speed Touch USB ]) at libusb:001:013 [root@majax root]# Not only the three connected scanners are listed, but also the Alcatel modem. I didn't know that this device is an internet scanner. In Mandrake Linux this causes the problem that Harddrake lists this device in the scanner sub-directory and users get confused. Perhaps there is a bug in "sane-find-scanner" which makes the modem recognized as a scanner. Here is the part which this device produces in /proc/bus/usb/devices; -- T: Bus=01 Lev=02 Prnt=02 Port=06 Cnt=06 Dev#= 13 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=06b9 ProdID=4061 Rev= 0.00 S: Manufacturer=ALCATEL S: Product=Speed Touch USB S: SerialNumber=0090D043AD74 C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=50ms I: If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) I: If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 1 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=06(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=07(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=87(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=05(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=85(I) Atr=02(Bulk) MxPS= 8 Ivl=0ms -- "lsusb -vvv" gives this: -- Bus 001 Device 013: ID 06b9:4061 Alcatel Telecom Speed Touch ISDN Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06b9 Alcatel Telecom idProduct 0x4061 Speed Touch ISDN bcdDevice0.00 iManufacturer 1 ALCATEL iProduct2 Speed Touch USB iSerial 3 0090D043AD74 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 147 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type none wMaxPacketSize 16 bInterval 50 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 1 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpoi
[sane-devel] First try dutch translation
--Boundary-00=_VVRXXGITYA6WG58NQPHU Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Some time ago Henning Meier-Geinitz asked for translators. I saw that the= re was no dutch-translation. So maybe the attached po-file will fill the gap= =2E Yann's script gives the following output: [.tmp/mustek.c:156](151) "Flatbed" [.tmp/epson.c:527](197) "Dither A (4x4 Bayer)" [.tmp/epson.c:528](201) "Dither B (4x4 Spiral)" [.tmp/epson.c:529](205) "Dither C (4x4 Net Screen)" [.tmp/epson.c:530](209) "Dither D (8x4 Net Screen)" [.tmp/leo.c:111](638) "8x8 Coarse Fatting" [.tmp/leo.c:112](642) "8x8 Fine Fatting" [.tmp/leo.c:113](646) "8x8 Bayer" [.tmp/leo.c:114](650) "8x8 Vertical Line" Translated : 552 (98.4%) (of which 7 fuzzy ( 1.3%)) Not translated :9 ( 1.6%) Total : 561 Besides I tested the file as noted in the po-README. There were no errors= =2E I hope that someone can check my translations and make necessary=20 corrections/additions. Bye, Martin --Boundary-00=_VVRXXGITYA6WG58NQPHU Content-Type: application/x-gzip; name="sane-backends.nl.po.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="sane-backends.nl.po.gz" H4sICCkuXT4AA3NhbmUtYmFja2VuZHMubmwucG8AtFzpciM3kv7vp8C2I9bqWJFmFYuXdmdjJbHV 7nBf22rbGxOOcIAskESzrqlDaumNJuYx/GKbmajCUQQp9cTuj/GIKOBDIpHIC4n+ni2ber1jdcmz KuG1zDO2yUt2e/n+FVvx9V5kMcsLbK+++55d58VDKbe7mp1dv2ThaBSqnh/L/ItY10Po8o6XtczY z7uc/Ue63+X/9bWKeJIMs+Q/z3HEePhdWm1lzF68wD+qusS/XrQIgzfx4FdRVjDfBat4JgYtERUL hqNhMPo9w84fPg+uS0HkDpa8FheEPBiFg3DKwvAiiP5tFIy6zoNP4k5W3r7B/GI8Mn3f8qoefG55 kZcXp1bTDsi2Dd+KwWfB0wv2XsSiTDiQS1/fvXn3yiwHFkCt13lWiwzmeSiAmFp8rX8sEi6zf2fr HS8rUf/ll883g7nbF2naiHLwKlvnscy2F2y+kjX1+Z/Ba5GJUhH88xVfiYSNhovhFL9+9/0FG9Zp 8SMsRKz/EEXSVNG8Ga4vgslYfdnW0/nXr9gSzFVL2lS12GNLONEApnE8slv+aKoVtIaztrVai6Iu xXB3ES5menSV8aJa8wzHT9ueTcpp2vnE/P6jKGiKSSclb2UmgHYjLG/lF+AJyARw4fT6IvUlETkS M12on9AtD4g6qyGEhvFkrNGwbYxto3FHyOuSP8AKEmFIeV3KL/AHL07T0S5PFFWO648mowPGTx1S ZyMP18Pp8/ZhOteDkQjVNwyjg6bxYVMU9fdwPBp593Ayc7kJ/frcjPqsjCz2VjWtqScJi9EJSbjO k7w0zP85EU15ivHhfLToMXqysGRifTGfBYbRvK6aaidrThsStUNTuS5z4A4uaRoEvS2Iwkn/gLTb MO5Ol+HuojteHXfXFzNL5DruDlp1i/CjwOYy0jWe2myGliia9KQWZpoFDl8nwTTsMzaKph1jX2U7 nq1FCoqmx947Ua5ELconjlo4n7VLK7KUdIHGXooNb5K6MsC3NehHzkvQYsCYJAFscVJRhfP5qIO7 FTWLFSS740kjKjJXwqyArUFllnlSDa21SOhXdfOye/yvyFiesm6BZOOgUy3YHg41UDR8gqS5e6jD edA/1dOJOTqtvIVjn7CNFhOfsHmUQBSOZj5hG036wjafhUayjLx1HT3CNh5HPWEbzeeOaJG8jRez nrB1i2oP9bRTZlr4AkOKkT/A0ZpV5KmoywdLsaoWKU5uwmKsxeyaJ3JVkkNgbTs1ivIJ8VpEkz6M YCsBciVYBtaZIaMM6q85CFws2F2egJjAH/iZ7Z8718y4Py/ebEBy+SoR8TmrdwJQ7+RasHuZJEAA W3fUxB052EmTNGQf4Hd5LytxzgBtbXjAZMUKUcKYFAbnWfJgI2xkWdV4Hsp66Dhhb7JYwrnAE1mB L7IXCRB2n5cxHjqaE/wMWLiPAVvRskCU8RDJuYRPZXU4HNwnAZN0KNAfRNaDcZqPk3nHxw+4unax rNpx9I4G67wswZ10xOHX3MyO/8Mlxs096/oK1sj69KzT0ZHdIxYjb1sCmCHA3Yu4Kemz2ash+wzj AM+j17bgFgL4ZgNeIQP1xcTXIq8a3EeZwq4LiRLAVo1M4gH4qTBkU4JaAzQkBlThRm6bViY2MoEh HAY3lYifvfO1/ALKsmI7IMFIecdI2ljFRxRBm5VbcZeTMCyFR/nS/q8ASu7P4f+3QD0sTeJY+ApY 4MbK9Q68byASSIA+BecJcLAVHPCV43tcTb5RbUigtWKxEjQrnQ1cikABW5WN3NdPCBe4Be02XzV1 DawDoFr0TBjsEy1/n+WO/6dCDdDgk6nWK++bdIVGZqPOX8lT2MG8p1gueVbzhNXdUclgybAPrkax 0KfGKCbA9Epph+fMhPawJn7xZ8wJH/JsOh4Rb0b63G3BHzaQW3SFjw5aGO0fhGHbODvwrHtkave6 bfeDByMfuCZzmTPOtnoGkAw8MTX4CyAs4FAeaHf4ioK97SYfnDOUzYSDzaY9x6979I7gVKDWcrWG Q9sk0tyCk2xmUXJ/dJSWm8uMJ/mWvXYGUyO0PgGixeNNtoZYuRKMzk37N0oHV+hIWicw19dL0BDO zkL8ui3zvMYu4C7ByiUIPwkPjRctId15AIhBBazJy2OkLcaGK2nKLSFSP4+MimyPCxwkvcWvcRi7 9qh8+qKV0lHkie8kETGdHgfNXbchOFujX9w/THE3YCtwiNyiDQOWA8fikoMeq/agmFObBh0PRvO+ 9xaGwWG4dtgUGT0lM247UPhbluzsETRk/eO9rF96J+7HR0HguJcqA3AYdvpDHh1h2+s4iILCsQl5 7KWEh9mDhSfs1DF7F0A6riVlE2YnYsjXjmi/7iktE6EfMEZ77poN0UGyZBIeeuzBZOpJgIx7JOt9 vEl4vRKxbZsPqTNeCKWFCjCC2fqB/ZJJK367kUkKmmonZOzF6IeyQH2PKH1KL5s6h4hFrtkyXzcU ZN0IzHRZOqntAr4AuLFtL3QPwDCjF+Ajwaz6Ixn+O8GQaAO6lNw7LtRmVWy5Z5xqFhvvYK01boDK Chw3tk14ZcWnbXtBKg6/eWEWLkw4nKQp4ys473481QG/Z6eAJ0EvWTTpBE83jPs9JibLpsLMoLO3 bpg5nvtaJ4sjKZBF4GkNAy0V7/PMToUJx2cw65n21xP116MN1U882YC3JdglO/sJfcXP8OOlmUN9 hx2D7+j9+XTapNNgZsI+v8azgwmv2NltvqmPTgjfH1GJ+2ec92fsr3k8P5jxmp29BzG4BXMsMt+U 176pwv7ixloOlyoUANZEXyN2xR9E+fKkGpmEfbqjUQ/sSoHdFrLkyVNoiz5a0EO7VmjeZfsQu/Sm QQx7iEt2Nv8WxEgL72cMotu8F8iZWO8ycAa3lm34LPZVbeW/QE22naTPiE8i7eot8/ssyXnMCl7D WBBXS6VZ30oSZS/W5CjW1QmsKx/WpJ+omgYa/ZNtaT7luc9STCaLAwC9s69LOvbGnuZ+LTAdHWBo wb2CaNdyXBLe3PsgFiOjePy+HvrlPl/PQARuwzTQqueXSqBzvJGZzZIlhpVtzCjwL+oh0bXz4mv5 fJMWfF0PYvCaCxAe2DnLILyD7ZJfTbsHyMgpiHkKAdohCn1R9vYklBbLN9l+8EX4CIIvtfvFg2Ny ZJ8+szQHXyO3MbD1nWr1isC0M2yd5zbup4hPZoi9iEaPy+2OYZJC1g9qFTREOyebuGz2e8z4glXH iGV/zxNZCydwM7haW7/N758Lm/AnYRcOuZSm5lV9EjiFXdlhrNf19gEb62JLMTuj4OcvwXD08lkS 7Q7wTLM4Pc38W6eZ+6aZjfQ010tLvJa+voHWCZcTVuQlsMh2gaGxqjnIkndsYI2lK9s1L4QzOJFb THB6R+uj/lagYrauJ9vf333PsqRyL9ZlIiit112sExx0TNpb5AvgFBz3jJ3F4qVnUuORRxahkZdA fe7BnTed4YdMOU88Q8JxFPSinmgceu8rInOT51xZaL9T31eMZv47ShO2mRhwNpv17yums170ZN1X BHPjuZrbiakbIIYL9yYsWhg7covJm3d5bCf2oCnN48anAsPxTPPUzhPsWpeud99Utx9y5ybJgBmF uizzIm/6V285ps9bPeAH8Ob/YgV2QMy+j+mlKjJ5Mxt0RTUfm
[sane-devel] Preferences in ieee1394 cards for Athlons?
Background: I have two computers in-house: I-Will + dual x86's and an Asus with dual Athlons. I would like to have the Nikon Coolscan 4000 on the athlon box, but cannot get it to recognize the Adaptec unit that came with the Nikon (dual-port NEC, should've been standard). On either the I-Will or Asus boards the ohci driver gives me a nastygram about ohci1394: $Rev: 578 $ Ben Collins ohci1394_0: Unexpected PCI resource length of 1000! ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[db008000-db0087ff] Max Packet=[1024] but at least the unit works on the I-Will. Question: Anyone else out there running a Nikon w/ Asus dual-athon motherboard? If so, any recommendations on cards that are likely to work? thanx -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080
Re[2]: [sane-devel] Problem in setting up Xsane
Hello Stephen, Wednesday, February 26, 2003, 5:23:47 PM, you wrote: SL> Standalone PC SL> OS RH7.3 SL> Xsane installed as standard installation (I have no idea to run its se= tup) SL> IDE Writer SL> IDE CDRom SL> Scanner connected to a ISA SCSI card ok ... SL> as root SL> # cat /proc/scsi/scsi SL> Attached devices: SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00 SL>Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e SL>Type: CD-ROM ANSI SCSI revision: 02 SL> /var/log/messages SL> .. SL> Feb 26 10:20:05 server kernel: scsi0 : SCSI host adapter emulation for= =20 SL> IDE ATAPI devices SL> Feb 26 10:20:05 server kernel: Vendor: SONY Model: CD-RW CRX160= E=20 SL> Rev: 1.0e SL> Feb 26 10:20:05 server kernel: Type: CD-ROM SL> SL> I think the ISA SCSI card is not detected. I think you are right! Try to find out what type of scsi-card you have installed. May be Win helps you with some information from device manager, more or less the scsi chip is the decisive information you should get. With this information you should tell RH to load the appropriate driver for that card. It=B4s very likely that Xsane will work afterwards. Good luck! Holger
[sane-devel] command line gamma value for coolscan2?
Using xsane, I normally set the Gamma value using the coolscan2 backend to "3" for all three colors. Looking at "scanimage", I cannot find any single setting that seems to handle the same option. Am I missing something or is there some doc available which describes building the -gamma-table values from a single- value setting on the command line? --gamma-table 0..255,... Gamma-correction table. In color mode this option equally affects the red, green, and blue channels simultaneously (i.e., it is an intensity gamma table). The description above shows that option --gamma-table expects zero or more values in the range 0 to 255. For example, a legal value for this option would be "3,4,5,6,7,8,9,10,11,12". Since it's cumbersome to specify long vectors in this form, the same can be expressed by the abbreviated form "[0]3-[9]12". What this means is that the first vector element is set to 3, the 9-th element is set to 12 and the values inbetween are interpo- lated linearly. Of course, it is possible to specify multiple such linear segments. For example, "[0]3-[2]3-[6]7,[7]10-[9]6" is equivalent to "3,3,3,4,5,6,7,10,8,6". thanx -- Steven Lembark 2930 W. Palmer Workhorse Computing Chicago, IL 60647 +1 773 252 1080
[sane-devel] Problem in setting up Xsane
Hi Holger, Thanks for your response. Holger Drefs wrote: - snip - > Yes but there should be the scanner as well! This is the machine where > the scanner is attached or? Have you got /dev/sg0 .. sg7? $ su Password: # locate sg0 /dev/sg0 /home/satimis/Mail/trash/cur/1046100409.1798.sg0n:2,S # locate sg7 /dev/sg7 /usr/lib/wine/wine/msg711.drv.so They are there. > There is a net.conf in C:\sane\etc\sane.d or corresponding path in > linux, you should write here the ip-number of the machine where the > scanner is attached. # locate net.conf /etc/sane.d/net.conf It is an empty file having following content it # This is the net config file. Each line names a host to attach to. # If you list "localhost" then your backends can be accessed either # directly or through the net backend. Going through the net backend # may be necessary to access devices that need special privileges. # localhost How to find out the ip-number of the scanner. It is a rather old machine but still working on Windows B.Regards Stephen
[sane-devel] Umax Astra 2200 USB
I was happy to see the Umax Astra 2200 being supported via USB as I had used the scsi interface before but was having problems with my scsi card. However, I am having regular problems getting things to work. I'm using gimp and the xsane plugin. What happens is about 98% of the image will be read in as indicated by the progress meter (and the debug output below) and then xsane freezes and gimp freezes and but the scanner head goes back as if the scan had been completed succesfully. here is the tail end of the debug output (SANE_DEBUG_SANEI_SCSI=255 SANE_DEBUG_UMAX=255). This behavior occurred with the 2.4.18 redhat kernel as well as the stock 2.4.20 kernel, and occurs with various settings of the following umax.conf parameters: scsi-buffer-size-min scsi-buffer-size-max scsi-maxqueue [umax] umax_reader_process: buffer of 45400 bytes read; 71505 bytes to go [umax] umax_queue_read_image_data_req for buffer[0], length = 45400 [umax] Sending SCSI cmd 0x28 cdb len 10, param len 0, result len 45400 [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] SCSI cmd returned 45400 bytes [umax] SCSI command successfully executed [umax] umax_queue_read_image_data_req: id for buffer[0] is 0x818b570 [umax] umax_reader_process: read image data queued for buffer[0] [umax] umax_wait_queued_image_data for buffer[0] (id=0x818b570) [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] umax_reader_process: buffer of 45400 bytes read; 26105 bytes to go [umax] umax_queue_read_image_data_req for buffer[0], length = 26105 [umax] Sending SCSI cmd 0x28 cdb len 10, param len 0, result len 26105 [umax] sane_read: read 4096 bytes [umax] sane_read: read -1 bytes [umax] sane_read: EAGAIN [umax] error in sanei_pv8630_bulkread (got 02) [umax] umax_queue_read_image_data_req: command returned status Error during device I/O [umax] ERROR: umax_reader_process: unable to queue read image data request! [umax] [umax] sane_read: read 3128 bytes [umax] sane_read: read 0 bytes [umax] do_cancel [umax] killing reader_process [umax] reader_process: terminated by signal 15 [umax] reader_process killed [umax] trying to release scanner ... [umax] Sending SCSI cmd 0x17 cdb len 6, param len 0, result len 0 ...and then everything hangs. Then I have to power cycle the scanner to get things to "work" again. Sometimes I'll get 4 scans in a row to work and then twice in a row it won't. I did read somewhere that an odd-numbered buffer caused problems with a different scanner driver...? Leigh -- Leigh Orf KG4ULP Assistant Professor of Atmospheric Sciences University of North Carolina Asheville, NC 28804
[sane-devel] Problem in setting up Xsane
Hi, On Thu, Feb 27, 2003 at 12:23:47AM +0800, Stephen Liu wrote: > Hi Hwnninf, Well, I think my name is written slightly different :-) > Standalone PC > OS RH7.3 > Xsane installed as standard installation (I have no idea to run its setup) You don't need to run any setup for XSane. The only thing you may need to setup is the backends. > IDE Writer > IDE CDRom Ah, IDE not SCSI. So you use idescsi. That's why your IDE device is found in /proc/scsi/scsi. > Scanner connected to a ISA SCSI card > I think the ISA SCSI card is not detected. Yes. So what did you do to load the driver and what happened? It's explained in detail in the HTML page you referred to in your first post. (Telling the computer about SCSI). You have the same card as mentioned in this article? Bye, Henning
[sane-devel] xsane don't save position
call: xsane --save Oliver On Wednesday 26 February 2003 00:07, Stian Jordet wrote: > man, 2003-02-24 kl. 17:09 skrev Christoph Knauer: > > Thaths right, what I mean is which windows are opened and in's positi= on, > > or which windows are closed. > > Speaking of.. I don't have mr. Knauer's problem, but every time I start > xsane it starts in Viewer mode, but I only use "save"-mode. Is it > possible to achieve that, somehow? > > Regards, > Stian > > ___ > 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] backend naming conventions/constraints
Hi, Silly question but are there any constraints on the name of a backend? I am in the middle of switching "Image Scan!"s backend from epson to epson-kowa and ran into the BACKEND_NAME macro ;-) Is there any harm in calling the backend library libsane-epson-kowa.* while defining the macro to epson_kowa? TIA, -- Olaf MeeuwissenEPSON KOWA Corporation, ECS GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
Re[2]: [sane-devel] Problem in setting up Xsane
Hello Henning, Wednesday, February 26, 2003, 2:29:44 PM, you wrote: HMG> [net.conf] >> You should remove the '# ' before localhost, if you are using Xsane on >> the same machine where the scanner is attached. HMG> Maybe I'm missing something here, but why shouldhe use saned / HMG> net.conf at all? You can use saned as a workaround to not be root, but HMG> that's only relevant for parport scanners. Oh sorry, I thought its always working in network mode. I came to sane because of the network capabilities, never thought about using it only locally where the scanner is attached. Have a nice day Holger
[sane-devel] Canon-SCSI
The Canon SCSI backend now supports the FB1200S flatbed scanner. The crashes with Mandrake Linux and the problems with the preview of xscanimage mentioned in previous postings have been resolved. The revised backend has been committed to CVS. Ulrich Deiters
[sane-devel] Problem in setting up Xsane
Hi, On Wed, Feb 26, 2003 at 01:57:25PM +0100, Holger Drefs wrote: [net.conf] > You should remove the '# ' before localhost, if you are using Xsane on > the same machine where the scanner is attached. Maybe I'm missing something here, but why shouldhe use saned / net.conf at all? You can use saned as a workaround to not be root, but that's only relevant for parport scanners. Bye, Henning
[sane-devel] Problem in setting up Xsane
Hi, On Wed, Feb 26, 2003 at 06:38:59PM +0800, Stephen Liu wrote: > >Yes but there should be the scanner as well! This is the machine where > >the scanner is attached or? Have you got /dev/sg0 .. sg7? > > $ su > Password: > # locate sg0 > /dev/sg0 Ok. Please tell us more about your system: - Which SCSI card is used for your scanner? - Is the SCSI driver for this card loaded? - Is your SCSI cdrom connected to the same SCSI card or a different one? Your problem is not related to xsane (that's "just" the graphical application, the scanner access is done in the SANE backends). It's a problem of your kernel or hardware. First make sure that your scanner is detected in /proc/scsi/scsi, then you can go on with sane-find-scanner, scanimage and xsane. > >There is a net.conf in C:\sane\etc\sane.d or corresponding path in > >linux, you should write here the ip-number of the machine where the > >scanner is attached. > > > # locate net.conf > /etc/sane.d/net.conf Ignore net.conf. At least if you don't want to use SANE over the network, you don't need it. Bye, Henning
Re[2]: [sane-devel] Problem in setting up Xsane
Dear Stephen, can you pls tell your general setup. Is that like: linux-machine with scsi-card attached 1 cd-rom, 1 scanner Xsane running on this machine? Wednesday, February 26, 2003, 11:38:59 AM, you wrote: SL> - snip - >> Yes but there should be the scanner as well! This is the machine where >> the scanner is attached or? Have you got /dev/sg0 .. sg7? SL> Password: SL> # locate sg0 SL> /dev/sg0 SL> # locate sg7 SL> /dev/sg7 SL> They are there. ok. SL> It is an empty file having following content it SL> # This is the net config file. Each line names a host to attach to. SL> # If you list "localhost" then your backends can be accessed either SL> # directly or through the net backend. Going through the net backend SL> # may be necessary to access devices that need special privileges. SL> # localhost You should remove the '# ' before localhost, if you are using Xsane on the same machine where the scanner is attached. You must insert the ip-adress of the machine where the scanner is attached if it is a different machine. SL> How to find out the ip-number of the scanner. It is a rather old SL> machine but still working on Windows ??? There is no ip-number for a scanner, only for machines in the network. WHat do you mean with "but still working on windows"? Cheerio, Holger
[sane-devel] Alpha version for hp5400 backend
--mR8QP4gmHujQHb1c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 26, 2003 at 12:14:31AM +0100, Henning Meier-Geinitz wrote: > > Feel free to test it and submit bug fixes, improvements >=20 > I would like to add the .desc file to CVS (external backends) so your > backend is found in the scanner search engine. I've edited your file a > bit. If you write one entry for each model, it's found easier (nobody > seaches for 54xx). Do you have a 5400 and 5470? As far as I know, the > 5490 is similar, therefore I've added it as "untested". Is this > correct? Heh, the desc file was there, is just isn't in CVS. We have a 5400 and a 5470c and the only difference we've seen so far is the version number returned. Maybe we need to check the HP site to see what the differences are. :) Never seen a 5490. Anyone got one? Anyway, thanks for the file. --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. --mR8QP4gmHujQHb1c 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+XBJBY5Twig3Ge+YRAvPlAJ9lRpya2thjwJ9EsVpX616anj+elgCgn/sG d22arHNCcIaI6bXikb1DHJE= =H2DJ -END PGP SIGNATURE- --mR8QP4gmHujQHb1c--
[sane-devel] Assistance
Hi, On Wed, Feb 26, 2003 at 10:09:50AM +0530, ionm...@indiainfo.com wrote: > Can I ask questions regarding actual scanning problems after > successful installation or is there a separate group/list for that? Despite its name, this list is for everything related to SANE. So if your scanning problem happens when using SANE, it's ok to ask. Bye, Henning
[sane-devel] Alpha version for hp5400 backend
Hi, On Wed, Feb 26, 2003 at 12:02:58PM +1100, Martijn van Oosterhout wrote: > Heh, the desc file was there, is just isn't in CVS. Sorry for confusion. I did use your desc file (from the .tar.gz) and just modified it a bit. With comitting it to CVS I meant SANE CVS, not your CVS. If it's in SANE CVS, it will be automatically pulled by the scanner search engine and users will find a link to your backend when searching for hp 5400. > Anyway, thanks for the file. I'll add it to SANE CVS. Bye, Henning
[sane-devel] xsane don't save position
Hi, On Wed, Feb 26, 2003 at 12:07:20AM +0100, Stian Jordet wrote: > Speaking of.. I don't have mr. Knauer's problem, but every time I start > xsane it starts in Viewer mode, but I only use "save"-mode. Is it > possible to achieve that, somehow? I don't think that you can save the mode. However, you can set the mode by an option: xsane --save Now create an alias or script with that option and you're dobne. Bye, Henning
[sane-devel] backend naming conventions/constraints
Hi,
On Wed, Feb 26, 2003 at 03:12:24PM +0900, Olaf Meeuwissen wrote:
> Silly question but are there any constraints on the name of a backend?
It shouldn't be too long, but epson_kowa is ok in this respect. It
shouldn't contain any characters that can't be used in the filesystem.
And it should be usable as a C identifier, that means it shouldn't
contain " ", "-" or any other charatcers that aren't allowed to be
used in identifiers.
The reason is that if you link more than one backend statically
("preload"), the symbols must be different (sane_gt68xx_init,
sane_mustek_init etc.). So the backend name is used in the symbol.
> I am in the middle of switching "Image Scan!"s backend from epson to
> epson-kowa and ran into the BACKEND_NAME macro ;-) Is there any harm
> in calling the backend library libsane-epson-kowa.* while defining the
> macro to epson_kowa?
I wouldn't do that. I haven't really checked the implications but that
may collide with one of the hacks used to enable static/shared linkage
and dynamic loading.
Why don't you use "libsane-epson_kowa" or "libsane-epsonkowa"?
Bye,
Henning
[sane-devel] Problem in setting up Xsane
Hi Oliver, Thanks for your response. Oliver Schwartz wrote: - snip - > Is your SCSI card recognised in Linux (i.e. what's the output of > "cat /proc/scsi/scsi")? $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e Type: CD-ROM ANSI SCSI revision: 02 It looks the SCSI card detected. > If so, does sane-find-scanner find your scanner? No $ sane-find-scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. # You may want to run this program as super-user to find all devices. # Once you found the scanner devices, be sure to adjust access # permissions as necessary. # If your scanner uses SCSI, you must have a driver for your SCSI # adapter and support for SCSI Generic (sg) in your Operating System # in order for the scanner to be used with SANE. If your scanner is # NOT listed above, check that you have installed the drivers. > I don't know where xsane got the "setup" device. Did you specify any > command line arguments? (You shouldn't). I am searching around the "setup" device/step for xsane. I have been looking around its website either. Can any folk on the list help B.Regards Stephen Liu
Re[2]: [sane-devel] Problem in setting up Xsane
Hello Stephen, Wednesday, February 26, 2003, 3:42:29 AM, you wrote: >> Is your SCSI card recognised in Linux (i.e. what's the output of >> "cat /proc/scsi/scsi")=3F SL> $ cat /proc/scsi/scsi SL> Attached devices: SL> Host: scsi0 Channel: 00 Id: 00 Lun: 00 SL>Vendor: SONY Model: CD-RW CRX160E Rev: 1.0e SL>Type: CD-ROM ANSI SCSI revision: 02 SL> It looks the SCSI card detected. Yes but there should be the scanner as well! This is the machine where the scanner is attached or=3F Have you got /dev/sg0 .. sg7=3F Forget about sane-find-scanner before your scanner isn=B4t shown here. >> I don't know where xsane got the "setup" device. Did you specify any=20 >> command line arguments=3F (You shouldn't). SL> I am searching around the "setup" device/step for xsane. I have been SL> looking around its website either. There is a net.conf in C:\sane\etc\sane.d or corresponding path in linux, you should write here the ip-number of the machine where the scanner is attached. Best regards, Holger Drefs
[sane-devel] Assistance
Can I ask questions regarding actual scanning problems after successful installation or is there a separate group/list for that? -- __ http://www.indiainfo.com Now with POP3/SMTP access for only US$14.95/yr Powered by Outblaze
[sane-devel] Question about non-blocking
--Xm/fll+QQv+hsKip Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable SANE supports a backend being non-blocking. Does that mean "don't ever block" or "don't ever block for long periods of time"? For example, the warming up of the lamp can take a while so you'd like to support non-block for that. OTOH, we can't support non-block for the USB reads and writes. But they don't take very long. Is it acceptable to claim to support non-block if you block only for small periods? --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. --Xm/fll+QQv+hsKip 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+W+5wY5Twig3Ge+YRApHkAJ9YK/2t/ZzsCeLfmnyO6dnt1n9DdQCgropJ 6Zqk4izJkt89n/fwRRyQA1I= =wK/G -END PGP SIGNATURE- --Xm/fll+QQv+hsKip--
[sane-devel] Alpha version for hp5400 backend
> > I would like to add the .desc file to CVS (external backends) so your > backend is found in the scanner search engine. I've edited your file a Oops, error. It should be in CVS. > bit. If you write one entry for each model, it's found easier (nobody > seaches for 54xx). Do you have a 5400 and 5470? As far as I know, the > 5490 is similar, therefore I've added it as "untested". Is this > correct? Status is development under way with untested alpha release. I forgot to mention that it has only been compiled for the moment under l= inux=20 and can probably break on other OS.
[sane-devel] Alpha version for hp5400 backend
Hi, > > Heh, the desc file was there, is just isn't in CVS. We have a 5400 and = a > 5470c and the only difference we've seen so far is the version number > returned. Maybe we need to check the HP site to see what the difference= s > are. :) I think they are similar scanners just with more options : * 5470 =3D 5400 + XPA (for film rolls and diapositives) * 5490 =3D 5470 + ADF (auto feeder)
[sane-devel] Problem in setting up Xsane
Hi all folks, Desktop KDE Scanner Agfa Snapscan 310 This is the first time I tried to setup Xsane for scanning on Linux. As user on console window # xsane After acepting the licence following Error warning popup Failed to open device 'setup' Invalid argument. Following URL provides a good example to setup this scanner but working on SANE which has not been installed as standard installation http://216.239.53.100/linux?q=cache:7fp6J492cE0C:duvet.eee.nottingham.ac.uk/scanner/snapscan_310_linux.html+How+to+install+scsi+scanner+on+Xsane&hl=en&ie=UTF-8 In addition it requires to make jumper setting on the SCSI card but my SCSI card coming with the scanner does not have jumpers. Any folks on the list have experience? Kindly advise. Thanks in advance. B.Regards Stephen Liu
[sane-devel] HP5400 status update
--mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Thanks to Thomas Soumarmon it now actually works as a backend to xsane. It spits up an error about too much data, but hey, it displays a picture, right? I've also updated the code a fair bit to remove a bit of duplication. I'm s= till not totally happy with it but it's much better. The source is now available through CVS on the project on sourceforge (http://sourceforge.net/projects/hp5400backend/) in addition to the snapshots on my homepage.. No, I havn't fixed issues with linking statis vs dynamic so don't ask. That's it for today, see you all tomorrow. --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Support bacteria! They're the only culture some people have. --mYCpIKhGyMATD0i+ 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+W3U9Y5Twig3Ge+YRApw/AKCOJ6lIgXIcWb5aMGp73woQZaltUwCePlqZ UbhZIpgmFWKL6+gyf1ZTseo= =/Ryj -END PGP SIGNATURE- --mYCpIKhGyMATD0i+--
[sane-devel] Question about non-blocking
Hi, On Wed, Feb 26, 2003 at 09:30:08AM +1100, Martijn van Oosterhout wrote: > SANE supports a backend being non-blocking. Does that mean "don't ever > block" or "don't ever block for long periods of time"? For example, the > warming up of the lamp can take a while so you'd like to support non-block > for that. OTOH, we can't support non-block for the USB reads and writes. But > they don't take very long. The non-blocking mode is only relevant for sane_read. As warm-up is ususally done in sane_start, it's not really relevant here. Non-block means: if you have no data, return immediately. Blocking means: Only return if you have at least one byte of data (or an error occured). Bye, Henning
[sane-devel] Alpha version for hp5400 backend
--wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, On Tue, Feb 25, 2003 at 11:05:05PM +0100, Thomas Soumarmon wrote: > Thanks to Martijn van Oosterhout, an alpha version of the SANE backend for > HP5400 scanners is available for download at > http://sourceforge.net/projects/hp5400backend Nice! > As it is alpha code, it is buggy and of interest only for development > purposes. > > Feel free to test it and submit bug fixes, improvements I would like to add the .desc file to CVS (external backends) so your backend is found in the scanner search engine. I've edited your file a bit. If you write one entry for each model, it's found easier (nobody seaches for 54xx). Do you have a 5400 and 5470? As far as I know, the 5490 is similar, therefore I've added it as "untested". Is this correct? Bye, Henning --wac7ysb48OaltWcw Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="hp5400.desc" ; Copied from hp3300 testtools - Martijn van Oosterhout 22/02/2003 ; SANE Backend specification file ; ; It's basically emacs-lisp --- so ";" indicates comment to end of line. ; All syntactic elements are keyword tokens, followed by a string or ; keyword argument, as specified. ; ; ":backend" *must* be specified. ; All other information is optional (but what good is the file without it?). ; :backend "hp5400" ; name of backend ;:version "(0.1)" ; version of backend :status :alpha ; :alpha, :beta, :stable, :new ;:manpage "sane-hp5400" ; name of manpage (if it exists) :url "http://sourceforge.net/projects/hp5400backend"; ; backend's web page :comment "HP5400 and HP5470 scanners. Prototype backend available" :devicetype :scanner; start of a list of devices ; other types: :stillcam, :vidcam, ; :meta, :api :mfg "Hewlett-Packard" ; name a manufacturer :url "http://www.hp.com"; :model "ScanJet 5400" ; name models for above-specified mfg. :interface "USB"; interface type of the device: ; "SCSI", "USB", "Parport (EPP)", ; "Parport (SPP)", "Parport (ECP)", ; "Serial port" or "Propretiary". :status :alpha :model "ScanJet 5470" ; name models for above-specified mfg. :interface "USB"; interface type of the device: :status :alpha :model "ScanJet 5490" ; name models for above-specified mfg. :interface "USB"; interface type of the device: :status :untested ; :comment and :url specifiers are optional after :mfg, :model, :desc, ; and at the top-level. --wac7ysb48OaltWcw--
[sane-devel] xsane don't save position
man, 2003-02-24 kl. 17:09 skrev Christoph Knauer: > Thaths right, what I mean is which windows are opened and in's position, > or which windows are closed. Speaking of.. I don't have mr. Knauer's problem, but every time I start xsane it starts in Viewer mode, but I only use "save"-mode. Is it possible to achieve that, somehow? Regards, Stian
[sane-devel] .fr.po - second snapshot - final
Hi, On Tue, Feb 25, 2003 at 10:50:26PM +0100, Yann E. MORIN wrote: > So here are the latest translations for french (attached). A little bit of > improvements thanks to (out of order!) : Stef, Henning and Frank. Thanks. By the way, the German translation: Translated : 533 (95.2%) (of which 16 fuzzy ( 3.0%)) Not translated : 27 ( 4.8%) Total : 560 > Henning, will you please apply that one? Thanx! Ok. make results in: generating sane-backends.fr.mo from sane-backends.fr.po sane-backends.fr.po:2098: end-of-line within string /usr/local/bin/msgfmt: found 1 fatal error One " missing :-) > What is the next step in french translations? I plan on getting the .fr.po > from cvs Anoncvs is not working currently. And I don't know when and if it will work again. > on a regular basis from a cron job, and have it checked against my > small script, and whenever the number of untranslated/fuzzy messages rise > above a certain value, I'll have a mail sent to me telling me : > "Hey boy, move your ass and check the translations for SANE!" > > Would a "0 0 1,16 * *"-job be enough? I guess it would be enough to check two weeks before every release. After that data the backends won't change much. Generally, you will only get major changes if a new backend is included and this backend does unusual stuff. E.g. the latest addition (ma1509) didn't need any additional translation because everything was already translated. > What would be a sensible high-water level for untranslated messages? (10%?) > And the high-water level for fuzzy translations? (5%?) That's ok. But I wouldn't be too strict with numbers. If you get the translation of "Gray" wrong everybody will notice. But nobody may find out about a wrong translation of "Dither 2x16 squared pattern" that's only used in a seldomly-used backend. So not only quantity counts. > How are the fuzzy messages tagged as fuzzy? Subsidiary question : who tags > them as fuzzy? #, Either you do it manually if you aren't sure about the translation or msfmerge does it when updating the po file from the backends. E.g. if the untranslated text changes from "Color" to "Colour" the translation of the original will be made fuzzy. If you think the translation is correct, just remove the fuzzy marker. Thanks again. Bye, Henning
