Hi,
I see many attempts of translation of doc, tcl/tk gui , but don't see a lot of things lead to term.
Does GRASS community already think about having structure for i18n ? I think it could be helpful.
Wha do you think about using PO files for all translation tasks. It seems to work great in other project.
Jean-Denis
Jean-Denis Giguere wrote:
I see many attempts of translation of doc, tcl/tk gui , but don't see a
lot of things lead to term.Does GRASS community already think about having structure for i18n ? I
think it could be helpful.Wha do you think about using PO files for all translation tasks. It
seems to work great in other project.
Alex Shevlakov has previously done some I18N work on GRASS. The
necessary infrastructure is present, in terms of the --with-nls
configure switch, the glocale.h header, and the _() macro which it
defines. AFAICT, this only works in 5.0/5.3 at present.
So far, the PostgreSQL modules, libgis, libraster, s.surf.rst and
v.digit have been modified to use gettext, while tcltkgrass and the
startup messages have been translated directly.
Currently, only Russian translations are included. See the locale
directory for the templates and translated catalogues.
The main issue with internationalising GRASS is that it requires
ongoing effort; you can't just do it once and forget about it.
Whenever code is updated, the developers will typically only update or
add English text. Translators need to continually watch for such
changes and update the message catalogues accordingly.
--
Glynn Clements <glynn.clements@virgin.net>
You wrote:
Hi,
I see many attempts of translation of doc, tcl/tk gui , but don't see a lot of things lead to term.
Does GRASS community already think about having structure for i18n ? I think it could be helpful.
Wha do you think about using PO files for all translation tasks. It seems to work great in other project.
Jean-Denis
The i18n theme was in Poland very important, because we use our special characters (like You in French). I made polish version of GRASS fonts and utilities to make them (take three last files from http://wgug.meteo.uni.wroc.pl/pliki.htm). With these utilities You can make all combinations of ISO (GRASS can use ISO, not UTF) versions of fonts, of course, french too. I'm developing now HOWTO about using other, than ASCII 32..126 characters in GRASS monitor and printing. But in istructions, included with those utilieties, You can read all, what You need, so You can make french fonts.
There was developed a polish Tcl/Tk GRASS, but it was not so needed, as fonts.
I think, after developing some of national fonts - it will be very easy to change GRASS installer (this is normal unix script). I could for example copy needed fonts after detecting, what LANG value is in the system. The second - there should be made scripts to generate postscript with proper fonts. This is easy too. It needs only some time, what I have not much...
Greetings
Adam
Adam Rade-B³owski wrote:e-A
I think, after developing some of national fonts - it will be very easy
to change GRASS installer (this is normal unix script). I could for
example copy needed fonts after detecting, what LANG value is in the
system.
It would be better to just add the extra fonts with new names, so that
the encoding can be chosen at run-time.
The second - there should be made scripts to generate postscript
with proper fonts. This is easy too. It needs only some time, what I
have not much...
As a quick hack, you should just be able to change ISOLatin1Encoding
in prolog.ps to the name of the desired encoding.
--
Glynn Clements <glynn.clements@virgin.net>