11/8/2023 0 Comments Translate xliff files online![]() ![]() Refer to Table 6-1 for a description of the locking choices in this menu. In the Identity inspector (under the Document section), choose a locking level from the Lock pop-up menu. In Interface Builder, select the view you want to lock. If you set a view’s lock attribute, it sets the lock attribute for all its descendant views. By default, views inherit their lock attribute from their parent view and top-level views inherit their lock attribute from the. You can set the lock attribute for a single view or the entire nib file. You can change user-visible strings and attributes-such as the size of the view-but can’t change any other attributes of the view. You can make other changes for example, you can change the enabled state of a control or cell. You can’t change any user-visible strings and can’t change a limited set of other attributes, such as the view’s size. ![]() You can’t edit any properties of the view. You specify the set of properties to lock by choosing a locking level (see Table 6-1). When a view is locked, you can’t change some or all of its properties in the inspector or the project editor. In Interface Builder, lock views you don’t want to accidentally change while waiting for translations. The App Store territories are listed in App Store territories. If you are unsure about what languages to add, consider the primary languages used in the App Store territories you choose in App Store Connect to market your app. For more information about how the bundle APIs find localized resources, read The Bundle Search Pattern in Bundle Programming Guide. For example, if you add English (United States), English (United Kingdom), and English (Australia) to your project, the bundle APIs search the appropriate region-specific folders first, followed by the English language folder. The region-specific resource folders are searched before the language-specific resource folders. When searching for resources, the bundle APIs try to find the best match between the languages the app supports and the user’s language and region settings. Even if you provide region-specific resources always provide a complete set of language-specific resources for all the languages you support. For example, if you don’t need to distinguish between different regions that use the English language, you can add English to support users in the United States, United Kingdom, and Australia. This can save a lot of space in your app bundle and help reduce localization costs. However, the more general you make your localized resources, the more regions you can support with a single set of resources. You can choose from more than 100 different languages and dialects designated by regions to localize your app. As necessary, perform additional localization steps yourself. Repeat the process as needed, translating just the changes between each app revision. Import the XLIFF translations into the project and test the app in each language you added. Continue developing your app while waiting for the translations. ![]() ![]() Submit the XLIFF file to a localization team for translation into multiple languages. Export all the development language strings files that contain user-facing text to a standard XML Localization Interchange File Format (XLIFF). When you are done internationalizing the app’s user interface and code, begin the localization process. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |