A module to keep XLIFF translation files in sync with a specified, automatically generated base-XLIFF file.
This PowerShell module is based off the XLIFF Sync VSCode extension.
Initial version with support for XLIFF 1.2 (support for XLIFF 2.0 follows later).
You need to have Powershell 5.0 or newer. This module uses classes.
You can install the module from PowerShell Gallery by running:
Install-Module -Name XliffSyncThe Sync-XliffTranslations function will synchronize translation units and translations for a specified base/source file and target file.
To use the function you will need to specify the path to the base/source file (-sourcePath) and a path to the target file (-targetPath) or a target language (-targetLanguage).
An example usage:
Sync-XliffTranslations -sourcePath "C:\MyProject\My Project.g.xlf" -targetPath "C:\MyProject\My Project.nl-NL.xlf" -findByXliffGeneratorNoteAndSource -findByXliffGeneratorAndDeveloperNote -findByXliffGeneratorNote -reportProgressThe function will try to find matching trans-units and translations within a target file as follows:
- Finding trans-units:
- By Id
- By XLIFF Generator Note & Source (controlled by switch
findByXliffGeneratorNoteAndSource)- By XLIFF Generator Note & Developer Note (controlled by switch
findByXliffGeneratorAndDeveloperNote)- By XLIFF Generator Note (controlled by switch
findByXliffGeneratorNote)
- Finding translations:
- By Source & Developer Note (controlled by switch
findBySourceAndDeveloperNote)- By Source (controlled by switch
findBySource)
- Initial translation:
- Parse from Developer Note (controlled by switch
parseFromDeveloperNote)- Copy from Source if source-language = target-language (controlled by switch
copyFromSource)
If no trans-unit or translation is found, the unit is added and its target node is tagged with state="needs-translation".
Please check the documentation of the function for more information and the available parameters.
The Test-XliffTranslations function (alias: Check-XliffTranslations) will check for missing translations and/or for problems in translations in a specified XLIFF file.
To use the function you will need to specify the target file (-targetPath) and whether you want to check for missing translations (-checkForMissing) and/or problems in translations (-checkForProblems).
If you let the function check for problems, then you can use the translationRules parameter to specify which technical validation rules should be applied.
An example usage:
$unitsWithProblems = Test-XliffTranslations -targetPath "C:\MyProject\My Project.nl-NL.xlf" -checkForMissing -reportProgressWhen finished the function will report the number of missing translations and number of detected problems.
Translation units without translations will be marked with state="needs-translation" and translation units with a problem in the translation will be marked with a 'needs-work' state and an "XLIFF Sync"-note that explains the detected problem.
The function will return the translation units with problems, which you can assign to a variable (e.g., $unitsWithProblems) or omit, to have the output printed.
If you use the -printProblems parameter, then you can use the -FormatTranslationUnit to specify which part of the trans-units should be printed.
The default value for this parameter is set to show the ID of the trans-unit, i.e.:
-FormatTranslationUnit { param($TranslationUnit) $TranslationUnit.id }For Business Central app translation use cases, you could change this to show the XLIFF Generator note, which is also the default for Test-BcAppXliffTranslations, i.e.:
-FormatTranslationUnit { param($TranslationUnit) $TranslationUnit.note | Where-Object from -EQ 'Xliff Generator' | Select-Object -ExpandProperty '#text' },Please check the documentation of the function for more information and the available parameters.
The Get-XliffTranslationsDiff function will compare an original and new version of an XLIFF file and produce a new XLIFF Diff file that contains all the translation units that were added or whose source text was changed.
An example usage:
Get-XliffTranslationsDiff -originalPath "C:\MyProject\OriginalVersion.xlf" -newPath "C:\MyProject\NewVersion.xlf" -diffPath "C:\MyProject\Diff.xlf" -reportProgressPlease check the documentation of the function for more information and the available parameters.
The Set-XliffTranslations function (alias: Trans-XliffTranslations) will apply translations to the translation units in a target file with a translation base from a source file.
An example usage:
Set-XliffTranslations -sourcePath "C:\MyProject\translationSource.xlf" -targetPath "C:\MyProject\translationTarget.xlf"Please check the documentation of the function for more information and the available parameters.
The Test-BcAppXliffTranslations function (alias: Check-BcAppXliffTranslations) checks for problems in translations in the XLIFF translation files used for Microsoft Dynamics 365 Business Central apps.
It first synchronizes the translation files with the .g.xlf base file, and then checks for problems afterwards.
You can use this function in the build pipelines of your Business Central apps after the compile step, to detect problems in the translations of your Business Central apps.
An example usage:
Test-BcAppXliffTranslations -translationRulesEnableAll -AzureDevOps 'error' -printProblemsThis function invokes the Sync-XliffTranslations and Test-XliffTranslations functions for each XLIFF translation file in the app folder(s).
Note that you can use the -syncAdditionalParameters and -testAdditionalParameters parameters to pass arguments specific to each of these functions respectively, e.g.:
-syncAdditionalParameters @{ "parseFromDeveloperNote" = $true }Please check the documentation of the function for more information and the available parameters.