Review Mixed-Direction Text in Arabic and Hebrew Email

Review Arabic and Hebrew emails in Migma as mixed-direction documents, not just translated paragraphs. Product codes, Latin brand names, dates and punctuation can sit inside right-to-left text, and each must retain its intended order when the email is rendered and copied.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 14, 2026.

Migma's language documentation lists Arabic and Hebrew and describes separate versions for review. We recommend that workflow for preparing a localized artifact, followed by a native-language review of the actual message. Listed language support is not evidence that every mixed-script combination works in every inbox.

Make a directional stress card#

Start with a small set of approved phrases that reflects the real campaign. Ask the language reviewer to supply the complete sentences; do not ask a layout tester to invent fluent Arabic or Hebrew.

Use this original card inside those sentences:

The card is an original proposed test, not an observed compatibility result. Use synthetic identifiers first, then replace them with approved campaign values before final review.

Direction is different from alignment#

Moving a paragraph to the right edge does not specify how an embedded left-to-right sequence should interact with its neighbors. W3C's bidirectional text guidance explains how directional isolation helps mixed text and distinguishes ordinary handling from forced character-order overrides.

That is HTML guidance. It does not establish support for a particular construct after an email client or export platform processes the markup. Ask the person responsible for the email HTML to choose an appropriate implementation, then test the resulting artifact in the clients that matter to the audience.

Avoid repairing the appearance by reversing the stored characters of an identifier. A code that looks correct in one screenshot can become wrong when selected, copied or read in another environment. Preserve the intended underlying string and fix its presentation with suitable markup and layout.

Run the card through the final reading path#

Create the language version in Migma and insert the approved mixed-script sentences. Inspect the full email rather than isolated words. Directional problems often depend on surrounding punctuation or the next phrase, so a standalone product code is an incomplete fixture.

Use Email Preflight for the available inbox and device views, then review received tests in the actual sending destination as your normal approval process permits. Check narrow widths, line wrapping and the plain-text alternative where one is supplied. Record which clients and versions were inspected instead of saying “RTL tested” without scope.

In each view, ask the reviewer to read the sentence aloud and identify the product, date and requested action. Separately copy the identifier into a plain text editor and compare it with the approved string. These tasks probe meaning and data integrity, not just visual neatness.

Repair one local problem at a time#

If a model number appears on the wrong side of its punctuation, keep the sentence fixed while the HTML owner changes directional handling. Regenerating the whole email at the same time makes it harder to know whether the repair worked or merely removed the difficult example.

If a line break separates a label from its value, review the available layout width and wording with the language owner. Do not shorten or reorder a phrase without checking whether that changes its meaning. Keep the stress card in the approval record so the next reusable version is tested against the same cases.

This is separate from the currency formatting contract: the question here is character and phrase order, not whether a displayed amount is the approved market price.

No Arabic or Hebrew campaign was generated, sent or tested for this article. W3C supplies the underlying direction concepts; Migma supplies documented localization and review surfaces. Begin with one mixed-script identifier from your next localized message and verify its visible and copied forms together.