[sane-devel] Encoding of backend translations

[Sergey Vlasov]

On Fri, 1 Mar 2002 17:00:34 +0100
mh <crapsite@gmx.net> wrote:

> > I didn't look into the details here, but the po files
> > include a Content-Type header, so it's up to KDE to convert
> > the charset into something it likes in my opinion.
> 
> Hmm, but at runtime, you normally load the .mo file, .po files
> are not part of the sane installation and probably will not be
> available if someone installed sane rpms, or am I missing
> something ?

The "header" part is included as the translation for "".

> I don't know, why KDE handles it the way it does; but after I
> asked for help, the reply I got was: "encode your .po files in
> utf8" Therefore it would be nice, if we could find a solution
> that works for all parties. (if possible at all)

Does bind_textdomain_codeset(backend_name, "UTF-8") help?

> > I'm not sure how easy/complicated it's to convert and edit
> > the existing files using UTF8 and if there are any problems
> > with older versions of gettext. E.g. does gettext convert
> > the trenslations back to iso-8859-1 (or whatever) if used in
> > a (non-gtk) program?

Newer gettext does this, as I have noted already.  In could
event convert to UTF-8 itself, if requested.