Localisation Services

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

Localisation Formats We Handle

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.

Typical structured and mixed-content projects 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 and kept consistent.

How We Approach Localisation

Our localisation work follows a structured, tool-supported process:

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

Localisation Workflow – I18n & L10n

I18n (Internationalisation) prepares the product so it can be translated without code changes.
L10n (Localisation) adapts the content for the target language using translation kits, TEP workflow, UI checks, and functional testing.

I18n → L10n Sequence

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