Re: Internationalized Sane

David Mosberger-Tang (David.Mosberger@acm.org)
Fri, 2 Apr 1999 17:19:51 -0800

>>>>> On Wed, 17 Mar 1999 14:24:20 +0100, Andre Herms <aherms@prinz-atm.CS.Uni-Magdeburg.De> said:

Andre> So I have some little problems:

Andre> 1) How shall SANE_Language be changed. - it could be done by
Andre> the frontend - it could be a new param to SANE_Init ? - it
Andre> could be made an extra Option ( best compatible way for me)

Andre> 2) Where shall the Strings be stored - it could be put in a
Andre> header-file. but the more strings, the bigger the resulting
Andre> file gets and it uses RAM. - it could be stored to an extra
Andre> text file. but than there must be some functions for
Andre> reading. And where to store this file.

Andre> I'd like to get some suggestions, whats the easiest way not
Andre> to change all backends or the Sane-standard

I think it would be best to put the language functionality in the
frontend since the frontend needs to be internationalized at any rate.
Also, suppose a user in Germany accesses a scanner in the US---would
it be realistic to expect for the scanner to provide a German user
interface?

I think GNU gettext guides the way in how to do this: use the english
strings (e.g., "brightness") as keywords into the database that
contains the translation.

--david

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