Right-to-left is a text direction in which reading and writing proceed from right to left, used by scripts such as Arabic, Hebrew, and Persian. In localization, right-to-left support affects text alignment, layout mirroring, icon direction, punctuation placement, and the handling of mixed-direction content such as embedded numbers or Latin brand names, so it is treated as a layout and internationalization requirement rather than a simple text reversal.
Angel Translation editorial reference · Confirm the rendering against your source and approved project terminology.
Check source meaning → confirm the preferred term → record approved variants and references.
Right-to-left issues appear in UI localization, app and web testing, help content, and subtitle or caption work for Arabic and Hebrew. Localization teams use pseudo-localization and in-context review to check mirrored layouts, navigation order, and mixed-direction strings. Engineers may also need to set text direction metadata and ensure fonts support RTL glyphs.
A common mistake is treating right-to-left as a translation-only change and not mirroring the layout, so the interface remains left-aligned and visually broken. Another error is misordering numbers, email addresses, or brand names inside an RTL sentence, which confuses users or changes meaning. Forgetting to set direction metadata can also make text render incorrectly in receivers.
Creative and consumer content needs accurate meaning as well as tone and context. Subtitles, interfaces and voice scripts also require checks for timing, character limits and pronunciation.
Provide approved terms and previous translations with the source files. Agree how variants, ambiguous wording and revisions will be reviewed. Terminology maintenance and any termbase handback are confirmed in the project scope. See the 8-step AI + expert workflow.
Employee-training video transcription and dubbing.
Read the published project →Brand documentation.
Read the published project →Published scope shows related industry experience; it does not confirm that this specific term was used or reviewed in the project.
Include the source and target languages, file types, intended use, deadline and any approved termbase. Agree handling before sending sensitive files. Acknowledged in 4 hours, quoted in 24.
Prepare an inquiry email →Content Globalization solutions →File handling →A glossary entry is not an official standard or evidence of regulatory acceptance. Confirm current requirements for your project separately.