Skip to content

Latest commit

 

History

History
113 lines (71 loc) · 8.45 KB

CHANGELOG.md

File metadata and controls

113 lines (71 loc) · 8.45 KB

Changelog

[1.10.0] 10-01-2025

  • 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)

[1.9.0] 19-05-2023

  • 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)

[1.8.0] 28-01-2023

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

Thank You (for 1.8.0)

[1.7.0] 31-05-2022

  • 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)

[1.6.0] 09-02-2022

  • 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)

[1.5.0] 07-12-2021

  • 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)

[1.4.0] 29-11-2021

  • 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)

[1.3.0] 29-09-2021

  • 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.

Thank You (for 1.3.0)

[1.2.0] 20-05-2021

  • New function Trans-XliffTranslations by Tomáš Žabčík
  • Include units that already have needs-adaptation state in needs work count (GitHub issue #8)

Thank You (for 1.2.0)

[1.1.0] 06-03-2021

  • 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 (for 1.1.0)

[1.0.0] 02-09-2020

  • Initial version