Xliff Compare & Finding Missing Translations

When working with Extensions I would not recommend working with Xliff files unless you design for AppSource. Otherwise CaptionML will work fine for Per-Tenant projects.

Unfortunately for me, I am working right now on submitting an AppSource project and I need to evaluate if my translations are complete.

As I explained at my presentation in Antwerp at NAVTechDays we continue to code in C/Side and then convert to Extensions and submit to AppSource. Therefor I don’t have the nightmare problem of maintaining Xliff files, I do however need to figure out how complete I am.

So in C/Side I am using CaptionML and when I convert to Extensions I simply use this flag in our converter which I have and you don’t. (Nananana…)

ForNAV Converter

We’ll change that soon. But meanwhile let’s look at the output.

Translation

You don’t need to be a rocket scientist to see that for example Czech and Swedish probably have missing captions. But which ones?

Michael has created a simple C# console application that will generate a file you can open in Excel to analyse this.

Result

You can download the tool from our GitHub. Don’t hesitate to make improvements.

https://github.com/ReportsForNAV/xliffCompare

Stay tuned for more info and learnings with Extensions, AppSource and converting code…

Comment List
Related
Recommended