Too many teams think of right-to-left support as a niche feature they’ll “add later.” But as Kareem Ennassag, Technical Director at the LangOps Institute, reminds us, you can't serve over 900 million potential users without it. In this episode of Bridging the Gap, Kareem joins Marta G. Coloma and Jan Bílek once again — this time to focus on the complexity behind right-to-left scripts, bidirectionality, and why ignoring RTL in early development often leads to long-term technical debt.

📝 The highlights 🔗

Start small, but plan ahead 🔗

Even if RTL languages are not your priority right now, Kareem argues that preparing your tech stack for RTL early on is easier than getting back to it later. He compares it to technical debt — one that can quietly grow until it blocks your entry into whole markets.

"Start early, start small. Invest a little into it — but it will save you a lot of trouble."

What RTL really means 🔗

Many assume RTL refers to a language — but it’s the script, not the language, that flows right to left. Arabic, Hebrew, Farsi, and Urdu all use RTL scripts. The real challenge appears when left-to-right (LTR) elements, like numbers, links, or brand names, are added to RTL text, creating bidirectional content that breaks without proper support.

Mirroring layout ≠ good UX 🔗

Supporting RTL isn’t just about flipping layouts. Kareem explains how the user journey reverses direction: buttons move, diagrams flip, scroll behavior changes, and common UI patterns no longer make sense if not adapted properly. Bad RTL implementation doesn’t just look strange — it renders products unusable.

Why tools and platforms matter 🔗

Even something as simple as choosing the wrong rich text editor can sabotage your localization plans. Kareem and Jan point out that developers should double-check toolkits for RTL and bidirectional compatibility from the beginning, whether it’s a design component, spreadsheet, or frontend framework.

Better resources than ever 🔗

From W3C and Unicode to guides from Microsoft, Apple, and Google, free, high-quality documentation is widely available. Developers don’t need to reinvent the wheel. The biggest step is knowing that RTL support is something to plan for.

🌟 Star quote 🔗

BTG-guest quote (2).png

🎙️ Watch & listen 🔗

YouTube 🔗

Spotify 🔗

🗞️ Additional resources 🔗

Having language support from the beginning pays off | Bridging the Gap Podcast, S02 EP04
**When should localization start? Kareem Ennassag explains why language operations are a mindset — not a feature to bolt on later when translations are needed.**
LocalazyBridging the Gap
AI, sign language & accessibility | Bridging the Gap Podcast, S01 EP08
Is accessibility for the Deaf community evolving thanks to AI? What does it have in common with localization? We talk to Signapse’s co-founder, Sally Chalk, to find out.
LocalazyBridging the Gap
📲 Follow the podcast on LinkedIn to be notified when we release a new episode!

💌 Connect with the guest & hosts 🔗

📚 More on the blog 🔗

Learn more about approaching RTL languages, and Arabic in particular, with this short guide by Arabic localization and BPO veteran Ahmed Megahed, who brings over 17 years of experience in the field. And if you're curious about how global brands like Netflix, Amazon, or Alibaba have tackled their entry to this market, make sure to check the piece below. ⬇️

What I’ve learnt localizing for Netflix and other global brands for the Arabic market
Some Western brands enter Arabic-speaking markets fully understanding their nuances. Others simply fail because they don’t. These are my top tips after 17 years working in the field.
LocalazyAhmed Megahed

🚀 About Localazy 🔗

Localazy helps you prepare, launch, and manage multilingual content at scale. Whether you’re just starting out or expanding into new markets, Localazy provides tools for automation, quality translation, and structured localization workflows.

Explore how to get started here, choose a plan, or contact us for support.