Changes

:First and most important is that "string freeze" is a restriction on developers and not translators.  String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.

:First and most important is that "string freeze" is a restriction on developers and not translators.  String freeze means developers need to stop changing UI strings so that translators can do their final work prior to release, in other words, string freeze is a start signal for translators to perform their final reviews and commits of PO files, not a stop signal, even the release date itself is not a stop signal for localization.

:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on lang-pap is not complete by the next release date.  This is part of the beauty of separating the code (release) from the strings (PO/MO files).

:Second is that even after a release is made and declared final and stable, localizers can complete their work and a deployment team can make a customization stick for a deployment that includes the post-release localization work, so you will not "miss the boat" for providing a localized UI environment for your deployment if work on your language is not complete by the next release date.  This is part of the beauty of separating the code (release) from the strings (PO/MO files).

==== Is it possible to edit more than one string at a time? ====

==== Is it possible to edit more than one string at a time? ====