[Chandler-dev] Localizing English
jeffrey at osafoundation.org
Fri Apr 6 09:56:08 PDT 2007
>> The most important thing is not changing the keys (English) that are
>> used by localizers to create .po translations. Your suggestion
> Cool! Looks like we've a deal then... :)
I think your proposal is perfectly reasonable, but I thought I'd mention
that I think it's possible we could have a lighter weight system. Mimi
seems amenable to just editing the Python directly, if she knows what
file to look in.
While I think folks on the design team aren't intimately familiar with
Python, so syntax errors may not be obvious to them, PPD folks can and
should test their changes just like developers, and syntax errors in
modules will generally prevent Chandler from even loading.
So one way or another, I'm in favor of not filing many bugs for
text-only changes. I do have a slight preference for NOT using an EN
translation, because my strategy when trying to find the code that gives
a particular message is often to search for the string I see. But
that's a tiny issue, I could turn off the translation when debugging.
Whatever's easier for the PPD team.
More information about the chandler-dev