Support/Project Process/Do you handle multi-language or localised projects?
Project Process

DO YOU HANDLE MULTI-LANGUAGE OR LOCALISED PROJECTS?

668 views
localisationi18nlanguages

Yes for web and app. Translations supplied by you or your translator; we handle layout, typography, RTL, and locale variants.

What we handle

  • String externalisation in code (i18n-ready architecture)
  • Layout adjustment for variable string length (German often ~30% longer than English)
  • Right-to-left layout flipping for Arabic, Hebrew, Persian
  • Locale-aware typography (CJK font fallbacks, diacritic support, ligature-aware kerning)
  • Number, date, and currency formatting per locale
  • Locale-specific imagery and tone where appropriate

What we do not handle

  • Translation itself — supplied by you or a translator you nominate
  • Cultural review — supplied by a native speaker on your team
  • Ongoing translation memory management (use Phrase, Lokalise, Crowdin)

Pricing impact

Multi-locale launches are quoted as the base build plus a per-locale uplift covering layout, QA, and asset variants. The uplift is typically smaller than a separate per-locale rebuild because the architecture is shared.

Was this helpful?

Tell us honestly. It is read by the people who write these pages.

If this didn't answer your question, ask Xylo.

Back to Project Process