original attribute in translated XLIFF file is changed to ....g.xlf

[ernestasjuska]

Hello,

In translated XLIFF files

...
  <file datatype="xml" source-language="en-US" target-language="lt-LT" original="My App">
...

is changed to

...
  <file datatype="xml" source-language="en-US" target-language="lt-LT" original="My App.g.xlf">
...

Is there any reason for changing this? Personally, I would rather have the original match the original in *.g.xlf file.

Thanks.

[jwikman]

Hi @ernestasjuska

Yes, the reason is that this is what is expected by the "Dynamics Translation Service" (read more about that service on https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/translation-service-overview). If having the app name (same as in g.xlf) the translation memory just won't work. I do not remember if we found out this by reading it somewhere, or if we found out by trial-and-error...

I assume that this is the thinking about this:

• The AL code is considered the "original" when creating the g.xlf file
• When creating a translated xlf, it is done from the g.xlf file, and hence the g.xlf file is considered the "original"

Make sense?

[ernestasjuska]

I see. Thanks.

[TysvdHeuvel]

Hi @jwikman,

I bumped in to this discussion here because I was also looking for answers. But, for us / our translation tools it works the other way around. It expects the original to be the same in both the source and target documents.
Is this perhaps something you could turn into a setting?

Would be great if that would be possible.

Cheers, Tys

[jwikman]

Hi @TysvdHeuvel,

I think we could add a setting for this behavior. I'll reopen this issue.

It could take some time before I'll have the time to look into it, so don't expect it to show up any day soon. :)

[TysvdHeuvel]

@jwikman BTW, I looked into that Dynamics Translation Service (DTS), but that is a weird thing..
It sounds promising.. but then you read:

There is no Business Central support.. This is just for old AX, F&O, NAV.
And if you logon to https://lcs.dynamics.com/v2 , that portal where you are supposed to work with this DTS.. then it feels like you are back in 1992..

I guess it is quite safe to say, that this DTS is of no use for BC developer.

[jwikman]

Yeah, that site is not a nice one...

But it works just fine with Business Central xlf files.

And there is even an VSCode extension for it as well, and it is created for BC Developers from what I read at https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/lifecycle-services/dts-vscode-doc

[jwikman]

And you missed a detail in your screenshot @TysvdHeuvel 😎

But I agree that there is quite a lot to wish for with both site usability and the documentations...

[TysvdHeuvel]

After reading your remarks here, I went back to the site..
..because yes it turns out that BC was listed and I did not see it...
But, disappointment was just around the corner.. When you select NAV, next you have to fill in a mandatory field ... which has no options.

[jwikman]

@TysvdHeuvel that is strange.
I have the option "NAV default" in that field...

And when creating a new "Translation Request", I have the option to select BC: