Critical Bug: RTL (Hebrew) text reversing word order in Visio for the Web (mac)

The behavior described matches known limitations and issues with bidirectional (RTL/LTR) text handling in Microsoft products when mixing Hebrew (RTL) with neutral characters and layout engines that rely on the Unicode bidirectional algorithm.

Key points from the documented behavior:

1. The Unicode bidirectional algorithm can reorder characters and words in ways that do not match user intent when using RTL scripts (Hebrew/Arabic) together with neutral characters (spaces, parentheses, punctuation) and LTR text.
2. This is particularly problematic in business and diagramming scenarios, because the rendered text may not match what was typed, even though it looks correct while editing and then changes when the control re-renders the text.
3. Similar issues are documented in other Microsoft products (for example, Dynamics 365 and Skype for Business) where Hebrew text or mixed Hebrew/English strings appear in reverse order or with punctuation moved to the wrong side when the text is re-rendered.

Given the context:

• The issue is not caused by the Mac itself but by how the web editor’s text control applies the Unicode bidirectional algorithm when it finishes editing and lays out the text.
• There is no documented Visio‑specific fix or setting in the provided material.

Practical guidance based on the documented bidi behavior:

1. Avoid weak/neutral characters around Hebrew where possible
   • When possible, avoid parentheses, underscores, and similar neutral characters in Hebrew-only labels, or ensure Hebrew characters appear on both sides of such characters. For example, documented guidance suggests avoiding patterns like Dynamics (DAT) and instead using Dynamics DAT to prevent reordering.
2. Use plain Hebrew without mixed LTR text or special grouping characters
   • For shapes that must contain Hebrew only, keep the text strictly RTL without embedded English words, underscores, or parentheses. This reduces the chance that the layout engine will reorder words.
3. If mixed Hebrew/English is required, test alternative separators
   • Documentation shows that underscores and some punctuation often trigger undesired reordering (for example, 123_456 becoming 456_123). Where possible, replace underscores or certain punctuation with alternatives (such as a period or slash) that behave more predictably in RTL contexts.
4. Report the issue and track it as a product bug
   • Similar bidi issues in other Microsoft products (for example, Hebrew word order in Skype for Business 2016) were addressed via product updates. The documented resolution there was to install a specific update. For Visio for the Web, the equivalent path is to open a support case so the issue can be logged and fixed in the service.
   • Provide support with:
     • Clear before/after screenshots (editing vs. after clicking outside the text box).
     • Exact sample Hebrew sentences that reproduce the issue.
     • Browser, OS version, and Visio for the Web environment details (Microsoft 365 tenant, account type).
5. As a temporary workaround, consider:
   • Keeping critical Hebrew text short and avoiding mixed-direction content in the same shape.
   • Using separate shapes for Hebrew and English text instead of mixing them in one text block, to reduce bidi conflicts.

Because the provided documentation does not include a Visio‑specific toggle (such as an RTL/LTR flag for Visio Web text boxes) or a confirmed fix, the only supported long‑term resolution path is to have the issue tracked by Microsoft Support as a bug in Visio for the Web’s RTL rendering.

References:

• Right-to-left language support and bidirectional text
• Hebrew words in instant messages are displayed in reverse order in Skype for Business 2016