Guides the AL translation phase — when to translate, how to handle XLF files, and quality expectations for localized texts.
Use this skill after implementation and core review are complete and the app builds successfully.
al-translator agent or perform translation manually.g.xlf fileal-develop-orchestrator or user explicitly triggers the translation phaseal_build or buildAlPackage) to generate the current ..g.xlfTranslations/:
a. Synchronize with refreshXlf.
b. Load glossary (glossary.tsv + getGlossaryTerms).
c. Load existing translations as style reference (getTranslatedTextsMap).
d. Fetch untranslated texts in batches of up to 100 (getTextsToTranslate).
e. Translate, validate, and save each batch (saveTranslatedTexts).
f. Repeat until no untranslated texts remain.
g. Final refreshXlf to confirm completion.%1, %2) in position and formatmaxLength constraints — measure and shorten before savingrefreshXlf — sync XLF with generated .g.xlfgetTextsToTranslate — fetch untranslated textssaveTranslatedTexts — save translations with stategetTranslatedTextsMap / getTranslatedTextsByState — existing translationsgetGlossaryTerms — glossary for target languagegetTextsByKeyword — search texts by keywordbuildAlPackage — compile and generate .g.xlfFall back to direct XLF file editing:
<trans-unit> elements without <target> or with state="needs-translation"<target> elements with the translationstate="needs-review-translation" on new translationsal-translator — the dedicated translation worker that executes this workflowal-develop-orchestrator — triggers the translation phase after successful build