Page Comparison

To deliver a unique experience to your website users and visitors, web agencies often customize their templates and scripts for your CMS (Content Management System). What can be termed as a negative point in this action is, when you That being said, if you decide to scale your website up to support multiple languagesmultilingual, it results in a complex will significantly complicates your localization flow. The localization flow becomes highly complex as more settings are required to be done, in order to support the custom changes introduced in the CMS. Building a channel of content to the  

The more custom changes were applied to your CMS, the more complex settings localization would require. Building a custom connector to your website in such a case users to tackle technical issues like:

will help you manage the following issues:

• understanding content processing overall as well as which content properties are localizable; 

• deciding which content must be protected or excluded altogether.Working out how ;

• finding ways to optimize content in a manner that it eases out integration with for the translation tool.;

• Scripts defining potential localization issues like (e.g. hardcoded strings, generation of content without language filters, etc) that must be fixed by developers before real translation.

To tackle and solve such complex integration issuesensure that your localization runs smoothly, we offer our product the ‘iLangL Cloud’'iLangL Cloud'. It is designed specifically to help resolve all integration related problems of our customers irrespective of whether they have aimed at detecting and resolving integration issues, no matter if customer has a single language, multilingual or multi-portal website. In this regard our website calibration services does not than aiding you in speeding up the processes of content localization. It also helps build an optimal channel, by linking your Our calibration services will also help to speed up the content localization. They will allow building an optimal channel that will link customer's website and the translation toolmanagement system. Our product ensures that no hurdle remains once our customers embark on the localization race.

To start working with our system, you need to go through three stages, we . We call it calibration.

Calibration is a process of checking on the way During calibration we double check if everything is setup set up properly and is as required and planned before running the localization process in actualruns smoothly, before we kick off the actual localization process. To perform this process calibration, you need understand the to understand a few key aspects:

• content structure

• ;
• how to filter

• content for translation

• ;
• how to optimize content for

• a translation tool;
• how to veriy the applied settings.

Content calibration process includes next steps:

1. Connection – establishing connection between iLangl cloud and customer’s CMS.

2. Configuration – content filtering and content processing.

3. Verification – final checking check which includes verification in Translation of compatibility with a translation tool, verification of translated content delivered back to client system and verification of the import to CMS and end result.

Why is

Calibration Required?

By default, connector settings cover the simple and general setup of Content Management System (CMS). iLangl provides connectors which help with simple settings like installation of CMS and translating e.g. CMS setup, translation of static content types, etc). However, as websites are , nowadays, customer needs are more sophisticated than that. Websites are usually highly scalable and contain lots of dynamic for efficient content that requires localization. Foreseeing and matching the exact customer's configuration without a thorough preliminary check becomes extremely hard in such a case. Let's take Wordpress for instance. At first sight, Wordpress seems to be quite simple. However, the CMS has more than 40,000 additional plugins which makes a connection between Wordpress and TMS significantly harder.

This is where website calibration becomes essential.
The connectors we offer cover most of  the general configuration and they highly adjustable. However, it is difficult to completely match customer configuration to the translator settings by default as we cannot predict or know what elements might be there on the customer website. Complete and proper calibration of website requires additional work, as each CMS has its own configuration which is impossible to predict. Our website calibration service will help resolve this issue for you. We are highly adjustable and manage to cover the bulk of general configuration aspects. We deliver a complete solution for better enhanced dynamic system integration. Thus, to set up the CMS properly, website calibration becomes essential.

Website calibration sounds complicated, we have simplified it for you and here is why you need it:

• The key focus of iLangl is to make sure the multitude of changes made to your website’s content are always reflected in the translated versions. Hence, we recommend continuous localization of web content.

• This is one of the key reasons we at iLangl have developed iLangL Cloud to ease the process of website calibration.

• We have made it easy for our customers to move towards continuous localization resulting in continuous and accurate translation rather than restricting translation and localization into a one time project.

Let us take the case of Wordpress. Wordpress seems to be simple when we start to build integration. The CMS has more than 40,000 additional plugins which results in significant complexity during integration phase between wordpress and the translation environment. Thus. website calibration is the key to successful translation.

Channel connection

The first step before starting preparation content for localization is to establish  

iLangl calibration will ensure:

• accurate content processing: its export, translation and import to customer's CMS;

• continuous localization is a streamlined and simple process

Channel Connection

First step of automated localization is establishing a connection between iLangl cloud and customer’s CMS. This process is described in detail details here. You should also to keep Please bear in mind that every CMS is specific unique and requires specific settings.

Anchor
content_conf content_conf

Content

Configuration

Once iLangL Cloud has access to your CMS, you have to must clearly define the scope of translation (what should/shouldn't be translated and what not. You have to let our system know what results you want to see after localization. For this you should make ). In order to do this, please create content configuration which includes two steps:

1. Content type configuration - clarification clarifes which types of content system should handle.

2. Content filtering - tuning what indicates which items inside the content types and according to what rules will be processed

1. should be processed and how (processing rules).

Content Type Configuration

Our system transfers all the content from a CMS splitting dividing it by types. Content type is iLangl unique description of entity. Based on content type we handle content, we apply rules for export and import content. Every type is unique and has it’s its own distinctive features. Each content type has its own unique individual settings. Each content type has rules like how to extract content and import content to CMS.We are using very simple Based on the type, we apply rules for content processing, export and import. 

Our structure of content types . The structure of content type is as listed below.is very simple. Please check the image below:

Each section item in the section list can be translated, which is extremely useful when you are building highly scalable, multi-lingual and CMS Portable websites. To avoid replication, speed up the translation , and reduce translation costs, iLangl enables allows you to choose whether to translate a field should be translated or not.

For starting To start configuration process, you should know which elements from your system should be translatedsystem elements require translation. In some cases, you will need access to the database and site backend to specify all list of the content which items you need.

Here you can find the instruction  which describes on how to work with content types.

Content

Filtering

In iLangl Cloud, we are using two types of filtering:

1. Static filtering –  management of translatable fields with binding to the content types

2. Proactive filtering – tag processing.

If your site is simple without dynamic fields, the first type can be suitable and sufficient for you, for example you use doesn't contain any dynamic fields (e.g. Wordpress CMS without advanced plugins. But ), static filtering should suffice for you. However, if Wordpress uses plugins with a lot of properties, which require further processing, you should use a second type of filtering for successful fully localizationto reach the best localization results.

Static

Filtering of

Translatable Fields

For every content type that you are included in localization include into localization scope, you can manage fields which will be translated or special rules how to handle for handling them. How to manage translatable fields you can find information To find out more about translatable fields management, please go here.

If you prefer to filter content using tags processing, you can enable a rule which makes making all the fields of current content type translatable and after that . Once done, you can process fields using tags.

Anchor
proactive proactive

Proactive

Filtering

Proactive filtering is more complex type of filtering and may require deep technical understanding how the of site is builtbuilding.

When your site is complex enough, proactive filtering is inevitable required to translate its ensure that content is translated properly. There are Some sophisticated CMSs , like Umbraco, that channel for it can be tuned correctly only through proactive filtering.Proactive filtering (e.g. Umbraco, etc) require proactive filtering to establish correct connection.

It is performed by applying rules how to handle tags.As first step you should enable in section Content for all Content types fields for processing. For this you should set rule for including content using regular expressions. For example .+ for tag handling.

To start with, please go to 'Configurations'>'Content'>'Content Types'. Click 'Edit' under the 'Actions' column and mark all the translatable fields that require processing. Please use regular expressions to set a rule for including content. 

For example '.+' means allow all properties.

After this you should set up replacement rules. For this you should Once done, please move on to replacement rules. In order to set a replacement rule, please switch to 'Text' tab and activate 'Wrap values to tagtags' option in section 'Text'the drop-down list.

Now, tags are ready for configuration. For You can customize the processing flow for each tag , that was automatically detected by iLangL Cloud (your website original tags) or manually configured by the text encoding (here described wrapping text in tags) , it’s possible to customize processing flow. . You can choose which content parts should be translated being split by tags. You  Apart from that, you can also use the preconfigured settings which were configured early. Just upload to the iLangL Cloud XML document with rules how to handle tagsfor tag handling to the iLangL Cloud.

Each item may have it’s its own translation rules. You can find the detailed instruction on how to process tags in the dedicated article.

Anchor
verification verification

Verification

Verification is the final step that ends wraps up your calibration process.

All described actions you should make the aforementioned steps should be made on your test environment and only after final verification you can transfer all settings to production environment.

Export content

After all configuration was done you need to make then transfered to the production once final verification is done. 

Content Export

Once content configuration is done, you should try out your first content export and to verify if the site is ready for final export. You should select . In order to do that, please select a language for testing and make pseudotranslation using Translation tool. After pseudotranslation was done you should to go perform a pseudo-translation using a translation tool. Once done, please go through the exported content in Translation tool and analyze exported text. It should not include technical information, tagsthe translation tool and make sure it doesn't include any tech information, tags, special characters, you etc. You should only see only that text splitted by segments which you want to translate.the actual segmented text for translation. 

If you see that some wrong information is present in exported fields, you should make configuration again.any odd data in the exported files, please perform re-configuration. 

If everything looks good, you can go move on to the import step.

Content Import

After Once export to test language was donetested, you can do import and publish the translated content to test environment. After import and publish was finished, pay Pay attention to the report , is it was fully successful. Then you should to check all places where content was translated, do they look good on the site?If something wrong you need to check configuration again or fix bugs on the web site if it can not be configurated. After all fixes you need to repeat import and publish processto see if import was successful, and check whether translated content looks good on your site.

If something is wrong, please double check configuration. If the issue in question can't be configured, please fix the bugs on your website and repeat import and publishing.

This step can require a couple of iterations before you make sure that everything is looks good.