You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An option to preserve the order of comment fields in the translation data would be very useful for me. This library almost works for my use case, but parsing a .po file with the library, modifying the translation data, and re-compiling the translation data back into a .po file with the library changes the ordering of comment fields. For example:
-#. ~ Snippet in category "tip"
#: data/core/tips.json
+#. ~ Snippet in category "tip"
msgid "Moose may not be your friend."
msgstr "Elche sind vielleicht nicht deine Freunde."
This seems consistent behavior, #. lines are always moved below #: lines. This causes diffs for translation files to become very large and hard to review. This is inconvenient for our workflow. The original translation files are generated with a process that orders the comments like this, which I can't affect.
The text was updated successfully, but these errors were encountered:
I second this, it should be possible to preserve the order as if the .po files are being processed with different tools it would be good to honour the previous order set in the template or existing file.
An option to preserve the order of comment fields in the translation data would be very useful for me. This library almost works for my use case, but parsing a .po file with the library, modifying the translation data, and re-compiling the translation data back into a .po file with the library changes the ordering of comment fields. For example:
This seems consistent behavior,
#.
lines are always moved below#:
lines. This causes diffs for translation files to become very large and hard to review. This is inconvenient for our workflow. The original translation files are generated with a process that orders the comments like this, which I can't affect.The text was updated successfully, but these errors were encountered: