Open Google Docs. Type some Arabic. Notice how the cursor jumps, how the punctuation misaligns, how the mixed English-Arabic text looks like it was arranged by a distracted intern. This isn't a bug — it's the default state of almost every major writing tool when handling right-to-left text.
The Real Cost of Bad RTL
When an editor treats Arabic as an afterthought, the toll isn't cosmetic. It's cognitive.
Every time the cursor misbehaves, your brain context-switches from "what am I writing?" to "how do I make this tool work?" Multiply that by a thousand writing sessions and you get the answer to why so many Arabic writers describe their tools as something they "fight with" rather than "use."
The specific pain points:
- Cursor jumping: Type a Latin word mid-sentence and the cursor lands in an unexpected place
- Punctuation chaos: Periods and commas cling to the wrong words
- Selection nightmares: Selecting text across script boundaries selects unpredictable chunks
- Bidirectional ambiguity: The editor can't guess whether a piece of text is meant to be LTR or RTL
What "Arabic-First" Actually Means
Notion and Google Docs support RTL — technically. You can switch text direction. The text will render from right to left. But the editor wasn't designed with RTL as the default reading experience. The layout, the toolbar, the spacing, the cursor logic — it all assumes LTR as the base case.
An Arabic-first editor inverts that assumption:
- RTL is the default: You don't "switch" to Arabic mode. You're already in it.
- The cursor knows where it is: No jumping. No guessing.
- Mixed text works: When you embed English words in Arabic text, they flow naturally.
- Typography matters: Arabic script needs different line heights, different font weights, different spacing than Latin. A one-size-fits-all approach gives you cramped, hard-to-read text.
Beyond Direction: What Else Should an Arabic Editor Have?
Proper Tashkeel Support
Arabic diacritics (harakat) are tiny marks that can change the meaning of a word entirely. Many editors render them poorly — overlapping, misaligned, or just invisible.
Font Selection That Makes Sense
IBM Plex Sans Arabic, Noto Naskh Arabic, Scheherazade New — these fonts were designed specifically for Arabic readability on screens. Most editors default to fonts optimized for Latin script.
Quranic Citation
For scholars, students, and anyone writing about Islam: being able to search and insert Quranic verses directly with proper formatting (mushaf-style, with surah and ayah numbers) saves enormous time. This isn't a feature you'd think of if you only ever wrote in English.
What Nuss Does
Nuss was built with RTL as the foundation, not a checkbox on a feature list. The editor defaults to Arabic direction. The AI assistant understands Arabic context — not just Arabic words, but the cultural and religious nuance behind them. Quran search is built in, not bolted on.
Try it free at nuss.ink and see what it feels like when a writing tool was made for your language from the first line of code.