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
I started noticing this after updating the bundle to the most recent version, so it seems like this was introduced recently.
The order of translations seems to be completely different between translation:extract and translation:download. I'm not sure if this is because they use different writers (see #392 (comment)) or simply because no ordering is applied at all (and therefor the order in Loco is used in translation:download, and the order in the local source code is used in translation:extract).
This results in a massive Git diff if you extract new translations from an external source (Loco in our case), making the translation:extract command basically useless because you will have to manually figure out which messages are added, unless you accept the massive diff in your commit (and the second massive diff after you run translation:download again). Of course this isn't an issue if you .gitignore all translation files, but we do commit our messages.en.xlf as the "source translations".
The text was updated successfully, but these errors were encountered:
I started noticing this after updating the bundle to the most recent version, so it seems like this was introduced recently.
The order of translations seems to be completely different between
translation:extract
andtranslation:download
. I'm not sure if this is because they use different writers (see #392 (comment)) or simply because no ordering is applied at all (and therefor the order in Loco is used intranslation:download
, and the order in the local source code is used intranslation:extract
).This results in a massive Git diff if you extract new translations from an external source (Loco in our case), making the
translation:extract
command basically useless because you will have to manually figure out which messages are added, unless you accept the massive diff in your commit (and the second massive diff after you runtranslation:download
again). Of course this isn't an issue if you.gitignore
all translation files, but we do commit ourmessages.en.xlf
as the "source translations".The text was updated successfully, but these errors were encountered: