For more information, please see the following sections: The following file extensions are supported when setting up file format configurations for iOS Strings files: .strings.
To learn more about working with file format configurations, please see the following pages:
- View file format configurations
- Modify file format configurations
- Create file format configurations
- Test and validate file format configurations
Default iOS Strings File Configuration
Every file format has a default configuration to ensure that a file can be translated; however, it does not handle every complex property that could be thrown your way when translating a source file. The default configuration for iOS Strings files does the following:
- Uses UTF-16 as the default character encoding.
- Extracts programmers' comments for translation.
- Does not show leading and trailing whitespaces to the translator.
- Uses SRX rules for text segmentation.
Custom iOS Strings File Configurations
If you are performing a iOS Strings file translation, a custom file format configuration might be necessary to achieve the right results in your target file. Outside of the default configuration selections, Wordbee Translator offers many additional choices for configuring:
- A different character encoding.
- Exclude programmers' comments from the translation.
- Not show texts containing neither letters nor digits to the translator.
- Exclude content from the translation via text segments or regular expressions.
- Always split text at line breaks.
iOS Strings File Options
When setting up a file format configuration for iOS Strings files, there are many options to choose from to ensure extraction is successful. The General Tab contains options for changing the type of encoding, general content options, exclusion of content, and text segmentation. The options are described in general below based on individual sections.
- Encoding - This option may be used to change the type of encoding used for the iOS Strings file source file. The default setting is UTF-16.
- Content - This section contains options for content within the source file and may be used to extract or exclude programmer comments, to show or hide texts not containing letters nor digits, and to show or hid leading and trailing whitespaces.
- Exclude Content - This option may be used to define content that should not be extracted for translation. For each piece of text (segments), the system looks for the texts or regular expression patterns entered in this section of the configuration. If a text/pattern matches, then it is possible to mark the segment as either translatable or not translatable. The system checks one pattern after the other until one matches. Text that matches none of the patterns is considered translatable.
- Text Segmentation - Enable/Disable SRX rules for text segmentation and choose to spilt or not split text at line breaks.