In today's guide, I'm going to walk you through installing the Lionbridge connector within Episerver and then creating a translation. The Lionbridge translator is a third-party component that can be installed within Episerver to provide language translations. If you run a multi-language website, you might want to create all your content in English and then send the whole site off to Lionbridge to get it translated into French. When a translation is ready, it's a simple point and click exercise to import the content into Episerver. If you do a lot of translations, this can save you a load of time.
Installing Lionbridge with Episerver is fairly pain-free. First, you'll need to make sure that you have a Lionbridge license. This is basically two snippets of XML that you will have to get from Lionbridge. After you have a license, on the Episerver Nuget feed https://nuget.episerver.com, type in Lionbridge:
Next, log into Episerver and create a new Gadget. I usually do this on the right-hand page like so:
In the gadget options, you should see the Lionbridge translator, add that to the page. Next, we add the license information in. You do this by clicking the Lionbridge settings tab, like so:
In here you'll see two fields, source and target. In here you need to add the XML provided to you by Lionbridge. The third is the language mapper file. A dummy one might look like this:
Creating A Lionbridge Translation
The basic steps for getting your content translated using Lionbridge, is to first create a new 'Lionbridge project' within your gadget. In the project, you add all the pages that you want to be translated, you add a date, select the translation type, e.g. English -> Swedish and then submit the project to Lionbridge. After a period of time, you'll get a notification your translation is ready. To create a new project, within your Lionbridge gadget, click the + icon, like so:
The Lionbridge screen is pretty simple. One word of warning YOU NEED TO SET THE DATE IN THE FUTURE otherwise, the project will throw an error. When you are ready to submit your project, the 'Publish translations' button that you can see greyed out in the screenshot above, will be clickable. Click that and then sit back and wait.
Ensure Your Scheduled Tasks Are Set
After you submit your project, you may have to wait a really long time if you haven't enabled the two Episerver Lionbridge scheduled tasks. These tasks are responsible for sending your requests over to Lionbridge, without these your requests won't do much.
To enable these tasks, in the Episerver admin section, find the jobs called 'Translation background jobs' and 'Translation projects updater'. Ensure both are enabled and set to run on a 10-minute phase.
After Translation Has Completed
When your translated copy is ready you should get an email from Lionbridge and within the Episerver editor, the translation project will also show 100%. To Import the translations, click the burger menu icon next to your translate Lionbridge project and select “Import Translations”:
After you select this, you should then be able to see the translated page within Episerver. The quickest way to do that is to navigate to the source page and within the 'languages now available' field, you should see your language – just click on the language you had selected and the translated page should now display.
Lionbridge Episerver Connector Takeaway
I've only used Lionbridge connector with Epsierver on one project so far and it does what it says on the can. I have no idea if there are alternatives out there, but this does work.
The main downside, that I came across as a developer, is that if you want to tear-up/down your database for unit testing, then as the connector is a gadget (and Episerver has no API to interact with it) there s no way to automatically inject the Lionbridge license in code. This has to be done manually. You could create a SQL script to try and automate this, however, I NEVER RECOMMEND THAT YOU BYPASS THE EPISERVER API!!! so you've been warned :)