Localisation Services (L10n)

Localisation (often written as L10n, because there are 10 letters between “L” and “n” in the word
Localisation) is the process of adapting software, websites, help files and user interfaces for different
languages and regions.

To support this work, we established a dedicated company:
L10n Infopreneur Private Limited, focused only on software and content localisation.

Our Localisation Tools and Licenses

Alchemy Catalyst (Developer Edition) We hold a developer license of Alchemy Catalyst, which allows us to: create translation kits for software, UI strings, resource files and structured content extract, manage and protect tagged text maintain layout consistency across multiple languages prepare build-ready target files for translators and reviewers Alchemy Catalyst has been part of our workflow for more than two decades, and we use it for both small UI modules and large enterprise applications.

SDL Trados We also maintain multiple licenses of SDL Trados, used for: terminology management TM maintenance and alignment multi-file localisation projects large-scale consistency checks across languages These tools allow us to handle a wide range of modern and traditional localisation formats, including: XML / XLIFF (1.2 and 2.0) JSON (web apps, APIs, mobile apps) YAML (DevOps and configuration files) HTML / XHTML RESX (.NET applications) .properties (Java applications) resource DLLs Markdown (.md) Android XML iOS .strings and .plist files

Structured Documentation and Mixed-File Projects

Many localisation projects today include bundles of different file types that must stay consistent across manuals,
help files, UI text, and online content. SDL Trados helps manage these in a single workflow.

Examples include:

• DITA XML files (e.g., *.dita, *.ditamap)
• DocBook XML (*.xml) used for technical manuals
• Help system files such as HTML Help (*.htm, *.html, *.hhp, *.hhc)
• Markdown documentation (*.md) for software and API guides
• Software UI + documentation mixes, for example:
  • *.resx (UI strings)
  • *.json (web/app strings)
  • *.md (documentation)
  • *.xml (config/help content)

These combinations are common in software products, SaaS platforms, engineering equipment manuals, and developer
documentation, where both UI text and long-form content must be translated together.

How We Approach Localisation

Our localisation process is designed to preserve technical accuracy, UI quality and long-term consistency across releases.

• Analyse files for internationalisation (I18n) issues
• Build translation kits using Alchemy Catalyst
• Establish terminology lists and style rules for UI consistency
• Translate and edit strings following TEP (Translate–Edit–Proofread) principles
• Perform pseudo-translation checks
• Rebuild target files and validate UI layout
• Create and maintain TMs for long-term projects

I18n → L10n Sequence

1. I18n Review
   Check if files are localisation-ready: formats, tags, encoding, UI issues.
2. Build Translation Kits
   Alchemy Catalyst: extract and protect tagged content.
3. Terminology & Style Guide Setup
   Glossary, UI rules, abbreviations, tone.
4. Translation (Human TEP)
   – Translate
   – Edit and proofread
   – Maintain TM consistency in Trados.
5. Pseudo-Translation Check
   Detect UI expansion problems, tag issues, encoding errors.
6. Rebuild Target Files
   Create final translated files; validate structure.
7. UI Layout Review
   Check truncation, overlap, spacing, directionality.
8. Functional Testing
   Menus, buttons, messages, navigation behaviour.
9. Final Delivery
   Localised files + updated TM + terminology updates.

Note:

• Alchemy Catalyst supports Steps 1, 2, 5 and 6.
• SDL Trados supports Step 4 and ongoing TM management.

This single workflow covers both I18n preparation and L10n execution, providing a
complete localisation pipeline for software and content.