> the question is if we should include functions like JPEG->PNG conversion
> in each backend that needs it or should we make filters that work as
> a "midend" (like sane-dll) that does the conversion.
There are arguments both for "simple" library functions callable by
backends and for the more complex approach to use "midends". But after
this not very pleasant development of the "Sane version 2" debate in the
last weeks I would like to leave the question, how and where to make
format conversions for a while. I prefer to collect more similar
questions, so that we can see which approach seems to be more promising,
regarding complexity (or, better, avoiding complexity...), versatility
and expandability of the Sane standard.
> I don`t know if it is a good idea to include language support into the backend.
> I think all the work should be done by the frontend. We only need a
> translation table. The rest can be done by NLS/gettext.
Well, it seems that my suggestion was indeed too complex...
Abel
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com