i18n of egcs

Philipp Thomas kthomas@gwdg.de
Thu Mar 25 03:43:00 GMT 1999


Yes, I know this is post 1.2 stuff, but as it looks like this could be
a way for me to contribute to egcs, I've started to track down all
that's necessary for complete i18n of egcs. 

Now before I go down the wrong path(s) I would like to get some input
for questions I have.

In the case of back/front ends the mechanism (as described in the
documentation) is clear: No direct calls to gettext(), the code doing
the output is responsible for getting messages translated. So xgettext
just needs to be told which keywords to look for and static strings
like help text for options marked.

But what should be done for the libraries ? As I see it, there is no
other way but to use direct gettext() calls. Or do the libraries also
have central functions for dealing with errors/warnings (haven't come
to inspecting the library code yet) ? And in order to keep the
installed stuff small, I'd say that the lang specific libraries should
have their own message catalogs, even if that gets a bit hairy wrt the
Makefile(s).

If any of you would share his/her thoughts and comments with me I'd be
very grateful.

BTW, anybody got hints/pointers for me (most probably better via
direct email) for how to setup my own cvs tree for egcs and then keep
it in sync with the cygnus tree ?

Philipp

---  caffeine low - brain halted



More information about the Gcc mailing list