a few weeks ago in mid-March we came across a fix (for bug 483629)
that changed an existing string without changing the entity name.
Instead of fixing that, we opted for going into the direction of
fixing all the strings in
mail/locales/en-US/chrome/messenger/search-attributes.properties
suite/locales/en-US/chrome/mailnews/search-attributes.properties
properly and get rid of all the magic numbers that posed as entity
names (and remove some obsolete strings in the process as well).
Fortunately that work has now been completed by Kent James and the
fix for bug 484147 was landed a few days ago[*].
What this means for new localizers is, that the entity names are now
much more self-explaining than they were before. However for existing
localizers this means, that a lot of new strings have shown up, which
you will now have to tackle again. We believe that this is the right
solution for the reasons outlined above.
If you have any questions, feel free to ask here
Simon
[*] http://hg.mozilla.org/comm-central/rev/96cc9a14c26e
--
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
Did the changes occur to the strings content too, or we just have
rename the strings entities from magic numbers to entity names?
Regards
- Anas
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
--
Experience is something you don't get until just after you need it.
> Hi Simon,
> Did the changes occur to the strings content too, or we just have
> rename the strings entities from magic numbers to entity names?
The latter. But I haven't looked at the changes in detail, so you
might want to have a look at the changeset
http://hg.mozilla.org/comm-central/rev/96cc9a14c26e to confirm this.
Cya
Simon