[sane-devel] Encoding of backend translations

[Henning Meier-Geinitz]

Hi,

On Fri, Mar 01, 2002 at 02:12:21PM +0100, mh wrote:
> I'd just like to ask, whether it would be a problem to use UFT8 encoding for 
> the backend translations?
> Reason:
> The KDE i18n framework has been switched to UTF8; .mo files generated from 
> .po files encoded e.g. in iso-8859-1 are not displayed correctly (missing 
> "Umlaute"/vowel mutations). 
> As far as I know, this wouldn't affect xsane (Oliver?), but would make access 
> to the backend translations much easier for KDE applications.

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.

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?

Is this supported by the (X)Emacs po mode/mule? I could convert the
files using iconv but can't check the result for correctness.

Bye,
  Henning