In the previous post you saw how to create a Microsoft Translator widget, customize it and put it on your web site. As part of this process you saw how to enable your readership as a community to help enhance the translations on your page. In this article, you’ll go step-by-step through the workflow of using the collaborative translations, including how to invite new members, and how to assign different members to different roles and responsibilities.
To get started, take a look at the page, and use the widget to translate the page into another language. In this example, I’ll use French.
If you do not see the ‘gear’ icon on the top right of the screen, you’ll need to sign in to the live id that you used to create the widget. To do this, hover over any text, and select ‘Improve Translation’.
You’ll then see the dialog that allows you to edit the text. Click ‘Sign In’ here to sign in with your Live ID.
Once you’ve signed in, you’ll see some differences in the dialog, including the submit button changing, so that as an administrator of the site, your changes go through right away. You’ll see these a little later.
You can go to the translation Dashboard either by selecting ‘Dashboard’ at the bottom left of the translation dialog, or by clicking the gear icon in the top toolbar.
When you select the Dashboard, you’ll be given a dialog with two tabs, one to Manage Translators and one to Manage Translations. The Manage Translators is selected by default, and it allows you to invite people to your site and operate on the site in different roles. Here you can see I am inviting a user at ‘email@example.com’ to join me on the site, and help me to improve the translations. I’ve set her to be a translator.
When I click ‘Send Invitation’, she’ll be added to the list on the right hand side and her role will be visible as ‘Translator’.
She will receive an email with a link back to the site, and instructions on how she can assist in improving the translations on the site.
When she visits the site, and hovers over a piece of text, she can select the ‘Improve Translation’ link, and sign in just as before. What she’ll see depends on the text highlighted, and the history of edits there, but for this example, she can see two translations of the highlighted text:
The bottom translation has the Microsoft Translator logo beside it, indicating that it is the default translation received back from the Microsoft Translator API. The top one has the administrators logo, and it is the one that you saw a little earlier in this article.
When she hovers over any of these translations, she’s given the option to Edit the translation, Select the current translation as the best option or report a translation as incorrect or offensive.
If she selects ‘Edit’ she can type something different in, proposing it as a better translation. So, for example, the English word ‘Azure’ was used in the original post. This was referring to the ‘Windows Azure’ technology, but the translation just translated the color azure to d’azur.
So she can retype the translation to ‘avec Windows Azure’ (with Windows Azure) instead of the confusing half-english ‘d’azur-powered’, and submit this as an alternative, improved translation.
The translation is accepted right away, and the page is updated with the new value:
However, this is customized only for her experience. Anybody else signing into the page will still see the original translation. If they hover over the text, they’ll see three options: the original, the one submitted by the administrator earlier, and the new one submitted by the invited translator:
The green one is presently the preferred translation, because it is the one the administrator submitted earlier in this article. To make the one from the invited guest become the default, the administrator will sign in as before, go to the dashboard and select the ‘Manage Translations’ tab. The list of community proposed translations will appear, and from there, the administrator can see what the options for translation are:
If the administrator decides that the second one (with ‘avec Windows Azure’) is the better translation, he can hover over it and select ‘Approve’. This translation now becomes the default, so all visitors to the page will see it.
In conclusion, you can see that the tools available for improving the translations on your site through collaboration with speakers of the target language, make the process smooth and efficient, without needing code to be written, and without needing to give others access to your web site. The widget provides all of the needed functionality.