Call us +971 54 558 2333Urgent legal translation in 2–3 hoursUrgent: 2–3 hours

Service preparation

Preparing String Files for App Localisation

Useful localisation files connect each piece of text to its purpose in the product. A clean export and enough screen context reduce ambiguity and make review easier. Before sending an app or software project, agree the target locales, source version and the files your team can import after translation.

Prepare your service request

Tell us your requirements and deadline. We confirm the scope, price and delivery before work begins.

View service

Export strings with stable identifiers

Use the product’s supported export format, such as XLIFF, JSON, PO or an agreed spreadsheet. Keep string identifiers separate from translatable text. Explain which parts must remain unchanged so variables and technical elements are not mistaken for content.

  • Identify placeholders, tags, links and protected product names.
  • Include plural forms and any length limits that affect the interface.
  • Mark strings that are obsolete, already approved or outside the release.
Preparing String Files for App Localisation — ALMUTARJEM, +971 54 558 2333, hello@mutarjem.ae
ALMUTARJEM · +971 54 558 2333 · hello@mutarjem.ae

Add context and terminology

A label such as “Open” can describe an action or a status. Screenshots, developer notes or staging access show the intended meaning. Share existing approved translations and explain which brand terms stay in their original form.

  • Link screenshots to string IDs where possible.
  • Provide a glossary and the audience or tone of the product.
  • Identify repeated text that has a different meaning on another screen.

Plan a language review in the interface

After translated strings are imported, an agreed staging review can identify truncation, inconsistent labels, mixed-language text and Arabic direction issues. This language and presentation review is different from functional testing or implementing code fixes. Name the developer or product contact who will act on the findings, and agree which screens and review rounds are included.

  • Supply a review build and access instructions without live customer data.
  • Agree the format for reporting a screen, issue and suggested correction.
  • Send later changes as an identified release or update set, not an unmarked replacement.

Related services