Arabic localization changes page direction as well as wording. Latin product names, numerals, URLs and wallet addresses inside right-to-left text need mixed-direction handling so their order remains readable.
Identify the reader and right-to-left context
Identify the target audience and register. Test navigation, tables, parentheses and currency amounts in the actual layout. Confirm that icons and page flow follow the intended direction while embedded identifiers remain unchanged.
Check order, punctuation and embedded numbers
Never reverse or translate an account number, URL, token symbol or wallet address.
What is the main technical review risk?
Mixed-direction strings may display identifiers in the wrong order. The language-pair index groups right-to-left checks with the site’s other locale references.
Set conventions for mixed-direction strings and names
Right-to-left localization needs to be considered in page architecture, not applied as a final alignment switch. Decide how navigation, tables, numerals, mixed-language labels and punctuation will behave. Provide target audience and register, and retain approved spellings for names and products. Embedded addresses, URLs, transaction hashes and account numbers must remain exact.
Review the interface with bidirectional text in place
Test mixed-direction content in real components. Inspect parentheses, currency amounts, phone numbers, Latin product names and text-selection order. Check reading order with keyboard navigation and assistive technology; a visually mirrored layout can still have an incorrect programmatic sequence.
Example: keep an identifier readable in Arabic copy
Test an Arabic interface containing Latin product names and numerals in a real browser. Confirm that visual order, copy-and-paste order and keyboard navigation all keep the identifier and its label associated correctly.
Test Arabic content in a right-to-left layout
Review directionality together with embedded Latin labels and numbers.
- Set the page direction and verify punctuation around mixed-script text.
- Check wallet addresses, model codes and numerals remain readable left to right.
- Test forms, tables and navigation in the production layout.
Questions about Arabic translation
Should a wallet address be mirrored with the paragraph?
No. Preserve the identifier’s character order and test its display.
Is right alignment enough for RTL support?
No. Check reading order, punctuation, forms and mixed-direction text.
Apply the layout check to a form field
A right-to-left payment instruction that includes a Latin wallet address needs visual and interaction checks. Verify that the address characters remain in source order, the copy button selects the intended string and the network label stays adjacent to the correct address. Review screen-reader order too; visual alignment alone does not guarantee that the control is understandable.
| Mixed-direction item | Check | How |
|---|---|---|
| Identify the embedded URL, number or Latin name. | Preserve character order and reading sequence. | Test display, keyboard focus and copy/paste behavior. |
Send source and display context for review
Provide the target audience, script direction, interface screenshots, approved names and embedded identifiers. Test the page flow, mixed-direction content, numbers, punctuation and keyboard order. Keep the original character order for account numbers, URLs and wallet addresses and confirm copying those values works as intended.
Is right alignment sufficient for an Arabic interface?
No. Test reading order, mixed-direction text and controls as well as alignment.