This repo contains samples that demonstrate the localization workflow for users of the Multilingual Application Toolkit Visual Studio extension and editor. You can also use GitHub Issues to submit feedback, report bugs, or ask questions.
MIT License
25
stars
4
forks
source link
Multilingual App Toolkit compatibility with XliffTasks #29
we are currently migrating our Xamarin Apps to MAUI and facing some issues regarding the localizations.
With Xamarin we used the Multilingual App Toolkit along with the Editor, to provide and gather translation for different languages through the xlf files. The build process with MAT will not work anymore as our build pipeline is also changing, and MAT is not working on non-windows build nodes. Therefore we tried to replace the build generation steps with the "XliffTasks" as we found no other options currently. And this is working in general.
But as we would like to stick to the MAT editor for the plain translation process, we discovered some problems regarding the exchange of xlf files.
The MAT always places <trans-unit> in a <group> element in the <body> element. The Editor rewrites elements that are not included in a group, to the last group contained in the file, on save. Also the Editor can't open xlf files which don't have a <group> element included at all.
Other Tools like the "XliffTasks" place the <trans-unit> plain to the <body>, which is complient to the xlf definition.
The editor should be capable of opening files without a <group>element and keep the intial structure.
Thanks in advance for feedback.
PS: Im also happy to here about working alternatives, but haven't found any yet.
Hi,
we are currently migrating our Xamarin Apps to MAUI and facing some issues regarding the localizations. With Xamarin we used the Multilingual App Toolkit along with the Editor, to provide and gather translation for different languages through the xlf files. The build process with MAT will not work anymore as our build pipeline is also changing, and MAT is not working on non-windows build nodes. Therefore we tried to replace the build generation steps with the "XliffTasks" as we found no other options currently. And this is working in general. But as we would like to stick to the MAT editor for the plain translation process, we discovered some problems regarding the exchange of xlf files.
<trans-unit>in a<group>element in the<body>element. The Editor rewrites elements that are not included in a group, to the last group contained in the file, on save. Also the Editor can't open xlf files which don't have a<group>element included at all. Other Tools like the "XliffTasks" place the<trans-unit>plain to the<body>, which is complient to the xlf definition.<group>element and keep the intial structure.Thanks in advance for feedback.
PS: Im also happy to here about working alternatives, but haven't found any yet.