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
Currently, when locating untranslated strings the yaml tagging allows for defining locale specific strings (ex: string@es: ...) but those strings are not imported into the translation catalog as being translated in the locale. And usage of the strings with _() make the translated string show up as being missing for the locale.
Part of the issue is that the untagging happens and replaces the untagged version. This makes it so that the code cannot tell that the value is a localized value without looking at the unprocessed file.
To properly handle this it will require tracking during the untagging process to keep track of the original and locale specific values and make sure they are part of the message catalog.
The text was updated successfully, but these errors were encountered:
Currently, when locating untranslated strings the yaml tagging allows for defining locale specific strings (ex:
string@es: ...
) but those strings are not imported into the translation catalog as being translated in the locale. And usage of the strings with_()
make the translated string show up as being missing for the locale.Part of the issue is that the untagging happens and replaces the untagged version. This makes it so that the code cannot tell that the value is a localized value without looking at the unprocessed file.
To properly handle this it will require tracking during the untagging process to keep track of the original and locale specific values and make sure they are part of the message catalog.
The text was updated successfully, but these errors were encountered: