The following file extensions are supported when setting up file format configurations for Code Files: .cs, .inc, .js, .css, .jfs, .cls, .asax, .asa, .c, .cpp, .h.
For more information, please see the following sections:
Default Code 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 Code Files does the following:
- Uses UTF-8 as the default character encoding.
Compresses sequences of whitespaces into a single whitespace.
Uses //notrans, //beginnotrans ... //endnotrans to delimit non-translatable code.
- Defines two regular expressions for text extraction: one for translatable content and one for content that should not be translated.
- Uses SRX Rules for text segmentation.
Custom Code File Configurations
If you are performing a code 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:
- HTML Code
A Few Examples
The following are just a few examples of what you can do with a custom Code File configuration in Wordbee Translator. For more advanced examples, please see our Code File Questions and Answers page.
To learn more about common Code File configurations heard by our support team, please see the Code File Questions and Answers section.
For more information about available configuration options when working with Code Files, please see the Code File Configuration Options page.