-
Notifications
You must be signed in to change notification settings - Fork 121
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
Ability to add country/region-specific localizations #329
Comments
There is an issue when specified region. I think this must be fixed in upcoming releases |
Is there anything I can do to help push this forward? I'm in need of differentiating between |
hi @kevincianfarini
and maybe it's already works? as i see full directory name used as language name so if you create |
Done! @Alex009. Unfortunately it was a bit more complicated than that, though. |
Not sure about the progress so I share my current workaround (a simple file renaming via gradle) if ever it can help someone.
|
will be released in 0.21.0 |
This was very helpful actually in case you have language-region based translations. I ended up with declaring the translation files as usual en-XX, etc (without the -r), so it would work in iOS nicely (and pass app store review as well).. And then added the following to build.gradle.kts file:
|
@kaidotarma glad to hear, but did you get an issue with 0.21.0? On my side I was able to remove this workaround after the upgrade. (If you still have an error with higher version, you may want to open an issue for the moko team to be able to help.) |
You are correct! My library version was not up to date in all places. |
Is it possible to provide different strings by region? E.g. distinguishing en_US and en_GB? If so, can you add an example to the docs?
The text was updated successfully, but these errors were encountered: