All geek questions in one place

Localization of Apple Watch database shows incorrect default language

I have an application localized in three languages ​​(simplified Chinese, French, and Czech) with development English.

enter image description here

While localization works fine on iPhone, Apple Watch has a problem: if the user set the viewing language in any language other than English / French / Chinese / Czech, then the content is displayed in Chinese (this should be the default value).

In accordance with this Technical Note :

If none of your preferred languages ​​is supported by your application, iOS selects the language that matches your application’s development area ( CFBundleDevelopmentRegion ).

Note. Be sure to set CFBundleDevelopmentRegion for your application. If you use basic localization, make sure that the CFBundleDevelopmentRegion value matches the language used by your content in the Base.lproj folder.

I confirmed that both of the above requirements are fulfilled ( CFBundleDevelopmentRegion="en" and all Base.lproj files are really in English). Is there something I'm missing? Again, this only happens for the Watch app, not for the iPhone.

+5
source share
3 answers

I have traditional Chinese and simplified Chinese, but traditional Chinese is selected as the default language. When I delete the traditional Chinese translation, English is selected.

I also set CFBundleDevelopmentRegion to en, which is the default value.

In your screenshot I did not see the English - English development language.

0
source

I had the same problem and I found a solution in this thread: https://forums.developer.apple.com/thread/86889

In principle, the extension Localizable.strings (Base) is required to expand the clock. Usually on the iOS side you do not need to specify the basic version of the file, but only translations. But the clock seems to require a basic version of the file for the system to work there in general. In fact, I only had the interface translated (in the watch app) and I didn’t even have Localizable.strings in the chat extension ... so I had to add some localizable lines in the extension, export the translations, import them again, and then manually add the base version (by checking Base in the Localization section of the File Inspector), because this obviously necessary thing is not automatically created.

0
source

Source: https://habr.com/ru/post/1269015/

More articles:


All Articles