[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: typo-fixing msgids (Re:
From: Krzysztof Lichota <krzysiek () lichota ! net>
Date: 2005-04-30 23:25:06
Message-ID: 427413D2.9010600 () lichota ! net
[Download RAW message or body]
David Faure wrote:
>>As I suggested many times earlier, I think the correct solution would be
>>to add translation with typo fix for en_US language - this way msgid
>>would not change. The same way as en_GB fixes their local spelling
>>(color vs. colour).
>
> I think this is too much trouble and source of confusion.
I see i18n() calls as mapping key (which is what programmer included in
source) to visible string (in most cases a translation). And, maybe
because I am a programmer, I don't like the idea of changing keys to fix
value.
If en_US is treated as normal translation, proofreading team can change
whatever they want even after the freeze - style, typos, even add some
additional, English-specific text.
> And most people won't install en_US, so they'll still get the typos.
en_US can be included by default with distribution. Only matter of
changing KDE to use these translations instead of using whatever was
passed in sources.
>>2. Translators tend to keep file to on their disk for a while and then
>>commit it back, replacing the contents. Then the translated message
>>would be lost.
>
> Impossible, cvs/svn tells you when you have to update before being
> able to commit, due to a commit having been made on the server.
> Every time I run check_po_files, the same situation happens: someone else
> than the translators is changing a .po file. Like everyone using CVS,
> translators have to remember to update before starting to work, and to
> commit relatively often. This is the only way people can work together.
The problem is when the work model is that only few members of the team
have CVS accounts and other translators send plain files, which are then
put in CVS. This is the case in my team.
Regards
Krzysztof Lichota (Polish team)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic