Bilingual Training Decks: Arabic RTL Layout Problems and How to Solve Them
Building an Arabic training presentation exposes problems that never appear in English decks, and most of them are not translation problems. Flipping text direction changes reading order, which changes where the eye lands, which breaks layouts that were designed around a left-to-right scan. Add English technical terms inside Arabic sentences and numbers that stay left-to-right regardless, and you get decks that are technically correct and visibly wrong. Whether slides come from an AI Course Builder or PowerPoint, the fixes are the same. What Actually Breaks 🖥️ Sign In to Access Your Dashboard Reading Order Changes Where Emphasis Lands In a left-to-right deck the eye starts top-left. Designers put the most important element there without thinking about it. In an Arabic deck the eye starts top-right. A layout with the headline top-left and supporting detail on the right now leads with the detail. The slide is not mistranslated; it is misdirected, and the effect compounds across a fifty-slide deck. The fix is mirroring the layout rather than only the text. Titles move right, bullet indentation reverses, image and text columns swap, and navigation elements follow. Most presentation software handles paragraph direction automatically and does not handle any of this, which is why decks that pass a text check still look wrong. Bidirectional Text Is the Hard Part Arabic runs right to left. Numbers run left to right. Latin-script terms run left to right. Real training content mixes all three constantly. A sentence containing an Arabic explanation, an English product name, and a figure has three direction changes in one line. This is bidirectional text, and rendering it correctly is genuinely difficult. What breaks in practice: Two mitigations. Keep Latin-script terms to a minimum in Arabic content, substituting Arabic equivalents where they exist and the audience accepts them. And check every slide containing a mixed-direction line visually, because automated checks will not catch these. Charts and Diagrams Must Be Mirrored Text direction is the visible half of the problem. Visual flow is the half people miss. Process diagrams: A left-to-right flow reads backwards in an Arabic deck. Mirror the sequence and reverse the arrows. Bar charts with time on the x-axis: Time should progress right to left, matching reading direction. Left unchanged, the chart implies the trend runs the wrong way. Numbered lists: Numbers sit to the right of the text. Icons implying direction: Arrows, progress indicators, and “next” affordances all need reversing. Element English deck Arabic deck Title position Left Right Bullet indentation Left Right Process flow Left to right Right to left Time axis Left to right Right to left List numbering Left of text Right of text Directional icons Point right Point left Numerals Left to right Left to right, unchanged Note the last row. Numerals do not mirror. Attempting to reverse them is a common and confusing error. Typography Differences That Matter Arabic script has different metrics from Latin script, and applying English typographic settings produces cramped, hard-to-read slides. Line height: Arabic needs more, because letters extend above and below the baseline more than Latin characters. Increase leading by roughly 20% over your English setting. Font size: Arabic at the same point size reads smaller. Increase by one to two points for equivalent legibility. Text length: Translated Arabic typically runs 20 to 25% shorter than English. Text boxes sized to English content will look empty, so layouts need adjusting rather than reusing. Font choice: Not every font has usable Arabic coverage. Test with your actual content, since fonts that render headings acceptably often fail on diacritics or extended characters. 📄 Generate a Free PDF Sample Course in Your Cloned Voice Bilingual Decks: Parallel, Not Combined Providers often ask for one deck carrying both languages. It rarely works. Two languages on one slide halves the space available to each, produces competing reading directions on a single surface, and doubles the cognitive load for learners who only need one. The result serves neither audience well. Parallel versions work better. One source, two outputs, generated together so they cannot drift. Learners get a deck in their language, and the deck is designed for that language rather than compromised between two. The exception is a glossary or terminology slide, where side-by-side presentation is the point. Keep those bilingual and make everything else parallel. The same variant logic applies here as in reusable course architecture. Keeping Both Language Versions Aligned To be clear about scope: generated slides follow templates, so RTL correctness depends on the template being built for it. A template designed for English and switched to Arabic will carry the layout problems described above. What generation changes is that both language versions come from one source. When content updates, both regenerate rather than one being edited and the other quietly falling behind, which is the usual fate of manually maintained bilingual decks. For a provider delivering bilingual programmes across 15 courses Metric Before After Arabic decks available 4 of 15 15 of 15 Time to produce an Arabic deck 1 week Same day Versions drifting after content update Routine None Slides requiring manual RTL correction Every one Mixed-direction only Fixing an RTL Deck in Seven Steps Frequently Asked Questions If your Arabic decks were made by switching text direction on an English template, the layout problems are still there. Rebuild the template rather than fixing slides individually. 👉 Book a Live Platform Demo with an EdTech Expert