Hi,
Brian Kirsch wrote:
Keep English strings in Python but allow the creation of an en.po for
making changes during code freeze points. i.e. Mimi wants to refine the
language on a dialog without editing the code.
The keys (Unicode strings in Python) remain the same so as
not to disturb other localization .po files. Using a en.po would allow us
to make subtle changes easily with out generating a rebuild of Chandler.
If I have correctly summarized your proposal then I would give a +1.
This is exactly what I had in mind. Sorry to have been somewhat muddled
in my first proposal.
The most important thing is not changing the keys (English) that are
used by localizers to create .po translations. Your suggestion
accomplishes
this.
Cool! Looks like we've a deal then... :)
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
