[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-extra-gear
Subject:    Re: [Kde-extra-gear] libksane release getting closer
From:       John Layt <johnlayt () yahoo ! com ! au>
Date:       2008-01-16 22:34:28
Message-ID: 200801162234.28350.johnlayt () yahoo ! com ! au
[Download RAW message or body]

On Monday 14 January 2008, Kåre Särs wrote:
> 1) Most strings for the sane options come from libsane. What is the best
> way to get translations for strings coming from non KDE libraries?

Umm, I'm no expert on i18n, so I could have entirely the wrong end of the 
stick here, but Sane has some languages translated:

http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/po/?cvsroot=sane

And according to the README file in there:

http://alioth.debian.org/plugins/scmcvs/cvsweb.php/sane-backends/po/README?rev=1.9;content-type=text%2Fplain;cvsroot=sane

Frontend developers: I want to add internationalization support for my 
frontend
-------------------------------------------------------------------------------

* The Makefile installs files called "sane-backends.mo" in the directory
  "$(prefix)/share/locale/lang/LC_MESSAGES/", e.g.:
  "/usr/local/share/locale/de/LC_MESSAGES/sane-backends.mo". For every
  language exactly one .mo file is installed. Earlier releases of
  sane-backends installed one file per backend, e.g. sane-umax.mo. For
  backward compatibility, frontends may want to check for these files, also.
* As mentioned above, GNU gettext is used. 
* With other NLS implementations, converting the mo files may work.


How you hook that up to the KDE i18n is beyond me, but I would assume this 
sort of situation has popped up before, perhaps try the i18n mailing list?

John.

--

Send instant messages to your online friends http://au.messenger.yahoo.com 
_______________________________________________
Kde-extra-gear mailing list
Kde-extra-gear@kde.org
https://mail.kde.org/mailman/listinfo/kde-extra-gear

[prev in list] [next in list] [prev in thread] [next in thread]