The following file extensions are supported when setting up file format configurations for INI files: .ini, .conf, .cfg.
For more information, please see the following sections:
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 INI 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 INI Files does the following:
- Uses UTF-8 as the default character encoding.
- Extracts and translates all keys.
- Does not show leading and trailing whitespaces to the translator.
- Uses SRX rules for text segmentation.
Custom INI File Configurations
If you are performing a INI 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.
- Specific keys to tranlsate.
- Each key to be an identifier.
- 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.
INI File Configuration Options
When setting up a file format configuration for INI 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 INI file source file. The default setting is UTF-8.
- Keys to Translate - Specify the names of keys to translate, one key per line. Leave box blank to translate all keys. You can use wildcards: A '*' matches any string, a '.' matches any single character. Example: "Key*" matches "Key_01", "Key_02", etc.
- Content - This section contains options for content within the source file and may be used to specify each key as a unique identifier, which is then used when pre-translating from previous file versions. It also contains option for showing or hiding leading and trailing whitespaces as well as any texts not containing letters or digits.
- 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.