Re: SANE_FRAME Formats (was Re: xsane-0.31 available)

Nick Lamb (njl98r@ecs.soton.ac.uk)
Wed, 4 Aug 1999 05:41:10 +0100 (GMT)

Am I fighting a losing battle here?

Why is it so desirable to have

This..... Instead of this...

SANE_FRAME_RAW SANE_FRAME_G3
SANE_FRAME_RAW SANE_FRAME_G4
SANE_FRAME_RAW SANE_FRAME_JFIF
SANE_FRAME_RAW SANE_FRAME_RGBI
SANE_FRAME_RAW SANE_FRAME_TEXT

How about...

SANE_FRAME_RAW SANE_FRAME_RGB
SANE_FRAME_RAW SANE_FRAME_GREY
SANE_FRAME_RAW SANE_FRAME_BLUE

Under what circumstances is it preferable NOT to know what kind of data
we are dealing with? Are default: labels in switch blocks suddenly being
taxed by the US government?

Maybe I'm being REALLY REALLY STUPID here, but I can't see any down side
to knowing what the **** was in the data stream before someone like
Oliver decides to turn it into a JPEG and save it in a file.

If you have some genuinely unexplained data, which can't be classified,
what makes you think anyone wants to process it anyway?

Nick.

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com