669
Like
Share
Report.
Previously I talked about my translation management extension. This extension does not translate automatically, but avoids these pains:
>Edit manually final xlf file.
>Translate more than once the same expression. For each use of the same in an element you must translate every element ocurrence.
So, the extension brings us these benefits:
>Translating automatically from previous xlf translation files, base app translations included, to your own extension translation.
>Detecting and group remaining translations that do not exist in previous xlf files, in a csv file ready to edit.
Shortly, the extension take to your extension translation any previous translation you have stored, group the expressions that do not exist in previous translations, and build the final xlf automatically. You have more information in this post: New translation files management extension - Dynamics 365 Business Central Community and in the extension: JAL Translations Mngt - Visual Studio Marketplace
New feature: exclusions.
This feature avoids the pain to have in the remaining translations csv file lots of useless expressions.
In the new feature we can specify a set of expressions in the steps file to exclude:
"ExclusionsFromManual": ["Report.*Spanish SILICIE declaration","Report.*EMCS Domestic Model"
So, if we find this expression in one of the lines of a translation unit it is excluded from manual translation. Notice that only is excluded from manual translation, if the expression is included in other previous translation files, the automatic translation stay working with it.
Unit translation is all the block between “trans-unit” tags:
<trans-unit id="Table 688966458 - Field 665627338 - Property 62802879" size-unit="char" translate="yes" xml:space="preserve">
<source> ,Other</source>
<target> ,Otros</target>
<note from="Developer" annotates="general" priority="2"></note>
<note from="Xliff Generator" annotates="general" priority="3">Table TIP Assistant Setup - Field Testing Options - Property OptionCaption</note>
</trans-unit>
Use case
This exclusion make sense with the domestic part of your extensions, for example a local government report declaration. If I have a report for the Spanish Tax authorities, only makes sense in Spanish language and the original must be in Spanish. So, in the translation step json file, I can add this expression to exclude all the captions of this report:
"ExclusionsFromManual": ["Report.*Spanish SILICIE declaration"
All the translation units of the report will have this note:
<note from="Xliff Generator" annotates="general" priority="3">Report Spanish SILICIE declaration
This way, the unit will be excluded from manual translation.
Also, notice that I wrote Report.*. Exclusions feature allows regular expressions.
*This post is locked for comments