composeMsgs.properties

[Neil]

Some of the strings in this file use the nonstandard insertion %P0%
instead of %S. In bug 536739 I propose to correct this however I don't
know how to handle the l10n aspect. Some suggestions:
1) Assume all localisers will read this and update their own repos
accordingly
2) Get someone in authority to push the trivial replacement to l10n thus
forcing all localisers to merge/rebase
3) Do nothing and wait for people to notice when step 4 or 5 gets
implemented
4) Change the codes for those two strings in nsComposeStrings.h thus
changing the property keys
5) Completely rewrite the way composeMsg.properties works

--
Warning: May contain traces of nuts.

[Simon Paquet]

Neil wrote on 30. Dec 2009:

> Some of the strings in this file use the nonstandard insertion %P0%
> instead of %S. In bug 536739 I propose to correct this however I don't
> know how to handle the l10n aspect. Some suggestions:
> 1) Assume all localisers will read this and update their own repos
> accordingly

That won't happen based on my own experience. I know that I tell all
localizers to regularly read this newsgroup/mailinglist (and Axel does
the same AFAIK), but the reality is, that not all localizers do read
it regularly.

> 2) Get someone in authority to push the trivial replacement to l10n
> thus forcing all localisers to merge/rebase

That would be my recommendation for such a change. For such a change
it would be much easier to do this in one place, instead of 70+
because AFAICS both Thunderbird and SeaMonkey are affected by this.

If you do that, be sure to announce this here again and give me a
heads-up as well, so that I can add a corresponding post to the
Thunderbird l10n blog.

Simon

--
Thunderbird/Calendar Localisation (L10n) Coordinator
Thunderbird l10n blog: http://thunderbird-l10n.blogspot.com
Calendar website maintainer: http://www.mozilla.org/projects/calendar
Calendar developer blog: http://weblogs.mozillazine.org/calendar