Note: apologies if this has been discussed before, but I couldn't find anything about this.
When exporting a .po or .pot file from admin/config/regional/translate/export currently the order is dictated by the order the strings happen to he in the database. In our workflow, we store custom translations in .po files in the repository, but whenever a developer exports a new version of a po file (this is primarily i18n strings), the order in the file is reshuffled according to the order the strings happen to be in their development database.
Introduce a sort into the export process. To get the best results, this should probably sort on context first, source string second.
* Sanity check. Does this approach make sense, or am I missing something?
* Check if the same is true for D8
* Create a version of the patch for D8
* Create tests
None.
If this constitutes an API change, the order of translation strings in .po/.pot files may change.
None.
Needs work
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Think this new feature will need some kind of. test coverage.