| Parallel Latin and Cyrillic | Old documents are Cyrillic, new ones Latin, and many offices use both. A translation set in the wrong script is unusable for the receiving body. | We read both scripts and set the target text to the script the specific receiving body expects, fixed in advance. |
| Oʻ and Gʻ typed as an apostrophe | The letters Oʻ (Cyrillic Ў) and Gʻ (Cyrillic Ғ) use the okina (U+02BB), not a straight apostrophe. Typed as ' or ', names become ambiguous and unfindable in registers. | We set Oʻ and Gʻ with the correct okina character, so names remain unambiguous and register-searchable. |
| Uzbek treated like Turkish or Kazakh | Uzbek has largely lost the vowel harmony typical of Turkic languages; analogies to Turkish or Kazakh import wrong forms and endings. | We translate Uzbek on its own terms, not by analogy to other Turkic languages. |
| Cyrillic letters Ў, Қ, Ғ, Ҳ confused | Uzbek Cyrillic carries letters (Ў, Қ, Ғ, Ҳ) that Russian keyboards and OCR confuse. Misread, a name or term becomes another. | Native specialists read the Uzbek Cyrillic letters correctly and check each name against the source. |
| Digraphs sh, ch, ng mishandled | Latin Uzbek uses digraphs (sh, ch, ng); split or merged wrongly, a syllable and a name change. | The digraphs are read and set as units, and names reconciled with the passport. |
| Agglutinative endings rebuilt from German | Uzbek is agglutinative; suffixes stack. Reconstructed from German word order, official forms become unnatural and wrong. | We write from Uzbek morphology, with correctly stacked suffixes, not reconstructed endings. |
| Certification abroad ≠ German authorisation | A German court-authorised translator is not automatically admitted in Uzbekistan, and the apostille and local forms differ. | We clarify where the document applies and set the right form; Uzbekistan is a Hague party, so we check the apostille in advance. |