It is important to realize that "string freeze" as a concept means that developers should not change any UI strings until the release date. It does NOT mean that translators can't translate more strings. In fact, string freeze is typically the start point for translation teams to do their last finishing work on reviewing and completing their PO files.<br>
<br>There is never a bad time for a translator to do their work, all strings contributed are useful. If it is important for a language team to meet a target date for completing their work (sometimes coorresponding to a new Sugar release) then string freezes represent opportunities to complete that work and know that the language localization will be part of a widely distributed release. Language files completed after the release date will still be available for download and use, so missing a release date timeline is not typically critical for a language team.<br>
<br>Just wanted to clear up any confusion. String freezes are meant to make it easier for localizers to do their work on a set of strings that will not change until after the release, it is not a deadline for translation activity. It is something that language administrators should take note of so they can review and commit their projects PO files.<br>
<br>cjl<br>