Cookies Settings

10 Reasons To Use iLangl Sitecore Connector

1. In-context Translation

Struggling with the painful layout and inevitable text fine-tuning after translation? There is a simple reason behind it - CAT tools have their own segmentation logic which does not reflect the real page layout. In some cases delivered translation is fine overall but still requires final polishing and adjustment of the layout in the CMS. iLangl Cloud offers in-context review and editing allowing the linguists to perform translation at iLangL proxy page. Proxy page looks exactly like the source page which expedites the whole process, boosts localization consistency and helps to tackle any layout issues before the translated text is physically imported back to the website.

2. Translation Ordering

Sitecore page layout contains a lot of Sitecore items. It can be quite of a challenge if you have to select them manually to get the entire page translated. With iLangL connector for Sitecore you can automatically export all the related Sitecore items within the main page and save yourself time for more important tasks.

3. Translatable Fields And Sensitive Data

Sitecore website has a lot of different templates and fields. Only some of them are fully translatable. Others may require just partial translation since they’re a mix of system data and translatable text. This makes translation very complicated as linguists aren’t always tech savvy enough to single out the actual text for translation. In order to receive good translation that won’t break the layout of a web page, you’ll have to provide detailed instructions, which can be pretty time-consuming.

With Sitecore connector you can cross it off your to-do list. Sitecore connector processes system data on the fly, hides or excludes translation fields that don’t require translation, optimizes content for translation tool and shows only clean localization text to the linguists. Linguists will never see any system data or corresponding markup (e.g. tags). Elimination of system tags will decrease translation efforts/costs and ensure that data structure remains intact. This also helps to ensure proper text segmentation which means generation of clean Translation Memories and more efficient translation reuse. Sitecore you can automatically export all the related Sitecore items within the main page and save yourself time for more important tasks.

4. Translation Context

In the majority of cases quality of the translation depends a lot on the reference materials and/or detailed instructions on how to handle particular text field. This information is usually added to the reference files and sent along with text for translation. The more instructions you have, the easier it is for a linguist to miss them. With iLangL this information can be assigned directly to a text field to ensure that translator notices it during translation. If you have special instructions for a particular page, you’ll be able to attach them to it with our permanent comments option. In addition, they can also be assigned to certain source and/or target languages. Each time this page is ordered, permanent comment with your instructions will appear in front of a linguist. All in all, instructions are much more efficient when embedded directly into the translation process, on the contrary to regular reference files.

5. Translation Synchronization

Thanks to flexibility of Sitecore connector, you can import full or partial translation of a Sitecore item. Different set of fields can be translated separately and then successfully merged into the final language version at your convenience. For example, you can assign one team to localize SEO fields and another one to translate the localizable fields. If target page doesn’t exist yet, Sitecore connector will create a new one based on the source version. Otherwise, connector will clone a new language version from the previous one. Non-localizable data can also be synchronized from master to the target version. It will be exported along with master content but hidden in the translation tool. Once translation is completed and imported, hidden data will be transferred to the target version together with it.

6. Length Validation

For some Sitecore fields character limit may be critical. Even advanced responsive html layout can’t be stretched enough to fit the translation into some languages with notoriously long words. To keep the layout neat and consistent, it’s crucial to apply length validation to the translation of headers, menu titles, etc... Length validation can be measured in max amount of characters or percentage. You may be surprised, but most of the translation tools can only provide length validation for a single segment. If validated property consists of two or more segments, there is no easy way for them to validate the field length. With iLangL localization tool length validation can be applied to fields with multiple segments, including all visible and invisible parts of field.

7. Continuous Localization

Continuous localization is a key factor in reaching your world audience and giving timely response to the international market changes. This strategy might be very resource consuming or even impossible due to loads of dynamic content requiring changes into numerous target languages. The only way to succeed is full automation. With iLangL connector for Sitecore you can identify the scope of items to include in continuous localization workflow, while our system will automate the entire process. Timely translation is the only manual step that requires involvement of a translation agency or you.

8. Marketing Review

As a localization manager you want to be sure that each piece of delivered translation is immaculate. You add your marketing team as an extra QA layer having them review the translation and make any necessary onsite changes to target your local audience. The process seems to be working like a charm but for whatever reason a new round of translation doesn’t include previous updates of the marketing reviewers. Sounds familiar? We bet it does. In order for these changes to be saved, they must be applied to translation memory directly, otherwise they won’t fetch up. In this case you have two options. First one is to include your marketing reviewers in the translation process and have them work in the translation tool directly. Two usual drawbacks are absence of context and necessity for CAT tool training. Second option is to synchronise your onsite changes with the TM. iLangL Cloud makes both options easy for you. We offer in-context and alignment modes to ensure that all your onsite changes are fetched up by the translation memory. New rounds of translation will include your previous updates and no work will be lost.

9. In-house Localization or Outsourcing

In-house localization or outsourcing? The choice is all yours. Having your in-house team could be more efficient localization wise but it is not always true for translation. Covering all the translation needs, which are constantly changing in terms of volumes and target languages, can be pretty challenging. Judging on the above, a mix of both would be a perfect solution. With different teams involved, how can you make sure that everything is running smoothly and everybody is on the same page? iLangL Cloud will be happy to take the burden off your shoulders. We offer a combo solution that will perfectly meet the needs of both in-house and outsourced teams giving your in-house translators intuitive platform to work with or seamlessly linking your website with the translation agency’s CAT tools. Flexibility of our tool will help you resolve any localization challenge in a blink of an eye.

10. Migration

Looking to migrate your multilingual website with all the languages to Sitecore or update the Sitecore version with full redesign? Well, in this case you should multiply the amount of efforts by the number of target languages you support. But not with iLangL Sitecore connector! We can help you align content between master and all your target languages from old website as well as generate translation memories for you. All you have to do is migrate the data for master language and our Sitecore connector will create target language versions in your new Sitecore instance for you. Generated translation memories can be reused in further translations which will save your time and money.