Page Comparison

The following file extensions are supported when setting up file format configurations for Web Pages: .htm, .html, .xhtml, . htmls, .php, .php2, .php3, .php4, .php5, .php6, .phtml, .csm, .jsp, .ahtm, .ahtml.

For more information, please see the following sections: 

toc 

...

Default Web

...

Page 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 Web Pages files does the following: 

• Extracts existing translationsUses UTF-8 as the default character encoding.
• Does not show leading and trailing whitespaces.
• Does not show preceeding and trailing markup.
• Splits segments at Web Pages segmentation boundaries

  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 Web Page Configurations

If you use Web Pages files Page content for translations, 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 content options.
• Extraction of Web Pages notes.
• Setting the segment status to "Translated" in the target file.
• Whitespace preservation and omitting texts with no letters or digits.
• Exclusion of specific content from translation.
• Text segmentation options such as splitting text at line breaks.
• Ability to load advanced properties not included in Web Pages standard files.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 Web Pages configuration in Wordbee Translator. For more advanced examples, please see our Web Pages Questions and Answers page.

HTML Content

While the default configuration is thorough enough to tackle most translation needs, it is not configured to handle HTML content. This is one of the biggest reasons to create a custom file format configuration for your Web Pages files.

With Wordbee Translator, you have the option to mark the content as HTML to ensure it is translated correctly. By ticking this option, Wordbee is informed that the content is HTML and you are able to create a custom HTML configuration or use the default to complete file translation.

Loading Advanced Properties

Some CAT tools include information that is beyond common Web Pages standards. Wordbee Translator offers an option for loading these more advanced properties, specifically the ability to extract the SDL 'origin' attribute that specifies the origin of the translation. 

Excluding Content

In some instances, you might need to exclude a specific phrase or text segment from the translation. This can be done by entering the phrase within the Exclude Content section of the configuration.

/wiki/spaces/WBT/pages/711314 page.

...