Translation Skill

state="new"

Workflow

Step 1: Find Changed Translation Files

git diff --name-only | grep -E 'messages\.[a-z]{2}\.xlf$'
git diff --cached --name-only | grep -E 'messages\.[a-z]{2}\.xlf$'

Step 2: Extract New Translations

.xlf

1. Read the file content
2. Parse to find all

   <trans-unit>

   elements
3. Filter for those containing

   <target state="new">

4. Extract for each:

   • id

     attribute (translation ID)

   • <source>

     content (English text)

   • <target>

     content (current translation, may be empty or placeholder)
   • Any placeholder elements (

     <x .../>

     )

Step 3: Find Source Context

$localize

grep -r "@@{ID}:" --include="*.ts" apps/ libs/

i18n

grep -r "@@{ID}\"" --include="*.html" apps/ libs/

Step 4: Generate & Review Translations

state="new"

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Translation ID: {id}
File: {xlf_file_path}
Target Language: {language_name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Source (English):
  {source_text}

Context:
  {file_path}:{line_number}
  {code_snippet}

Proposed Translation:
  {proposed_translation}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

• Accept the proposed translation
• Provide an alternative translation
• Skip this entry

Step 5: Apply Approved Translations

1. Replace the

   <target>

   element content with the approved translation
2. Change

   state="new"

   to

   state="ai"

<trans-unit id="myTranslationId" datatype="html">
  <source>English text</source>
  <target state="new">Old or empty translation</target>
</trans-unit>

<trans-unit id="myTranslationId" datatype="html">
  <source>English text</source>
  <target state="ai">Translated text</target>
</trans-unit>

Language Detection

messages.de.xlf

messages.fr.xlf

messages.es.xlf

messages.hu.xlf

Placeholder Handling

<x id="INTERPOLATION" equiv-text="{{...}}"/>

{{count}}

<x id="INTERPOLATION_n"/>

<x id="PH" equiv-text="..."/>

<x id="PH_n"/>

<x id="LINE_BREAK" ctype="lb"/>

<br>

<x id="START_TAG_SPAN"/>

<span>

<x id="CLOSE_TAG_SPAN"/>

</span>

<x id="START_BOLD_TEXT"/>

<b>

<x id="CLOSE_BOLD_TEXT"/>

</b>

<source>Hello <x id="INTERPOLATION" equiv-text="{{name}}"/>, you have <x id="INTERPOLATION_1" equiv-text="{{count}}"/> messages.</source>
<target state="ai">Hallo <x id="INTERPOLATION" equiv-text="{{name}}"/>, Sie haben <x id="INTERPOLATION_1" equiv-text="{{count}}"/> Nachrichten.</target>

Translation Guidelines

1. Match existing tone: Review other translations in the file to maintain consistent style
2. Preserve placeholders: Copy placeholder elements exactly, only translate surrounding text
3. Consider context: Use the code context to understand how the text is used
4. Domain terminology: Use standard terms for:
   • Mobility/transport: commute, emissions, CO2, modal split
   • UI elements: buttons, labels, tooltips
   • Business terms: audit, score, analysis
5. Formal vs informal: German typically uses formal "Sie" form in business software

Common Translation Patterns

German (de)

• "Save" → "Speichern"
• "Cancel" → "Abbrechen"
• "Loading..." → "Wird geladen..."
• "Error" → "Fehler"
• "Success" → "Erfolgreich"

French (fr)

• "Save" → "Enregistrer"
• "Cancel" → "Annuler"
• "Loading..." → "Chargement..."
• "Error" → "Erreur"
• "Success" → "Succes"

Spanish (es)

• "Save" → "Guardar"
• "Cancel" → "Cancelar"
• "Loading..." → "Cargando..."
• "Error" → "Error"
• "Success" → "Exito"

Hungarian (hu)

• "Save" → "Mentes"
• "Cancel" → "Megse"
• "Loading..." → "Betoltes..."
• "Error" → "Hiba"
• "Success" → "Sikeres"

Batch Processing

1. Group by file for efficiency
2. Show a summary of how many entries need translation per file
3. Process entries one at a time, waiting for approval
4. After all entries are reviewed, show summary of changes made

Error Handling

• If no changed translation files found: Inform user and suggest running

  git status

• If no

  state="new"

  entries found: Inform user that all translations are up to date
• If context not found: Still propose translation based on source text alone, note missing context
• If file parse error: Report the error and skip the problematic file