Divehi to Traditional Mongolian: preserve reading order when copying a practical message
The two scripts do not share one reading direction
A Divehi message translated into Traditional Mongolian changes writing systems as well as language. When copying a booking, address or delivery instruction, preserve the sequence of information without assuming that the target should follow Thaana’s visual direction. A layout difference is not automatically a change in the translation’s meaning.
The Unicode specification describes Thaana as right-to-left, while its European-style numbers display left-to-right. It describes Traditional Mongolian as normally vertical, with characters running downward and successive columns progressing from left to right. These are different arrangements, not two versions of the same right-to-left flow.
Unicode also describes horizontal left-to-right presentation for Mongolian when vertical layout is unavailable. A short target passage displayed horizontally can therefore still be Traditional Mongolian text. It should not be identified as Cyrillic simply because the interface presents it in a horizontal line.
For a copied address, keep the actual sequence of the address components and their relationships intact. Do not manually reverse the entire result to make it resemble the source. Such a reversal can alter the order of words and numbers while leaving enough familiar shapes to conceal the mistake.
A booking message deserves a separate check of its identifier. Compare the complete number or reference against the source, rather than judging it by its position on the screen. The surrounding script can change how the line looks without authorizing a change to the reference itself.
Different visible boundaries need different checks
Gnanadesikan notes that Divehi word spacing is not always consistent. A source can join a verb with the previous word, or place demonstratives and numeric expressions next to nouns without spaces. A count of visible source words is consequently an unreliable target length requirement.
This is useful when a delivery instruction contains a quantity beside an item name. Recover which number modifies which item before comparing the target. A missing source space should not cause the quantity to be attached to the wrong item or treated as part of a name.
The Unicode account separately explains that some Traditional Mongolian grammatical suffixes are visually separated from their stems while remaining part of the grammatical word. A target gap and a source space therefore need not represent equivalent boundaries. Adding or removing spaces solely to match their counts can damage the text.
For an original message listing two packages and their separate references, check the packages, quantities and identifiers as distinct units of information. The target can use a different visual arrangement while preserving all three. A neat-looking layout does not establish that the references remain assigned to the correct packages.
After copying the translation into its destination, read the complete message again rather than only its first line. Confirm that the intended item still has the same quantity and reference, and that any location instruction still belongs to it. These checks address the practical effect of moving from Thaana to Traditional Mongolian without trying to force the two scripts into identical spacing or direction.
Language references