Use case

The official document, in both languages.

Ministries and agencies publish decrees, circulars, and reports in Arabic and English. TranslateX turns the signed original into a publish-ready edition in the other language, keeps official terminology exact through governed glossaries, routes every document through human review, and runs entirely inside your own network when policy requires it.

Bilingual publishing

The Arabic original and the English edition,
from the same file.

A circular is signed in Arabic in the morning. The English edition used to mean a translation office, a designer, and a week. With TranslateX it is one click and a review.

Decrees, circulars, reports

Official documents come out looking official.

Ministries and agencies publish in a fixed visual language: numbered articles, tables of entities, stamps, headers, annexes. TranslateX rebuilds the translated document in that original design, so the English edition of a decree carries the same structure as the Arabic instrument it mirrors, and an annual report keeps its charts and tables in place.

Arabic and English is the flagship pair, and the hard part is direction. When the page flips between RTL and LTR, TranslateX mirrors the layout so each edition reads naturally in its own script.

  • PDF, Word, PowerPoint, and Excel translated as complete documents
  • Fonts, tables, spacing, and slide structure preserved
  • RTL and LTR layouts mirrored automatically
How layout preservation works
Circular 12-2026.pdfOriginalAR

تعميم رقم (١٢) لسنة ٢٠٢٦

Circular 12-2026 (EN).pdfTranslated copyEN

Circular No. (12) of 2026

Review before publication

Nothing official leaves without a human signature.

Formal documents are reviewed, not just translated. The review editor puts the source and the translation side by side, segment by segment, with statuses your team controls: machine, edited, accepted, locked. A track-changes view shows exactly what the reviewer changed, and automated QA verifies numbers, punctuation, and untranslated segments before the final document is rebuilt in the original layout.

  • Side-by-side segment review with statuses and reviewer notes
  • Track-changes diff against the machine translation
  • QA checks for numbers, punctuation, and missed segments
Document translation and review
Review · Circular 12-2026.pdf
GGeneral Secretariat
Settings
ReviewCircular 12-2026.pdf
Accept allExport
1

يُعمل بهذا التعميم اعتباراً من تاريخ صدوره.

This Circular shall come into effect on its date of issue.

Accepted
2

على جميع الجهات المعنية تنفيذ أحكامه كلٌّ فيما يخصه.

All concerned entities shall implement its provisions, each within its remit.

Edited
3

تُرفع تقارير المتابعة خلال خمسة عشر (15) يوم عمل.

Follow-up reports shall be submitted within fifteen (15) working days.

MTNumber check passed
4

يُنشر هذا التعميم في الجريدة الرسمية.

This Circular shall be published in the Official Gazette.

TM locked
31 segments · 29 accepted · QA: numbers verified

Official terminology

One entity, one name.
In both languages, in every document.

The fastest way to look unofficial is to translate the same ministry three different ways. Terminology governance ends that.

Glossaries and style

Approved terms, enforced by the system.

A government glossary pins the approved rendering of every entity name, honorific, program title, and legal instrument, per language pair, with categories and notes. TranslateX enforces those terms on every job automatically, so the decision made once in a style committee holds in every circular, report, and press statement that follows.

Beyond single terms, style governance applies your organization's writing style to whole documents: the register, the formality, the phrasing your publications are expected to carry.

  • Term bases per language pair, enforced on every job
  • Organizational writing style applied automatically
  • Translation memory reuses wording your reviewers approved
Style governance
Glossary · Official AR-EN
GGeneral Secretariat
Settings
GlossaryOfficial AR-EN
Add termImport
Source termTarget termCategory
Ministerial Decreeقرار وزاريOfficial
Executive Regulationاللائحة التنفيذيةLegal
His ExcellencyمعاليTitles
Official Gazetteالجريدة الرسميةOfficial

Entity names, honorifics, and instrument types rendered one approved way, in every document.

Enforced on every translation job in this workspace

Sovereignty

Runs where your documents
are required to live.

TranslateX is built by Lisan, and more than 24 government entities work with Lisan. That experience shaped the deployment story: sensitive documents should never need a public translation website.

On-prem, air-gapped, sovereign

The whole platform inside your perimeter.

TranslateX deploys in the cloud, in sovereign clouds, or fully on your own infrastructure via Docker, with documented air-gapped installs for networks that never touch the internet. The On Premises (local) model option runs translation itself on your hardware, so neither the documents nor the engine leave the building.

Enterprise controls come with it: roles for admins, managers, translators, reviewers, and viewers, LDAP and Active Directory sign-in, MFA, audit logs with SIEM export, and white-label branding so the platform carries your identity.

  • Docker deployment with documented air-gapped installs
  • Local translation model for fully offline operation
  • LDAP, MFA, audit logs, SIEM export, white-labelling
Security and on-prem
DeploymentWhere documents live
CloudTranslateX managed cloudFastest start
Sovereign cloudYour national or regional cloudData residency
On-premisesYour servers, your networkAir-gapped installs

The On Premises (local) model option keeps the translation engine itself inside the perimeter.

Scans and archives

Older decrees exist only as scans. Press F6, capture the page on screen, and TranslateX reads and translates it instantly. Screen translation

Arabic-first engineering

Native RTL handling, Arabic punctuation, and typography nuance, built as the core of the product rather than an afterthought. Arabic and RTL

Scoped with your entity

Deployment model, white-labelling, and rollout are agreed directly with your team. Write to support@lisan.com to start. Talk to us

Frequently asked questions

Can TranslateX run entirely inside a government network?

Yes. TranslateX deploys via Docker on your own infrastructure, with documented air-gapped installs and an On Premises (local) model option that runs the translation engine itself on your hardware. Sovereign-cloud deployment sits between full on-prem and our cloud. See security and on-prem.

How does it keep official terminology consistent?

Glossaries pin the approved rendering of entity names, honorifics, and legal instruments per language pair, and TranslateX enforces them on every job. Style governance applies your organization's writing style on top, and translation memory reuses wording your reviewers already approved. See glossary and memory.

Is a machine translation published directly?

Not unless you choose to. The review editor gives your own reviewers side-by-side segments, statuses, a track-changes diff, and automated QA checks on numbers and punctuation. The final document is rebuilt in the original layout only after review.

What Arabic does TranslateX translate?

Modern Standard Arabic, the register official documents are written in, with native RTL and LTR handling, Arabic punctuation, and typography nuance. Arabic and English is the flagship pair among more than 20 supported languages. See Arabic and RTL.

Does Lisan work with government today?

Yes. More than 24 government entities work with Lisan, the company behind TranslateX. Deployments are scoped directly with each entity: write to support@lisan.com or use the contact page.

Translate the document. Keep the design.

Right-click a file, work inside Office, or press F6 on anything on screen. TranslateX returns the same document in the other language: fonts, tables, and layout intact, terminology on brand.

Arabic, English & more · Layout preserved · On-premises available