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

A small mess with Spanish language #22

Open
vitalii-tym opened this issue Sep 12, 2018 · 0 comments
Open

A small mess with Spanish language #22

vitalii-tym opened this issue Sep 12, 2018 · 0 comments

Comments

@vitalii-tym
Copy link
Contributor

Lets say I want Ukrainian, Norwegian and Spanish. For this I make the following request:

strsync -b en -x el vi ca it ar es_MX cs id en-GB ru nl pt tr en-AU th zh_TW ro pt_PT pl fr zh_HK ms hr de hu hi fi da ja fr_CA he zh_CN ko sv sk
(uk, no, and es are absent in the -x parameter)

Ukrainian and Norwegian translated, but Spanish not.

If I remove es_MX form exceptions and put es instead - still no Spanish translation.

Only if I remove both es_MX and es, I will get Spanish, but in the log it says:

Analayzing localizables... es (at ./es_MX.lproj)
Adding File... ./es_MX.lproj/Profile.strings
Translating...

and .strings files appear for both languages this time: es and es_MX in the project folder. However, both files seem to be equal (at least for a small test set of strings I tried), so I have no idea if they are in Spanish or in Mexican Spanish.

Impossibility to get es without es_MX and vice versa isn't a big issue - extra strings can be deleted afterwards, but I'm afraid these two might have been mixed and it is not clear which one I get as result.

Also it is possible, maybe, that Google doesn't support es_MX and everything is in Spanish?

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

No branches or pull requests

2 participants