Hi! We need to document which contexts are needed for which strings. Then these contexts can be used for contrib at least, and included in core later.
I propose we start documenting these on a handbook page, for instance divide it in "Implemented" which only contains "May" so far, and "Proposed" which will contain the rest for now.
If a string is used in one context in core, and in another in contrib, we should use the core meaning as default context. Then we will only have a problem for D7 if a string is used in several contexts within core.
2010/1/18 Gerhard Killesreiter gerhard@killesreiter.de:
I am afraid that there is no such time window anymore for core. However, you can still work with contrib authors to improve the situation.
I think I've read somewhere that fixes of typos in the text are still welcome (couldn't find it again when I tried). If there are a few contexts which make a big difference, maybe it's not completely impossible to get them in? After all, the string freeze is there for translators' sake, so if the translation community strongly request a few exceptions to the string freeze, that might be possible.
Hilde