linglo is built by one person, in Tunisia. That is not a humblebrag — it is the reason the product exists.
Every big translation tool supports Arabic. Open one, run a real document through it, and look at what comes back: letters that refuse to join, a layout flipped into nonsense, page numbers stranded on the wrong side, tables collapsed into rubble. It technically supported Arabic. It just did not respect it.
That happens because in most of these products Arabic is locale #27 — a row in a spreadsheet, added late, tested never. Right-to-left is treated as a rendering bug to be worked around rather than how half a billion people read. If you have ever received an Arabic PDF back from a translation tool and quietly rebuilt the whole thing by hand, you already know exactly what I mean.
I got tired of rebuilding documents by hand. So linglo starts from the other end: Arabic first, and the layout is not allowed to break. Joined letters. Real right-to-left. Tables, footnotes and figures that stay where the author put them. Registers that match how official documents are actually written in Tunis, Rabat, Cairo, Beirut or Riyadh. Western digits, because that is what those documents actually use. The other 44 languages came afterwards, and they work — but they were never the point.
There is no support team, no sales team and no roadmap committee. When you email [email protected], it reaches the person who wrote the code. When something is broken, you are talking to the one human who can fix it — and who would rather hear about it than not.
It also means linglo can do things a larger company cannot justify: care about how a Tunisian ministry writes a date, or spend a week on footnotes that overflow a page. That is the whole advantage, and I intend to keep it.
— Safouene, Tunis
Throw a real document at it.
Start freeMore:
All formatsFAQPricingPrivacy
Home · Pricing · Privacy · Terms · [email protected]