Hi,

Heikki Toivonen wrote:
Maybe I misunderstood, because this does not make sense to me:

So you are saying we will not change strings in Chandler code, but you
will manually change Chandler.pot, which should be used by translators
to create po files?

You misunderstood what Brian said. His point is : the strings in the code (the untranslated ones that are used as msgid if you prefer) are not good, the English is poor, the wording is inconsistent, etc... which makes the work of translators hard. So we should make our best effort to change them before we start localization for good. 2 points are making that a tad tricky: - We are in a "string freeze" period and we asked devs not to change those strings (but that's a constraint we added on ourselves, not a law of physics) - We better have that done by one person so that consistency is indeed achieved. Turns out that this is what Mimi's just done with her Chandler-en.po

So the proposal is:
1- Mimi tweaks the Chandler-en.po may be once more (actually she logged bug 9954 against herself to do just that). Note that Mimi prefers working on the po rather than the Python and xrc because in the po you have all the strings right here and there and you can ensure consistency in a much easier way. 2- When done, Brian makes the manual changes of the strings in Python and xrc files. Other devs please continue to respect the "string freeze" or his and Mimi's work will be made that much harder. 3- When all the substitutions are done, we'll create a new Chandler.pot (using the usual createpot tool) that we'll commit in the localizations svn and we'll give the "go" to other localizers to start their work

Note that this operation will likely make the use of a Chandler-en.po much less critical, except for those stray strings that we may want to tweak once more post point 3.

Does it make more sense?

Brian, Mimi, please chime in if I miss something.

Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to