Translation Workflows & Terminology
Practical guidance for translators and localisation teams — keep your EN↔AR terminology consistent across projects, CAT tools, and export formats.
What this guide covers
Use TermScan to check EN→AR term consistency inline — paste a paragraph, get a validation report.
Build and export terminology databases in JSON, CSV, or TBX with GlossExport — filtered by domain and jurisdiction.
Guidance for connecting Taqnilex to MemoQ, Trados Studio, and other CAT environments via TBX or REST API.
TermScan — inline term validation
TermScan analyses a block of English or Arabic text and cross-references every technical term against the Taqnilex corpus. It flags terms that diverge from authoritative sources and suggests the validated equivalent — ranked by source authority and ★ Harmonised status.
CAT-tool integration: MemoQ & Trados
Keep your termbase synchronised with your CAT environment. Taqnilex exports are compatible with major translation platforms.
Import a Taqnilex TBX glossary as a MemoQ term base. The ★ Harmonised badge and source authority are preserved as term metadata, visible in the Translation Results pane.
- Export your domain glossary from GlossExport (TBX format)
- In MemoQ: Term bases → Import → TBX
- Set the term base as default for your EN→AR project
Use a Taqnilex CSV glossary as a Trados termbase via the Termbase Converter or import directly into MultiTerm.
- Export your glossary from GlossExport (CSV format)
- In Trados: MultiTerm → Import → CSV, map columns (EN source, AR target, domain, source authority)
- Enable term recognition in your project settings
Teams on the PRO or ENTERPRISE plan can query Taqnilex directly from their CAT tool via the REST API. No export/import cycle — term lookups happen in real time during translation. Get an API key →
TBX export & validation
Export terminology glossaries filtered by domain (patent, legal, medical, pharma, energy, construction, IT) and jurisdiction. Choose JSON, CSV, or TBX format.
Open GlossExport →Check your TBX file for structural issues, missing fields, and provenance badges before submitting to a client or regulator.
Open TBX Validator →Translator's quality checklist
- Verify authoritative source matches — for each technical term, confirm it matches the source authority expected by your client (WIPO for patents, Arabterm for regulatory, UN for diplomatic).
- Run LRA checks for patient-facing text — if translating ICFs, PILs, or patient education materials, ensure the Arabic reads at LRA ≥ 60.
- Prefer ★ Harmonised terms — when multiple equivalents exist, the ★ badge signals the term has been formally validated by ALECSO and is most likely to be accepted across MENA regulators.
- Export TBX for project memory — after finishing a project, export the validated terminology as a TBX glossary for reuse and client handoff.
- Run TermScan on final draft — before delivery, paste the full translated text into TermScan for a last-pass consistency check.