Mango Translations — Translation QA checks | mangotranslations.xyz

Mango Translations — Translation QA checks | mangotranslations.xyz

Translatability and language markup

Use translate, lang, id and protected identifiers according to W3C ITS so the target page keeps its keys and declares its language.

W3C ITS 2.0 defines Translate values yes and no to express whether selected content is intended for translation. In HTML5 the native translate attribute is the counterpart of the ITS Translate category, so the same intent can be expressed without a separate ITS namespace.

The HTML lang attribute is the counterpart of ITS Language Information, and id is the counterpart of ITS Id Value. That means language declaration and identifier preservation are markup concerns, not afterthoughts in the translation memory.

The signature mark of this site, drawn as a plate

On narrow screens, swipe or scroll the plate sideways.

In practice, mark every token the runtime substitutes with translate="no", and keep id values byte-identical between source and target. A translated id is invisible in review but breaks anchors, scripts and form labels at runtime.

Check the result mechanically: extract protected tokens and ids from both pages and compare the lists. Markup that looks correct in the editor can still lose a token when a string is edited by hand.

  • Apply translate="no" to placeholders, codes, URLs and brand strings.
  • Keep id values identical; treat them as keys, not prose.
  • Verify lang on the html element and on inline foreign-language spans.
  • Verify dir separately, including embedded opposite-direction runs.

Further reading