Page Comparison

The following file extensions are supported when setting up file format configurations for Code Files: .htmcs, .htmlinc, .xhtmljs, . htmlscss, .phpjfs, .php2cls, .php3asax, .php4asa, .php5c, .php6cpp, .phtml, .csm, .jsp, .ahtm, .ahtml.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.

• Converts characters not compatible with the target encoding into entity references.

• Compresses sequences of whitespaces into a single whitespace.

• Enables SRX rules for text segmentation.

• Enables the use of //notrans, //beginnotrans ... //endnotrans to delimit not translatable code.

• Extracts quoted strings.

• Defines specific translatable attributes for extraction. 

Custom Code

...

File Configurations

If you use Code Files content for translationsare 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
• HTML Attributes
• Content Exclusion
• Text Segmentation
• Extracting & Excluding Quoted Strings
• Including/Excluding Additional Content
• Configuring Translatable Attributes and Tags
• CMS Specific Settings

...

A Few Examples

The following are just a few examples of what you can do with a custom Code Files File configuration in Wordbee Translator. For more advanced examples, please see our /wiki/spaces/WBT/pages/711314Code File Questions and Answers page.