Mango Translations — Translation QA checks | mangotranslations.xyz

Mango Translations — Translation QA checks | mangotranslations.xyz

Characters, bytes and storage limits

Measure expansion in characters and storage in encoded bytes, and normalize to NFC before counting so the two figures are comparable.

ITS Storage Size specifies a maximum storage size, and Allowed Characters specifies permitted characters. These are different constraints, and a string can satisfy one while failing the other once it is encoded.

Expansion is measured against the source. Growth from 8,000 to 9,200 characters is 1,200 extra characters, or 15% expansion. That figure is what tells you whether a field with a hard cap will still accept the target.

The signature mark of this site, drawn as a plate

On narrow screens, swipe or scroll the plate sideways.

W3C ITS recommends normalized transcoding to Unicode Normalization Form C in its implementation guidance. Normalizing before counting prevents composed and decomposed forms of the same visible text from registering as differences.

Report both figures side by side: characters for expansion and bytes for storage. A single number hides which limit is actually at risk.

  • Normalize source and target to NFC before counting.
  • Measure characters for expansion and encoded bytes for storage.
  • Compare both against the declared ITS Storage Size and Allowed Characters.

Further reading