Henning Meier-Geinitz wrote:
[snip]
>
>
>> but not a scanning application either,
>
> Come on.
In the context of scanning negatives and films using high end scanners
xsane is not scanning application but a toy.
>
>> its results are useless. Take this as a fact which we can debate
>> e
> Err... excuse me? I don't think the amount of money any of the SANE
> developers makes from SANE development justifies any effort on this
> behalf.
I am aware of that, and I wasn't asking the sane developers for any
effort, unless you count brain-picking as effort.
> No, there goes "Vuescan i
Hi Mr. Kuhlmann,
I was the one to bring up the issue with the SPARC workaround, the sane folks
helped me a lot to do the testing and find out that using the "old" interface
made everything work.
And, as a matter of fact, everything on SPARC64 is compiled 32 bit in the user
world. Only the kerne
Hi,
On 2006-01-08 19:40, Jon Chambers wrote:
> I don't see any "#ifdef WIN32" in the SANE code so I don't think that is a
> target platform.
See README.windows...
Bye,
Henning
Hi,
On 2006-01-09 09:54, Volker Kuhlmann wrote:
> 1) sane is an API for scanners which works
> 2) sane is *NOT* a scanning application, i.e. some software which gets
>some scanning work done.
sane-backends is not. Frontends like scanimage, xscanimage and xsane
are.
> 3) xsane is a GUI around
Hi,
> He doesn't want to recompile
> for 64bit because the amount of money he makes from the Linux
> version doesn't justify it.
Err... excuse me? I don't think the amount of money any of the SANE
developers makes from SANE development justifies any effort on this
behalf.
> I can understand yo
> > Most annoying that it doesn't work with SCSI scanners on 64bit machines,
> > something a recompile would fix. Hence my recent question about write()
> > encapsulation in sanei_scsi.c (which no-one replied to :( ).
> If somebody else needs such a special handling because of the
> binary-only na
Hi again,
On 2006-01-08 17:00, Henning Meier-Geinitz wrote:
> formats) and therefore help to identify a USB scanner exactly. The
> second reason for adding these ids to the description files is to
> generate the lists for hotplug/udev events (e.g. libsane.usermap)
> automatically from the descript
Hi Alessandro,
On Sun, 8 Jan 2006, Alessandro Zummo wrote:
> I agree. I only know of unix sockets, so probably the first version won't work
> straight on windows...
I don't see any "#ifdef WIN32" in the SANE code so I don't think that is a
target platform. Nonetheless there are MaC OS and OS2
On Sun, 8 Jan 2006 15:16:38 + (GMT)
Jon Chambers wrote:
> This could be useful. What scanner are you working on and what stage are
> you at? Do you know the network protocol? Do you have a working
> prototype? Have you made a start on a SANE backend?
Epson CX11NF. The protocol is ESC/
Henning Meier-Geinitz wrote:
> Hi,
>
> On 2006-01-08 14:27, Volker Kuhlmann wrote:
>>Most annoying that it doesn't work with SCSI scanners on 64bit machines,
>>something a recompile would fix. Hence my recent question about write()
>>encapsulation in sanei_scsi.c (which no-one replied to :( ).
>
Hi Alessandro,
On Sun, 8 Jan 2006, Alessandro Zummo wrote:
> SANE actually misses a network transport and, since I'm dealing
> with a network capable MFP too, we can maybe coordinate the
> efforts to create and test one. Let me know if you're interested.
This could be useful. What scanner are
Hi developers,
The format of the SANE description files (.desc) has been changed to
allow the addition of USB vendor and product ids to each model entry.
These ids will be shown in the HTML lists (and all other output
formats) and therefore help to identify a USB scanner exactly. The
second reason
Hi,
On 2006-01-08 14:17, Andrei V. Toutoukine wrote:
> OK, I'd like to try. Should I contact the manufacturer for protocol
> details or maybe someone has these already?
Asking is always a good idea. If they don't have a protocol
description, maybe they can give you the source code of the windows
On Sat, 7 Jan 2006 22:31:05 + (GMT)
Jon Chambers wrote:
> I have written a driver for network scanning using a Dell 1600n MFP. It
> is implemented as a perl script and can be found here:
> http://www.jon.demon.co.uk/dell1600n-net-scan/
>
> I am currently in the process of figuring out how
Hi,
On 2006-01-07 05:15, Aurelien Jarno wrote:
> -#if defined(__linux__) || defined (HAVE_SYS_HW_H)
> +#if defined(__GLIBC__) || defined (HAVE_SYS_HW_H)
But this means that Linux without glibc won' work, which is the reason
for this one:
> #elif HAVE_ASM_IO_H
> # include /* older Linu
sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060108/1f2cbc07/attachment.htm
From henn...@meier
Hi Torsten,
waiting for linux log for Hp2300c from you. if you got it
please send me it to my email.
Regards,
Parag.
On 1/8/06, Torsten Evers wrote:
> Hi Parag,
>
> Am Sonntag 08 Januar 2006 01:53 schrieb
> sane-devel-requ...@lists.alioth.debian.org:
> > Message: 1
> > Date: Sat, 7 Ja
On Sat, 7 Jan 2006, Henning Meier-Geinitz wrote:
>> of creating (or extending) the SANE back-end?
> See SANE website, section Contributing. See also the archive of this
> mailing list for similar questions about writing backends.
OK, I'd like to try. Should I contact the manufacturer for protoco
Hi Parag,
Am Sonntag 08 Januar 2006 01:53 schrieb
sane-devel-requ...@lists.alioth.debian.org:
> Message: 1
> Date: Sat, 7 Jan 2006 18:09:16 +0530
> From: Parag N()
> Subject: [sane-devel] require Hp2300C linux debug messages
> To: sane-devel@lists.alioth.debian.org
> Message-ID:
>
>
Hi,
On 2006-01-08 00:05, Ben Tasker wrote:
> I recently posted on this list about a Xerox 4800 flatbed scanner. After a
> little investigation it would seem that Xerox have simply rebranded the
> Visioneer 4800 scanner. If the Visioneer 4800 one touch is ever supported I
> assume the Xerox will be
Hi,
On 2006-01-08 14:27, Volker Kuhlmann wrote:
> Most annoying that it doesn't work with SCSI scanners on 64bit machines,
> something a recompile would fix. Hence my recent question about write()
> encapsulation in sanei_scsi.c (which no-one replied to :( ).
I didn't answer because I'm not reall
Hi,
On 2006-01-08 10:16, Julien BLACHE wrote:
> > 2. The Dell 1600n sends data back in CCITT Fax Group 4 or JPEG formats
> > (for monochrome or colour scans respectively). To convert this to an
> > array of RGB data will require converstion via an external library
> > (eg: libjpeg). Is this extr
Jon Chambers wrote:
Hi,
> 1. Hopefully trivial: I have written a dummy backend and sym-linked
> it to /usr/lib/sane/libsane-dell1600n-net.so. How can I get a SANE
> frontend to find it?
Add dell1600n to /etc/sane.d/dll.conf.
> 2. The Dell 1600n sends data back in CCITT Fax Group 4 or JPEG fo
> hangs the SCSI bus. On the other hand the vuescan does a good job with
> it (too bad it's not free and not open source).
Hm, vuescan is reasonably priced, has a user interface, supports it8
targets, process calibration and reasonably good infrared cleaning, and
most importantly, actually works..
PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060108/7b7dd185/attachment.htm
From photopi...@interia.pl Sat Jan 7 23:48
26 matches
Mail list logo
