Hello,
On Thursday 15 December 2011 06:40:32 Stef wrote:
Le mercredi 14 d?cembre 2011 10:17:38 K?re S?rs a ?crit :
Hi,
While testing the 16 bit features of Skanlite I noticed a problem with
endianness. If I scan directly with epson2 on a x86 I get one byte
order,
but if I do a
actually, the wikipedia page says this:
Unfortunately it appears that the various implementations could not
agree on which byte order to use, and some connected the 16-bit
endianness to the pixel packing order.[5] In Netpbm, the de facto
standard implementation of the PNM formats, the most
Le mercredi 14 d?cembre 2011 10:17:38 K?re S?rs a ?crit :
Hi,
While testing the 16 bit features of Skanlite I noticed a problem with
endianness. If I scan directly with epson2 on a x86 I get one byte order,
but if I do a network scan through saned+epson2 running on a PowerPC I get
the other
Hi,
While testing the 16 bit features of Skanlite I noticed a problem with
endianness. If I scan directly with epson2 on a x86 I get one byte order, but
if I do a network scan through saned+epson2 running on a PowerPC I get the
other order
Is there a workaround for this?
Ideally I would
