1.10.0

• Changed severity of the "There are no target translation files" message in Test-BcAppXliffTranslations to be based on the -AzureDevOps parameter.

Thank You (for 1.10.0)

• Christian Hovenbitzer for your Pull Request #42 "Change severity of "There are no target translation files" message in Test-BcAppXliffTranslations to be based on -AzureDevOps parameter"

1.9.0

• Added -useSelfClosingTags parameter to the Sync-XliffTranslations command (GitHub issue #38)
• Added -processAppFoldersSortedByDependencies parameter to the Test-BcAppXliffTranslations command.

Thank You (for 1.9.0)

• Frédéric Vercaemst for filing Issue #38 Different Developer closing note when syncing xliffs via PS vs VS Code

1.8.0

• Added -parseFromDeveloperNoteTrimCharacters parameter to the Sync-XliffTranslations command (GitHub issue #39)

Thank You (for 1.8.0)

• Frédéric Vercaemst for filing Issue #39 "parseFromDeveloperNoteTrimCharacters" parameter missing in Sync-XliffTranslations / Test-BcAppXliffTranslations

1.7.0

• Fix for "attribute target-language cannot be found" bug by Timotheus Pokorra (GitHub issue #30)
• Fix for SetXliffSyncNote method which inserted the source-node another time when whitespace should not be preserved.

Thank You (for 1.7.0)

• Timotheus Pokorra for your Pull Request #31 "Set attribute target-language even if it does not exist yet"

1.6.0

• Fixed missing Write-Host "##[endgroup]" in Test-BcAppXliffTranslations
• Support for multi-character -parseFromDeveloperNoteSeparator by David FeldHoff
• Changed default value for parameter -FormatTranslationUnit in Test-BcAppXliffTranslations to show both the Xliff Generator note and XLIFF Sync note for detected problems.

Thank You (for 1.6.0)

• David FeldHoff for your Pull Request #29 "Fix splitting if the separator consists of more than one character"

1.5.0

• Added -FormatTranslationUnit parameter to Test-XliffTranslations function. (GitHub issue #21)
• Added -FormatTranslationUnit parameter to Sync-XliffTranslations and Test-BcAppXliffTranslations functions. The latter has a default value that will print the AL object/field/action/control concerned. (GitHub issue #21)
• Write parameters when -Verbose switch is used with Sync-XliffTranslations or Test-XliffTranslations functions.
• Use List[] instead of array(s) in the Test-XliffTranslations function. (GitHub issue #18)
• Use List[] instead of array(s) in the Sync-XliffTranslations function. (GitHub issue #18)
• Added parameters -syncAdditionalParameters and -testAdditionalParameters to Test-BcAppXliffTranslations function. (GitHub issue #22)
• Fixed detected source text changes not being included in the detected issues.

Thank You (for 1.5.0)

• Jan Hoek for your Pull Request #26 "Added -FormatTranslationUnit parameter" which adds the -FormatTranslationUnit parameter to Test-XliffTranslations.
• Jan Hoek for your Pull Request #27 "Use List[] instead of arrays" which changes Test-XliffTranslations to use lists instead of arrays.
• Jan Hoek for your thoughts on aligning the parameters of Test-BcAppXliffTranslations (via DM).
• Sergio Castelluccio for reporting Test-BcAppXliffTranslations not failing builds in Azure DevOps if errors are detected in a specific scenario (via DM).

1.4.0

• Changes in usage of Resolve-Path for scenarios where the -targetLanguage parameter of Sync-XliffTranslations is used.
• Added formatting settings (.vscode/settings.json) for PowerShell formatting (GitHub issue #23)

Thank You (for 1.4.0)

• David FeldHoff for your Pull Request #19 "Resolve-Path gets an error if the file does not exist yet."
• Jan Hoek for your Pull Request #24 "Chose formatting settings that matched current formatting as much as possible"

1.3.0

• Renamed functions to adhere to approved verbs and added aliases to still support the old function names (GitHub issue #10)
• New function Test-BcAppXliffTranslations, to be used for checking translations in a build pipeline for Microsoft Dynamics 365 Business Central apps. This function uses the Sync-XliffTranslations and Test-XliffTranslations functions to check for problems in all translation files of the BC app workspace folder.
• Add Resolve-Path for loading XLIFF files from or saving them to a filepath. (GitHub issue #6)
• Abort if file-load failed. (GitHub issue #5)
• Updated README with Installation instruction.

1.1.0: Merge pull request #4 from rvanbekkum/develop

Changelog

• Fix for findByXliffGeneratorNoteAndSourceText throwing error on variable not being found.
• Fix for incorrect assumption of xml:space="preserve" which would lead to errors in an attempt to insert whitespace/nodes.
• Fix/Improvement: Find by source (and developer note) would take the first unit with the same source text even if that unit did not have a translation, now it takes the first unit with the same source text with a translation to reuse translations.
• Command Check-XliffTranslations now returns the units that contain problems as an array. Useful if you want to do something with the outputs, e.g., extract/show more information or completely fail your build pipeline if any problems are found.

Thank You

• Tomáš Žabčík for your Pull Request #3 "fixing variable name"
• Simone Colombo for filing Issue #2 "Error syncing Angular translations"