I think get gets time to return to an objective discussion.
The sound on this list - especally the sound of YOUR mails -
got very bad the last weeks.
Please everybody, calm down and let's have objective discussions.
In my opinion Andreas is right that it is a bad idea to
add each frame format to enum SANE_FRAME_*.
It is much more simple to extend the standard to support
new formats when we define the frame format in a string.
The question is if the string has to be a string defined by MIME.
I did not read the MIME specs but as far as I know there are
a lot of formats listed and MIME allows to extend the definition
by eXperimental types.
So the question is do we define a new standard that has to be
extended step by step in the future or do we use a subset of an
existing standard.
We also could say we use the mime type definitions where they
make sense so frontends and other applications can take
advantage of this and we define our own definitions
like "sane/rgbi" where this makes sense.
Bye
Oliver
-- EMAIL: Oliver.Rauch@Wolfsburg.DE WWW: http://www.wolfsburg.de/~rauch
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com