Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagged Strings Show as Untranslated #697

Open
Zoramite opened this issue Dec 7, 2017 · 0 comments
Open

Tagged Strings Show as Untranslated #697

Zoramite opened this issue Dec 7, 2017 · 0 comments

Comments

@Zoramite
Copy link
Member

Zoramite commented Dec 7, 2017

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.

@Zoramite Zoramite added this to the Bucket List milestone Dec 7, 2017
@Zoramite Zoramite added this to TODO in Internationalization via automation Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant