The following file extensions are supported when setting up file format configurations for Java Properties files: .properties.
For more information, please see the following sections:
Default Java Properties 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 Java Properties files does the following:
- Uses UTF-8 as the default character encoding.
- Does not extract programmers' texts for translation.
- Does not show texts containing neither letters nor digits to the translator.
- Does not show leading and trailing whitespaces to the translator.
- Uses SRX rules for text segmentation.
- Always splits text at line breaks.
Custom Java Properties File Configurations
If you are performing a Java Properties 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.
- Extract programmers' texts for translation.
- Show texts containing neither letters nor digits to the translator.
- Show leading and trailing whitespaces to the translator.
- Mark content as HTML and select a configuration for translation.
- Disable SRX rules for text segmentation.
A Few Examples
The following are just a few examples of what you can do with a custom Java Properties file configuration in Wordbee Translator. For more advanced examples, please see our Java Properties File Questions and Answers page.
To learn more about common Java Properties file configurations heard by our support team, please see the Java Properties File Questions and Answers section.
For more information about available configuration options when working with Java Properties files, please see the Java Properties File Configuration Options page.