[Chandler-dev] Localizing English

[Philippe Bossut]

Hi,

There's one bug 
(https://bugzilla.osafoundation.org/show_bug.cgi?id=8648) that made me 
thought about an old idea I had when localizing Chandler in French: what 
about creating a localization package for "English"? The strings in the 
code could then be considered as being in "geek speak" while the 
official end user facing English UI strings would be found in the 
localized English files.

Advantages:
- It can be fairly difficult for someone like Mimi or others to hunt 
down strings in the code. Compare that to editing a po file which 
contains all the strings in one place.
- It's error prone of course...
- Such a change requires rebuilding the app (while a change in a 
localization package doesn't)
- Sometimes it would be convenient for devs to differentiate 2 strings 
in the code that just happen to be the same in English but could be 
different in another language (e.g. "from" in "from 8:00 to 9:00" and 
"from John" are actually different and could be differentiated in the 
code if one could write "from (time)" and "from (person)" in the code, 
and let both be translated as "from" in the English po. Note that in 
this example the whole strings would be coded as "from %(starttime)s to 
%(endtime)s" and "from %(person)s" so the problem wouldn't happen but 
you get the idea...)

Thoughts?

Cheers,
- Philippe