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
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?
The text was updated successfully, but these errors were encountered:
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
, andes
are absent in the -x parameter)Ukrainian and Norwegian translated, but Spanish not.
If I remove
es_MX
form exceptions and putes
instead - still no Spanish translation.Only if I remove both
es_MX
andes
, I will get Spanish, but in the log it says:and .strings files appear for both languages this time:
es
andes_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
withoutes_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?The text was updated successfully, but these errors were encountered: