Some languages are not matched to Base app translations

[JSebastianN]

I really like how the tool makes suggestions for known field names.

However, I cannot get it to do Danish or German.

Here is a comparison between French, Italian, Danish and German

fr-FR
Location Code - FOUND!
Remaining Quantity - FOUND!
Qty. Rounding Precision - FOUND!

it-IT
Location Code - FOUND!
Remaining Quantity - FOUND!
Qty. Rounding Precision - Not found

da-DK
Location Code - Not found
Remaining Quantity - Not found
Qty. Rounding Precision - Not found

de
Location Code - Not found
Remaining Quantity - Not found
Qty. Rounding Precision - Not found

Troubleshooting Danish:

A)
I checked the
"C:\Users\JohannesSebastianNie.vscode\extensions\nabsolutions.nab-al-tools-1.28.0\dist\da-dk.json"
"Location Code" and "Remaining Quantity" seems to be included here, while "Qty. Rounding Precision" is not.

B)
I tried feeding NAB with Danish base translations from the file "Base Application.da-DK-16.5.xlf" in /Translations -folder. using this setting
"NAB.TranslationSuggestionPaths": ["/Translations/"]
But that did not help

C )
I tried setting "NAB.MatchBaseAppTranslation": true, but it did not help

[JSebastianN]

okay, target-language="de" must be target-language="de-DE" even is "de" is an ISO code for German.
German it now triggering.

[jwikman]

Hi @JSebastianN,

This feature is implemented in a quite simple, yet effective, way:
We have generated dictionary files (the json file you already found) from the xlf files found in the Base Application. The files are published in an Azure Storage with the name coming from the target-language in the xlf file. These json dictionary files are then downloaded when you are trying to match the translations, based on the target-language in your app.

Because of that, we are using the same language codes (and file names) as they do in Base Application, which is the reason you won't get a hit for "de", but for "de-DE".
The xlf files used are:

Base Application.cs-cz.xlf
Base Application.da-DK.xlf
Base Application.de-AT.xlf
Base Application.de-CH.xlf
Base Application.de-DE.xlf
Base Application.en-AU.xlf
Base Application.en-CA.xlf
Base Application.en-GB.xlf
Base Application.en-NZ.xlf
Base Application.en-US.xlf
Base Application.es-ES.xlf
Base Application.es-MX.xlf
Base Application.fi-FI.xlf
Base Application.fr-BE.xlf
Base Application.fr-CA.xlf
Base Application.fr-CH.xlf
Base Application.fr-FR.xlf
Base Application.is-IS.xlf
Base Application.it-CH.xlf
Base Application.it-IT.xlf
Base Application.nb-NO.xlf
Base Application.nl-BE.xlf
Base Application.nl-NL.xlf
Base Application.ru-RU.xlf
Base Application.sv-SE.xlf

Which then results in the following json dictionary files:

Name             
----             
cs-cz.json       
da-dk.json       
de-at.json       
de-ch.json       
de-de.json       
en-au.json       
en-ca.json       
en-gb.json       
en-nz.json       
en-us.json       
es-es_tradnl.json
es-mx.json       
fi-fi.json       
fr-be.json       
fr-ca.json       
fr-ch.json       
fr-fr.json       
is-is.json       
it-ch.json       
it-it.json       
nb-no.json       
nl-be.json       
nl-nl.json       
ru-ru.json       
sv-se.json       

Does it make sense?

I do not have a good explanation about what is happening with the danish dictionary file. The file did just not seem to be complete. The published files was created from v18.0.23013.23795. I have now recreated them from v21.2.49946.49990, and now it seems as the danish translation works better. Please try it yourself and confirm :)

[JSebastianN]

da-DK is can now find "Location Code" so I think it is good 👍
Thanks and a happy new year to you.