X

Register now for unlimited access to Sitecore resources.


Already have an account? Log in now

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
X

Request a demo

It’s easy to get started. Sign up for a personalized demo.

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
Sitecore Blog: Getting to Know Sitecore

Translation Management With Sitecore & Clay Tablet

By Adam Conn, January 18, 2011 | Rating:  | Comments (5)

These days, it's not at all unusual for a website to support multiple languages. If you're someone who works with multilingual sites, you will definitely want to check out an integration module for Sitecore that Clay Tablet Technologies recently released. Want to learn a little more about it? Read on!  And read on even if you aren't interested in translation management, because what CTT has done is a great example of the level of integration Sitecore's technology partners are able achieve.

In case you've never heard of Clay Tablet Technologies (CTT), they are a Sitecore technology partner that develops connectivity software for translation systems. Clay Tablet doesn't perform the translation. It brokers the communication between a content management system and a system or organization that provides translation services. In other words, it facilitates getting content to a translation provider and then back into a content management system.

The many benefits to this approach are beyond the scope of this article, but they can be summarized as increased efficiency and increased flexibility. Clay Tablet reports that their customers have reduced the amount of time spent managing translation (again, not the translation itself, but the process before and after) by 60%. This is accomplished by eliminating the need to develop custom integration with translation providers, and by eliminating the manual processes - like copy and paste - that are tedious, time-consuming, and inefficient parts of the translation management process.

Increased flexibility results from having a content management system communicate with Clay Tablet rather than a specific translation provider. Once the content gets to Clay Tablet, Clay Tablet's routing rules determine where the content should be directed and how the content should get there. Switching from one translation provider to another becomes a simple matter of configuration in the Clay Tablet dashboard.

The integration module is called the Clay Tablet Connector for Sitecore (CT3). It works by hooking into Sitecore's workflow engine. When an item is submitted for translation, new language versions of that item are created, and eventually populated with the content that has been translated.

Workflow is the key to the integration of Sitecore and Clay Tablet. CT3 provides a workflow action that submits an item for translation. A sample workflow is installed with the module. This workflow demonstrates how translation can be incorporated into a Sitecore workflow.

 

Workflow is one way to submit content for translation, but there are others. Bulk translation jobs can be initiated. A third option is to manually submit a single item.

Manually submitting a single item can be done from the Page Editor. This module is compatible with earlier versions of Sitecore CMS, but for this article I'm using 6.4. In the Page Editor, I have a new strip named "CT3 Translation". This strip has a "Translate To" button.

 

Clicking this button launches a dialog that allows me to specify translation instructions. The main option I have is which languages I want to translate to. I'm going to select all of the languages available.

 

Back in the Content Editor, CT3 provides a variety of ways to track the status of the translation. The "Translation Status" tab shows the status for a specific item.

Other views are available to give a more expansive view of translation progress. Filters allow a user to determine which items are in a specific step of the translation process.

After content is translated and received by Sitecore, content authors may review the translated content.  If additional changes are needed, CT3 presents the author with some options.  In the following screenshot, I right-clicked on one of the entries in the Translation Status tab.  A context menu appears that allows me to request a translation correction, among other things.

 

Behind the scenes there is a lot going on. But all of this logic is controlled through pipelines. The current version of CT3 supports a dozen pipelines that allow the various parts of the process of getting content to and from Clay Tablet to be modified and enhanced.

For example, maybe my company just changed the name of one of its products. I want to ensure the old product name hasn't slipped back in. I could add a processor to the "HandleTranslatedItemPipeline" pipeline that compares the translated content to a blacklist. If a restricted word is found, I could send an email. This is a simple example, but the point is that CT3 doesn't force your translation process to be done a certain way.

The CT3 module is a powerful tool. I hardly scratched the surface with this post. But if you like what you see, I encourage you to give Clay Tablet Technologies a call.

Tags: Content Strategy, Content Authoring

Comments

  • Awesome post Adam - thanks so much!

    One point that stands amplification is that the CT3 Connector allows a Sitecore client to use any translation provider they might wish to use. Clay Tablet can seamlessly interconnect with all the leading translation systems from firms like Lionbridge and SDL, and even machine translation solutions like Google Translate and Microsoft's Translation API - but our clients often use the translation provider they've always used and are comfortable with. They just use the Clay Tablet Sitecore Connector to make that interaction much more efficient.

    Despite this great post - there's still so much more. If you've read this and wonder if CT3 can help your firm localize content more efficiently - we'd be happy to dicuss your particular needs to see how we might help.

    RK

    - Robinson Kelly
    January 18, 2011 at 1:15 PM

  • Hi,

    We struggle with the minor formatting and text alignment edits that are usually required after translation. With segmentation by the TM the translators have no real context for the page layout. So in some cases the translation comes back fine but still needs to be touched in the CMS to make it layout better. We have tinkered with SDL SQL mounts over content database tables to show the translation in our CMS real-time, so the content can be reviewed also in the page context.

    Does the SiteCore+Clay Tablet account for this? In the workflow above, under the 'Editing Translated Version" step, are the changes/formatting persisted back in the TM (SDL)? That would be very, very cool! We're ok if it becomes necessary to tinker with formatting on occasions, but since we publish Global, Regional and Affiliate levels of content... it is a pain when Global content is (re)pushed out and our Affiliates need to (re)make layout tweaks. This also opens the door for them to change the content and alter some areas under stricter governance...

    Thanks

    - Joe Kline
    February 08, 2012 at 12:09 PM

  • Hey Joe - you highligh what we think is indeed one of the very coolest, if not immediately apparent features in the Clay Tablet Connector for Sitecore. You CAN indeed send changes made in Sitecore during ICV (In-country validation) BACK to the LSP/TMS to update the TM's. We feel this is a "must have" feature - but it took some crafty engineering. Happy to show anyone who's interested how this actually works.

    Thanks,

    RK

    - Robinson Kelly
    February 10, 2012 at 6:01 AM

  • I'd be really interested to see the sorts of files we, as an LSP, could expect from our clients when using a (Sitecore) Clay Tablet integration.

    We've just received a Sitecore XML dump from one of our clients to translate, and quite frankly, it's been difficult. With repeated text locked out by our client in their XLIFF, as well as hyperlink text found in XML attributes rather than the XML node content itself, it's meant that we were unable to see half of the sentence, or indeed reorder things depending on the language:

    <phrase path="/abc/def" key="123" itemid="{689A8DEE-FA53-4B4E-9AFA-43D93C7EC384}" fieldid="Short text" updated="20130425T102909">
    <fr-FR>I will comply with the company's </fr-FR>
    </phrase>

    <phrase path="/abc/def" key="123" itemid="{689A8DEE-FA53-4B4E-9AFA-43D93C7EC384}" fieldid="Link" updated="20130425T102909">
    <fr-FR>&lt;link text="Privacy Policy" linktype="internal" url="/privacypolicy" title="Privacy Policy" querystring="" target="" id="{D8C239FF-6BE9-4F05-AD70-A87AD4BBEBA6}" /&gt;</fr-FR>
    </phrase>

    Is it possible to see the sort of files that we would be working on if this were a Clay Tablet implementation, or does this depend on the way the site has been set up? We still haven't found a way of reordering content when we're working this way, so if Clay Tablet would help solve this, it would be good to see what we could expect.

    Thanks,
    Sam

    - Sam Whatley
    October 11, 2013 at 2:32 AM

  • Hi Sam - we'd be happy to send you over a sample XML file. I think you'll find it pretty clean and easy to work with. It'll probably transform this project from painful to speedy.

    Our XML format will elegantly get parsed by any CAT tool and works nicely will all TM's and TMS's. We estimate about a billion words of content flowed between Sitecore systems and translation firms last year through Clay Tablet integrations - so it's a format that's working well for LSP's and clients worldwide.

    Just send a note to info (at) clay-tablet.com and reference this thread - we'll get you a sample file right away.

    Thanks,

    RK

    - Robinson Kelly
    October 11, 2013 at 9:02 AM

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
Cookies help us improve your website experience. By using our website, you agree to our use of cookies. OK Learn more