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

English is used instead of the base language for missing pt-BR #8

Open
biodranik opened this issue Jun 2, 2023 · 0 comments
Open

Comments

@biodranik
Copy link
Member

There is a logic now that our clean_strings_txt cleans up similar sub-languages translations, and twine properly supports it by generating the base language for iOS. For example:

[type.historic.fort]
en = Fort
...
pt = Forte
pt-BR = Forte
ro = Fort 
...

becomes

[type.historic.fort]
en = Fort
...
pt = Forte
ro = Fort 
...

and works correctly. The bug appears when that translation is referenced in another translation:

[type.someothertype]
ref = type.historic.fort

Then instead of pt Forte the wrong en Fort is generated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant