Task documentation
Plug-in Translatability Log Frequently Asked Questions

This page explains the most common error and warning conditions that occur in the build's Plug-in Translatability Log. You can find the log in the "TPTP Runtime and SDK" section of a build's download page. When you look at the file, you may see a problem reported, for example:
  package.html  HTML-32     833   Missing META tag.  Required CHARSET value must be defined in this file.         
The problem code is the number on the left of the message, which in this example is "833".

Problem Code IDs
  1. 115
  2. 119
  3. 122
  4. 827
  5. 831
  6. 833
  7. 840
  8. 841
  9. 920
  10. 955
  11. 957
  12. 964
  13. 969
  14. 980
Code ID Fix
115 Add this comment to the start of the file
119 See if the file should be translated, and if not, once the errors in any other files are fixed, then transfer this defect to the build team so that they can exclude the file from the translation check.
122 Variant characters have a hexadecimal representation of x'80' - x'FF', and are commonly the lead byte character of a 2-byte DBCS character. This means a user in Japan will see corrupted characters when viewing the English, non-translated text.

To fix the problem, remove the hexadecimal character from the file and replace it with either its ASCII or HTML equivalent.
827 In order for the browsers to properly show this text, the CHARSET value must match the encoding of the translatable text contained in this file. Otherwise, corrupted characters will be shown. To fix the problem, follow the instructions in 833.
831 Add this doc tag in the <head>:
833 Update the meta tag in the file to either of the following:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
840 The FACE attribute of the FONT tag defines specifically which font will be used to display a portion of text. This attribute should not be used because the specified font may not be available in all languages, particularly DBCS languages.

To fix this problem, delete the FACE attribute. If available, rely on the .css file instead.
841 A FONT or FONT-FAMILY attribute has been found in a STYLE section and the attribute hardcodes the name of one or more font face names. These fonts may be hard to reproduce in a non-English environment. A CSS should be used instead.
920 Add one of the following comments to the file to indicate what type of single quote handling should be used:
Choose which comment to use based on this criteria:
NLS_MESSAGEFORMAT_ALL Each string is assumed to be processed by the java.text.MessageFormat class (single quote must be coded as 2 consecutive single quotes '').
NLS_MESSAGEFORMAT_NONE All strings are assumed to NOT be processed by the java.text.MessageFormat class (single quote must be coded as 1 single quote ').
NLS_MESSAGEFORMAT_VAR Strings which contain replacement variables are processed by the MessageFormat class (single quote must be coded as 2 consecutive single quotes ''). Strings which do NOT contain replacement variables are NOT processed by the MessageFormat class (single quote must be coded as 1 single quote ').
955 An XML element (e.g. <br>) has an extra terminating element (e.g. <br></br></br>). Remove the extra element.
957 An XML element (e.g. <br>) is missing a terminating element (e.g. </br>). To correct the problem, either remove an unneeded element or add the matching terminating element.
964 Ensure that the correct encoding is specified: <?xml encoding="UTF-8" version="1.0" ?>
969 If the file should not be translated then transfer the bugzilla to the "Build" component. If the file should be translated then ask your Project lead for help.
980 An HTML element has been found which uses uppercase letters. Locate the listed line number in the XHTML file, find the element and change it to lower-case letters. For example, change "<META>" to "<meta>".