> I think we will save one image to one file.
> For sane-2.0 I suggest to add a "comment" string to the
> parameter block, the backend can write any comment, into
> it and if the filetype allows comments in the header, the frontend
> saves the comment to the file.
>
> If we have different images, we will save them to different
> files so we call a new sane_start.
>
> If there is an audio stream or something else that shall be saved with the
> image into one file, that can be done with a raw format that is generated
> by the backend and the frontend simply saves the file.
OK, I made things again more complicated than necessary... So, the only
remaining questions are about different frame formats (no, don't want to
discuss them right now ;) and the uncertainities about some details of
the semantics of sane_start, sane_cancel and related stuff. Since I'm
working only on a very "stupid" scanner compared with these Bell &
Howell machines, I will not make any further comments. (I hate backseat
drivers, so I'll try to avoid this role ;)
Abel
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com