![]() In order to translate other apps, you must use the of the original property, not the one of an extension object as that might have been modified. Use the of the label where it was defined Otherwise, translations are only used to translate labels in the same app.įor apps where translations are meant to translate the current app, the generated xliff file will have the correct value of the app name. When translating other extensions, make sure that the attribute original in the element in the xliff file is not set to the name of the current app. When your extension is then built and published, change the language of Dynamics 365 Business Central to view the UI in the translated language. Create a directory named Translations, in the root of the extension, and place the translated xliff file there. Advanced features and Xliff translations available. When the dependencies are set, you can add xliff files in your current project that translates the object captions of the referenced extension. Open Xliff Editor Xliff File Management Free Xliff Editor for your multilingual content. To translate other extensions, for example, when adding translations to the Base Application, you must reference the project to be translated using the dependencies section in the app.json file. When the extension is built and published, you can change the language of Dynamics 365 Business Central to view the UI in the translated language. There is no enforced naming on the file, but it's a good practice to name it. If you translate your extension to multiple languages, you must have a translation file per language. This is illustrated in the example below. The attribute corresponds to the object ID in the extension. The target-language must be specified in the format "-", for example "da-DK", "es-ES", or "de-DE". For the translation, you'll now have to add the target-language and a element per label. xlf file, you can see a element for each label. LabelName = 'Label Text', Comment='Foo', MaxLength=999, Locked=true Īnd the following is the syntax for Label data types: varĪ : Label 'Label Text', Comment='Foo', MaxLength=999, Locked=true Use the same syntax for report labels: labels In this video you'll learn how XLIFF files are organized and how to manage them with a convenient online editor.Timecodes:00:00 Intro: what. For more information, see Label Data Type. The comment, locked, and maxLength attributes are optional and the order is not enforced. The label syntax is shown in the example below for the Caption property: Caption = 'Developer translation for %1', Comment = '%1 is extension name', locked = false, MaxLength=999 The default behavior is that these elements aren't generated. Furthermore, the XLIFF tool offers tons of benefits one of them is that it improves the lives of. It's an XML-based format, designed in 2002, to help systematize the way localizable data is exchanged between different tools during a process known as localization. The syntax is as follows: "features": ĪPPLIES TO: Business Central 2020 release wave 2 and laterīy setting the GenerateLockedTranslations flag in the app.json file, you specify that you want to generate elements for locked labels in the XLIFF file. XLIFF is an acronym that stands for XML Localization Interchange File Format. For the table fields, the OptionCaption is used. ![]() If the object already has a Caption property set, that value will be used. The editor automatically connects to appropriate translation memories, term bases, and/or machine translations when logged in.įor supported version, see the download site.Make sure to rename the translation file before building the extension next time, as it'll be overwritten.īy setting the GenerateCaptions flag in the app.json file, you specify that you want to generate captions based on the object name for pages, tables, reports, XMLports, request pages, and table fields. MXLIFF files are the native file format for the editor and can be downloaded from translation projects. ![]() To place the panes back in their original positions, select Restore default layout from the Tools menu. Panes in the editor can be moved outside the main window to give more visibility. While translating offline is supported, full functionality is provided when connected. Minimum requirements are a processor (CPU) not more than 8 years old, 2GB of RAM and at least 256 MB of disk storage. The CAT desktop editor is a lightweight CAT tool that can be installed on Windows, Macintosh, and Linux operating systems. An updated OS and editor version will be required.ĭownload the latest version to use with an updated OS. This is due to the deprecation of Legacy APIs. As of January 2021, all outdated OS support ends and their corresponding desktop editor versions will no longer function.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |