- TRANSLATION WORKSPACE XLIFF EDITOR FREE DOWNLOAD HOW TO
- TRANSLATION WORKSPACE XLIFF EDITOR FREE DOWNLOAD FULL
- TRANSLATION WORKSPACE XLIFF EDITOR FREE DOWNLOAD CODE
To see the code in action, press F5 to build and deploy the VS Code extension to a VS Code development host environment. The getTranslationServiceApiKey() tries to retrieve the key from the settings and if it does not find it, it prompts the user for it: In order to call the Translator Text service, the API key is needed. Upon activation, the extension registers a command binding to call the translate() method on the XLIFFTranslator class where all the magic happens. This VS Code extension is written in Typescript, so get ready, I am going to walk you through it.
TRANSLATION WORKSPACE XLIFF EDITOR FREE DOWNLOAD FULL
The full source code for the XLIFF extension is available on GitHub here, so go ahead and download it. If you are not familiar with VS Code extension development, there are lots of resources and samples online to get you started. Actually, it does not even have to be an AL extension and you can use this tool to translate any XLIFF file in any VS Code project. This extension, once installed in your VS Code editor, will translate any XLIFF file in your workspace.
TRANSLATION WORKSPACE XLIFF EDITOR FREE DOWNLOAD HOW TO
Just to avoid the confusion, what I am about to talk about, is how to write a VS Code extension, not an AL extension. Making a (VS Code) extension…to translate your (AL) extension So, let’s put this all together in a nice little VS Code extension, that can automate all that for you. Now that the service is created, you can translate strings by issuing REST API calls as documented here. There you can see the API keys that you will need to call the service:Ĭopy one of the key values, we will need it for later. After a while, the service gets deployed, then click on it and go to ‘Keys’.
In the Azure portal, click on ‘Create a resource’ and search for ‘Translator Text’ and then click create.įill out the various information required and click ‘Create’ again. In this blog post, we will be using this service to translate the XLIFF files, so first thing is to deploy a translation service in you Azure subscription. This could be the subject of an entire blog series, so I will not digress here but if you want to learn more you can click on this link.
The Translator Text API, is an Azure cognitive service that leverages advanced neural network technology to deliver high-quality AI powered translations. Quite straight forward indeed.Īt this point, you could proceed by manually entering the translated strings in the files, but let’s take this to the next level and use Azure cognitive translation services. At the top of the file, a ‘file’ tag has attributes to specify the source and target language. Strings to be translated are listed with a ‘source’ XML tag and the corresponding translation is marked with a ‘target’ tag. The format itself is rather self-explanatory. Many tools used by translators understand this format and XLIFF files usually have the. It is an XML-based format that is widely used in the translation world. XLIFF stands for XML Localization Interchange File Format. In this blog post, I will show how to write a Visual Studio Code extension, which can automatically translate your Business Central Extension using Azure translation services. Business Central AL extensions already allow you to package your translation together with your extension. If you seek international growth for your solution and look for reaching markets across the world, you will be faced with the need to translate your software.
0 kommentar(er)
