Translation Enforcement

[dksander]

Hi,

Translation is a headache for much of the PTE development. Currently, we make do with some tooling in VS Code — we're using NAB (nabsolutions.nab-al-tools) to update, sync, and add new translations.

However, it's not very efficient and is prone to errors when developers forget to add translations (in the local language) and push changes to GitHub.

Would it be possible to add a translation check in AL-GO that could be enforced during a pull request build? For example, for every translation in the g.xlf file, there should be a matching translation in the other translation files? or som regex expression to check for empty or dummy filled text?

Br
Lars

[mazhelez]

Hey @dksander

We don't have any planned work around translations at the moment. But can you not add this check as a custom (not AL-Go-related) workflow?

[dksander]

Hi @mazhelez
That will properly be my next move :-)

Thanks for your answer 👍

[dksander]

If you have a good idea of where it would make the most sense to place it in the workflow, I’d really appreciate a tip or two 😄

[dksander]

With the new AL-Go release I have found my answer 👍
Thanks for custom template :-)

[pri-kise]

@dksander could you maybe help how to get this to work?
I was expermenting a little bit with xliff sync powershell module: https://github.com/rvanbekkum/ps-xliff-sync
I don't know how to integrate this step into al-go:

This is my current draft:

name: 'Check Translations'

on:
  workflow_run:
    workflows: ['_Build AL-Go project']
    types: [completed]

jobs:
  xliff-sync-check:
    runs-on: windows-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Install XliffSync module
        shell: pwsh
        run: |
          Install-Module -Name XliffSync -Scope CurrentUser -Force

      - name: Run XLIFF translation test
        shell: pwsh
        run: |
          Import-Module XliffSync
          # Adjust buildProjectFolder as needed, here we use the root
          $buildProjectFolder = "$(Resolve-Path .)"
          # Optionally, set $appFolders or leave empty to process all subfolders
          $params = @{
            buildProjectFolder = $buildProjectFolder
            appFolders = @("PTE-BaseApp") # Uncomment and edit if you want to restrict folders
            translationRules = @("ConsecutiveSpacesConsistent", "OptionMemberCount", "OptionLeadingSpaces", "Placeholders")
            AzureDevOps = "error"
            printProblems = $true
            printUnitsWithErrors = $true
          }
          Test-BcAppXliffTranslations @params

[fvet]

@pri-kise @dksander Any final solution you could share?

We've a fully working custom translation step running with Azure Devops (ALOPS) and Xliff sync from Rob, but are looking to migrate to AL-Go. Would be great if someone could share some 'translation check/xliff sync' community enhancements (using either Xliff sync or NAB AL Tools)

[freddydk]

I decided to go with NAB AL Tools for CCMS here: https://github.com/directions4partners/CCMS and will document that.
If this works well, I might suggest an implementation for AL-Go with a simple setting for enabling that (if Microsoft will take it)