Outil de traduction strings.xml Android

strings.xml Android avec prise en charge de CDATA et des string-array

Aucune connexion requise À partir de $19 Sûr pour les variables

Le problème

  • Les sections CDATA cassent dans les analyseurs XML génériques
  • Les entités HTML (&, <) sont doublement encodées
  • La structure des string-array se perd
  • Les spécificateurs de format %1$d sont mal traduits

La solution

  • L'analyseur XML Android préserve CDATA
  • Entités HTML gérées correctement
  • Structure string-array et pluriels préservée
  • Spécificateurs de format (%1$d, %s) verrouillés

Avant et après traduction

Découvrez à quoi ressemblent les fichiers Android XML avant et après la traduction IA. Les variables restent intactes.

Original (anglais)

Nombre de mots : 28
<resources>\n  <string name="greeting">Hello {player_name}!</string>\n  <string name="newline">Line 1\nLine 2</string>\n  <string-array name="items">\n    <item>Sword</item>\n    <item>Potion</item>\n  </string-array>\n  <string name="count">%1$d items found</string>\n</resources>

Traduit (espagnol)

28+ langues
<resources>\n  <string name="greeting">¡Hola {player_name}!</string>\n  <string name="newline">Línea 1\nLínea 2</string>\n  <string-array name="items">\n    <item>Espada</item>\n    <item>Poción</item>\n  </string-array>\n  <string name="count">%1$d objetos encontrados</string>\n</resources>

Remarque : Toutes les variables (comme {pattern}) restent complètement inchangées dans la version traduite.

Modèles de protection des variables

Les fichiers Android XML contiennent des modèles spéciaux qui ne doivent jamais être traduits. Notre IA les verrouille automatiquement.

Verrouillé
{player_name}

Accolades

Verrouillé
%1$d

Format Android

Verrouillé
%s

Printf

Préservé
<![CDATA[

CDATA

Préservé
&amp;

Entité HTML

Prêt à localiser votre jeu Android ?

Téléchargez votre fichier Android XML et obtenez une traduction IA sécurisée pour les variables en 24 heures. Aucune connexion requise. À partir de $19 par fichier.

24 heures · Variables sécurisées · 28+ langues

Translate Android strings.xml online — without breaking your app

Your res/values/strings.xml is where every language version of your app starts. Translating it by hand means keeping %1$s, %2$d and string-array blocks in sync across values-es/, values-fr/ and a dozen more folders — the kind of busywork that eats a release week. Generic AI tools see %1$d and happily translate it into broken text. LocaFile AI is an Android strings.xml translator that locks your format specifiers before the AI ever sees them.

Upload your strings.xml, pick a pass, and get back files ready to drop into res/values-<lang>/ — 28 languages, same keys, same structure, only the values translated. No login required, pay-per-pass from $19, engine-aware instead of a generic XML shortcut.

A string.xml translator that respects Android resource rules

LocaFile AI parses strings.xml the way Android actually reads it: <string>, <string-array> and <plurals> nodes are handled separately, CDATA sections and HTML entities are preserved byte-for-byte, and positional format specifiers (%1$s, %2$d) are locked so plural rules and String.format() calls keep working in every language.

The result is a file you can drop in and ship — not a translation you have to hand-repair. That is the point of an Android XML translation tool that understands the format it translates.

Android strings.xml translation — FAQ

How do I translate Android strings.xml online?

Upload your strings.xml, choose your languages, pay for a pass, and download the translated files. No login required — your download link is your recovery key. Pay-per-pass from $19, with no per-word or per-language fees.

Is there an Android string translation tool that localizes strings.xml automatically?

Yes — LocaFile AI is an engine-aware strings XML translator. It parses res/values/strings.xml the way Android does, locks format specifiers, translates the values, and returns files ready to drop into values-<lang>/. From $19 per pass, no login, no subscription.

Will translating strings.xml break my %1$s or %1$d format specifiers?

No. Positional format specifiers like %1$s, %2$d and %s are locked with regex token replacement before the AI sees your text, then restored byte-for-byte after translation. Your String.format() calls keep working in every language.

Does it handle string-array and plurals?

Yes. string-array and plurals blocks are parsed and translated as their own structures, so item order and plural quantities stay intact.

Where do I put the translated strings.xml files?

Each translated file drops straight into res/values-<lang-code>/strings.xml — for example values-es/ for Spanish. Keep the same filename and Android picks the files up automatically.

What about CDATA sections and HTML entities?

CDATA sections are preserved byte-for-byte and HTML entities are left alone, so rich text and encoded characters are not double-encoded or mangled.

How much does translating Android strings cost?

From $19 per pass, one-time, no subscription. You choose how many languages you need — the pass covers them. No per-word pricing, no login required.