If there are only one translation file, the translation file will be opened with the translation selected. Place the cursor on a AL code line that should be translated and execute this command to find any translations of the selected line. Use this command to find all places where you've got multiple targets, caused by the matching finding multiple sources with different translations NAB: Find translated texts of current line Uses the Find in Files feature to search for translation units in need of review or translation. The -tags are not used when this setting is activated. Which is any state except final, signed-off, translated. If the setting NAB.UseExternalTranslationTool is set to true it searches for any target with a state that is considered not completed. If the tag is selected, review the suggested translation (added by source matching) and update if needed, then you remove the tag.If the tag is selected, review the translation and update if needed, then you remove the tag.If the tag is selected, replace it with the translated text.NAB: Find next untranslated text (Ctrl+Alt+U)įinds the next occurrence of the tags or and selects the tag. Only xlf files with the same target language as the selected xlf file will be modified.Works similar as NAB: Refresh XLF files from g.xlf, but you will first need to select another xlf file to use for matching (read more about matching in the NAB.MatchTranslation setting documentation). NAB: Match translations from external XLF file Please create an issue if you have an opinion of how the target states should be used or if you wish to see more functionality that improves the workflow when working with translation tools. The note is then removed when the target state attribute is set to "translated". If the setting NAB.UseExternalTranslationTool is enabled this note is added as well.If this note exists when the NAB: Refresh XLF files from g.xlf is executed again and the translation tag is removed, this note will be removed. The note can be identified by the "from" attribute that is set to "NAB AL Tools". If a translation tag (, and ) is added, there is also an added note that explains why this is done.Read more in the NAB.MatchTranslation setting. If the setting NAB.MatchTranslation is enabled and a not translated text is found, it tries to match the source texts to find if this text has been translated before.New translations with other source language than g.xlf is replaced with or.New translations with the same source language as g.xlf gets copied to target, but prefixed with or.Modified translations gets prefixed with or.Translations marked as translate=no gets removed.The xlf files gets the same ordering as g.xlf.If the setting NAB.UseExternalTranslationTool = true the state attribute of is modified instead. The default behavior is to insert the tags mentioned below. Iterates the g.xlf file and updates all language xlf files. Execute "NAB: Find next untranslated text" from the Command Palette and handle the untranslated/modified translation until you've handled them all.Execute "NAB: Refresh XLF files from g.xlf" from the Command Palette.Build your app, so that the g.xlf file gets updated.The workflow for working with these XLIFF tools are NAB: Create PermissionSet for all objects.Work with Dynamics 365 Translation Service (DTS).NAB: Create translation XLF for new language.NAB: Match Translations From Base Application. NAB: Download Base App Translation files.NAB: Find source of current Translation Unit ("F12" in xlf files).NAB: Find translated texts of current line.NAB: Find multiple targets in XLF files.NAB: Find next untranslated text (Ctrl+Alt+U).NAB: Match translations from external XLF file.NAB AL Tools supports the pre-release functionality in VSCode v1.63 and later (read more in the release notes for VSCode). This extensions is a tool that helps with AL development.
0 Comments
Leave a Reply. |