Page Comparison

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: 

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 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-16 8 as the default character encoding.
• Extracts Does not extract programmers' comments 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

...

• A different character encoding.
• Exclude Extract programmers' comments from the texts for translation.
• Not show 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.
• Exclude content from the translation via text segments or regular expressions. 
• Always Disable SRX rules for text segmentation.
• Exclude text segments, words, or terms from the translation.

Java Properties File Options

When setting up a file format configuration for Java Properties files, there are many options to choose from to ensure extraction is successful. 

General Tab

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 Java Properties file source file. The default setting is UTF-8.
  
  
• Content - This section contains options for content within the source file and may be used to exclude programmer comments, hide text not containing letters nor digits, or to hide leading and trailing whitespaces. 
  
  
• HTML Content - This option may be used to inform Wordbee Translator that the source file contains HTML content. It is disabled by default and must be enabled to translate Java Properties files containing HTML content. Unless otherwise specified, the default HTML file format configuration will be used for the translation.
  
  
• Text Segmentation - Enable/Disable SRX rules for text segmentation and choose to spilt or not split text at line breaks.

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 Questions and Answers page.

...

Do Not Translate Tab

The Do Not Translate Tab contains options for excluding segments of text, words, or terms from the translation. The options are described in general below based on individual sections. 

• Segments - Mark specific text segments as translatable (extracted) or not translatable (ignored) when found by the system. Regular expressions may be entered in the system to protect entire segments or just terms within the file. These segments or terms will not be extracted for translation and be taken into account during the wordcount step. In the translation editor, they will appear as tags and can be used to protect parts of texts that should not be translated, but should still appear in the translated document. A good example, is entering terms or regular expressions to protect brand names or confidential content like software codes.
  
  
• Words or Terms - Configure single words, terms, or segments to be excluded from the translation. Any text captured by regular expressions is converted into markup and not modified. A description may be added to avoid confusion. When no description is added, the original text will appear upon hovering over the markup. This feature is useful to protect certain terms that must not be modified by the translator. For instance the company name, or technical references, etc...