Remove German messages?
Jakson A. Aquino
jaksonaquino at yahoo.com.br
Tue Aug 30 17:45:21 CEST 2005
On Tue, Aug 30, 2005 at 03:26:15PM +0200, Bernhard Reiter wrote:
> No objection,
> just an addition for completeness:
> Most of the problems could also be solved if
> we could just create the german po file directly out of
> the source code.
> So the alternatives to maintain this would be to write
> a script doing just that.
I think that the extraction of the German strings directly
from the source code is just one step of a longer process.
The steps that I have in mind are:
(1) Identify what German strings in the source code are
outdated in relation with their English counterparts.
(2) Translate and/or correct these messages in the source
(3) Run the script to extract the German and English
messages and put then in the po file.
Probably, the step 3 is the easiest. I think it can be
solved with gettext + grep. Anyway, it's simpler to
translate a po file using poedit than to do the translation
directly inside the source code, because poedit checks
immediately whether we did any spell or printf mistake. One
advantage of translating directly in the source code would
be that the messages are contextualized by the code around
them. But with poedit (or kbabel) we can see the context if
Other advantage of having only one language in the source
code is that it becomes smaller and easier to read and fix.
It's easier to run the code in our mind if it is entirely in
Of course, if you prefer, we can try the scripts. Would you
like to write them?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://intevation.de/pipermail/statist-list/attachments/20050830/27d6a508/attachment.bin
More information about the Statist-list