Persian (Farsi) Software Localization
Native Farsi linguists translate your web, desktop and mobile software, protect every half space and check the right-to-left interface in a real build before each release ships.
- Languages
- 19
- Languages
- Vetted Native Linguists
- 700+
- Vetted Native Linguists
- Localization Tasks / Year
- 100K+
- Localization Tasks / Year
- Founded
- 2016
- Founded
El Turco provides Persian (Farsi) software localization services for SaaS companies, enterprise product teams and LSPs. Native Farsi linguists translate interface strings, help articles and release notes under ISO 17100 and then test the right-to-left build in context. Our Istanbul production team manages each project, with headquarters in London and unreleased builds kept under NDA and ISO/IEC 27001.
Persian software localization adapts the interface, documentation and locale settings of a product so Farsi readers use it as if it had been built in Persian. Persian shares a script with Arabic but needs its own handling. Farsi has its own letters, digits and calendar. It also depends on an invisible half space that string pipelines often strip. Product teams that own the software come first for us. LSPs that need a native Persian software desk inside their own workflow come second.
Shared workflow: Translation & Localization and Technology & IT.
Scope
What does Persian software localization cover?
UI strings
Menus, buttons, field labels, error messages and notifications in Persian, kept inside length limits with placeholders, tags and ICU variables untouched.
Help center and documentation
Knowledge base articles, setup guides, admin documentation and API reference text, with every UI term matched to the Persian interface.
Release notes and in-app messages
Changelogs, what's new screens, product emails and push notifications in the formal register your product uses.
App store listings
Store titles, descriptions, keywords and screenshot captions in Persian, plus a list of screenshots that need a right-to-left version.
In-context linguistic review
Farsi reviewers open your build or staging site and report mirroring errors, clipped text, broken bidirectional lines and wrong characters, each with a screenshot.
Persian specifics
What makes Persian different for software localization?
Persian versus Arabic characters
Arabic yeh and kaf look almost identical to the Persian letters on screen but use different code points. Mixed characters break search, sorting, filters and deduplication. We normalize every delivery to Persian characters and flag source data that needs the same fix.
The half space
The zero-width non-joiner, or half space, keeps parts of one Persian word apart without a real space, as in the verb prefix mi- and the plural suffix -ha. Some string extractors, CMS fields and sanitizers remove it, so letters join wrongly. Our QA confirms half spaces survive the round trip into the build.
Right-to-left and bidirectional text
Navigation, form fields and directional icons flip to right to left. Brand names, URLs, file paths and placeholders in Latin script sit inside Persian sentences and need direction handling so punctuation lands in the right place.
Digits, calendar and currency
Persian has its own digits, distinct from Arabic-Indic digits for four, five and six. Iran uses the Solar Hijri calendar with the week starting on Saturday. Prices may be shown in rial or toman, so every currency string states its unit. These settings are fixed per locale before translation starts.
Formal register and word order
Business software addresses users with formal "shoma" and plural verbs. Persian is verb-final, so English fragments that start with a verb are rebuilt as natural Persian phrases. Concatenated strings are replaced with full sentences.
Plurals and placeholders
Nouns stay singular after a number, so ICU "one" and "other" often carry the same text. The ezafe linking vowel depends on the word before it, so we keep variables at phrase edges.
Process
How we run a Persian software localization project
Turnaround is agreed at scoping, with a 24-hour option for small urgent updates.
Step 1
Scoping
We review file formats, string volume, release cadence and target variety, then agree register, digit style, calendar and currency unit. Iranian Persian is the default target, with Dari confirmed separately where needed. The pilot is free.
Step 2
Glossary and style guide
A shared glossary fixes product terms, UI labels and whether each feature name stays in English, is translated or is transliterated. The style guide records loanword choices and the half-space rules.
Step 3
TEP translation
A native Persian translator, a second native editor and a final proofreader work on every file under ISO 17100. MTPE under ISO 18587 is used only where content suits it, after character normalization.
Step 4
What's Wrong? QA
Before any file returns to your repository, What's Wrong?, our own QA tool, confirms that placeholders, tags, length limits, glossary terms, numbers and Persian letters are all correct.
Step 5
In-context review
Reviewers test the Persian strings in your build, attach a screenshot to each issue and confirm the fixes once the next build is ready.
Step 6
Continuous localization
Each new string reaches the Persian team from your Git repository, your TMS or Hub, our middleware. Translated strings go back the same way. Turnaround is agreed at scoping, with a 24-hour option for small urgent updates.
Industries
Who buys Persian software localization?
Related
Language page
Persian translation and localization
Native Persian (Farsi) linguists for right-to-left software, game, e-commerce and marketing content, plus Persian AI training data.
Same language
Persian Game Localization
Persian in-game text, right-to-left UI, store pages and in-build LQA for mobile, PC and console titles, in formal or colloquial Farsi.
Same language
Persian E-Commerce Localization
Persian product catalogs, right-to-left storefronts, checkout and campaigns by native Farsi linguists, with MTPE for large catalogs.
Same language
Persian AI Training Data
Farsi speech, annotation, RLHF, moderation and MT datasets built by native speakers, with Persian character normalization and agreement reports.
Same service
Turkish Software Localization
UI strings, help content, release notes and store listings in Turkish, with continuous localization through your TMS or repository.
Same service
Arabic Software Localization
Arabic UI strings, right-to-left layout review, help content and release notes, delivered through continuous localization for SaaS and enterprise software.
FAQ
Persian software localization FAQ
Does El Turco test the Persian interface as well as translate it?
Persian software localization at El Turco covers both translation and in-context testing of the interface. Native Farsi reviewers work in the Persian build or staging site and check right-to-left mirroring, bidirectional lines with Latin text, truncation, half spaces, Persian characters and terminology. Every issue comes with a screenshot and a proposed fix. The reviewer confirms the fix once the next release is ready.
Why do Persian strings break when they pass through our software?
Persian strings usually break for two reasons. Some extractors and sanitizers strip the zero-width non-joiner, the half space Persian uses inside words. Text copied from Arabic sources also carries Arabic yeh and kaf, which disrupt search and sorting. El Turco normalizes characters, checks half spaces with What's Wrong? QA and reports pipeline steps that need a developer fix.
Which file formats and tools does El Turco support for Persian software?
El Turco translates Persian software in JSON, XLIFF, PO and RESX resource files and in documentation exported from your help center. Farsi linguists work in RWS Trados, memoQ, Phrase and XTM, where ICU plural syntax, placeholders and tags are protected. What's Wrong? QA also checks Persian characters and half spaces in each file before it returns to your repository or TMS.
How does continuous Persian localization fit our release cycle?
Continuous Persian localization links El Turco to your Git repository, your TMS or Hub, our in-house middleware. A Persian team picks up each new string as developers commit it and returns the translation ahead of the release. Turnaround is agreed at scoping, with a 24-hour option for small urgent updates, so Persian ships in the same deployment as English.
Can LSPs subcontract Persian software localization to El Turco?
LSPs can subcontract Persian software translation, editing and in-context review to El Turco and deliver the work under their own brand. Farsi linguists join the CAT tool or TMS of the LSP and apply the style guide and glossary of the end client. LSPs can try the team first with a free 300-word test translation. Pricing is per-word, hourly or project-based, quoted after scoping.
How does a Persian software localization project start?
A Persian software localization project starts with the contact form, where you share the product type, file formats, string volume and release cadence. El Turco then proposes a plan for translation, in-context review and continuous updates. Product teams can ask for a free pilot first. Unreleased strings stay under NDA and inside the ISO/IEC 27001 information security system.
Ready to Scope Persian Software Localization?
Share the content type, volume and timeline for a scoped plan. A free pilot comes first if you want proof before committing. Pricing is per-word, hourly or project-based, quoted after scoping.