[Chandler-dev] Re: Script to upgrade localized PO files
bkirsch at osafoundation.org
Wed Aug 15 15:26:18 PDT 2007
On Aug 15, 2007, at 12:19 PM, Jonas Beckman wrote:
> Brian Kirsch wrote:
>> That is really just a fancy way of saying I will take all msgstr
>> strings in the Chandler-en.po
>> and make them the keys in Python code.
>> So for example, I would edit line 109 of Chandler.py and change
>> the code to read
>> _(u"Another Chandler is already running off the same data
>> This will of course break some of the keys in the Chandler-sv.po
>> is why we can work closely to ensure a smooth merge.
> OK, seems like a good idea... in fact, I wondered if you were going
> to do that. Just let me know when and my script can find and switch
> those keys for localized versions.
> BTW - do you still have a french version lying around? It would be
> fun (and might be useful) to try my scripts on some other language.
Philippe Bossut did do a French translation in the past. I am not
sure what the current
state of the localization is.
>> Since keys are the English text, they can be as complicated as
>> need be to capture the English context.
>> However, as mentioned above English centric formatting (excessive
>> tabs, newlines) is not really
>> appropriate and should be avoided in translations when possible. I
>> will be looking in to this further
>> in 0.7.1.
> Fair enough. Complex content is not a problem and keys with
> multiple lines and many variables substitutions work just fine.
> But so far, unusual msgid formatting is behind almost all problems
> I've had processing our PO files. If it's doable, reducing or even
> eliminating redundant newlines will definitely make things smoother.
> / Jonas
More information about the chandler-dev