iLangL Cloud Spring 2016

Multiple Channel Configuration

The process of localization is a complex one, considering there are several participants at work, and even for those who employ advanced integration solutions for the job are met with untimely surprises every now and then. Have you just gathered all your content and have sent them for translation, thinking that this part of the job is over? Well think again! The process of content localization is never over, and if you think the process is done with and you can now relax until the translated content is received back, you are so very wrong! A customer may at the nick of time decide to fill in extra content on empty slots, or the developer of a customer’s site may suddenly decide to enhance or improve the layout of the site or install an additional module, adding in a new list of content properties as a result. In such a case, almost instantly you are left with the job of localizing new content. At this time you may be standing between the questions of whether I should wait for the previously sent content to arrive and then send the new task, which will be very time consuming, or should I simply resend the whole content again for translation?

If you are encountered with such issues in website localization process; we offer aid through introduction of a new feature ‘Multiple Channel Configuration’. Using this feature, new channel configuration can be created included only the new content that is required to be translated other than the primary content already previously exported for translation.

With our newest feature, you are now able to manage multiple configurations related to import and export of content translation along with providing a new dimension for solving all import and export issues.

What can be done with the ‘Multiple Channel Configurations’ feature?

  • Incremental content translation is based on properties
  • Separate workflows can be defined for separate sets of properties within the same content. For example, if you are configuring the metadata properties which are being operated by the SEO workflow, you can also configure other contents that are included in the localization workflow.
  • Content processing can also be managed in different ways for the similar content, however in different languages.
  • Different configurations can be linked with various Memsource templates in the automation workflow.
  • If more than one Localization Manager is working on a single data source, the scope of the content can be optimized on a per manager basis by offering specific configurations for every manager.

Introducing the multiple configuration options on your website can eventually make all processes easier. There are different configuration options for different cases and which greatly helps in avoiding unwanted situations that are a part of one time configuration job. There are various features which can be configured in different ways including:

  • Excluded content
  • Processing of content – configuration rule of tags and text encoding
  • Properties configuration/content types

Memsource Project Templates

In order to automate the process of project creation, project templates are extremely useful. It helps in creating different as well as repetitive projects for ongoing clients along with reducing the risk of human error.

The Memsource Cloud technology integrated in our website is exceptionally advanced and helps in fully automating the localization process for the platforms that we are currently supporting and will support in future. The major highlight of automation is related to the Memsource Project Templates that can easily specify suppliers, workflows, TB’s and TM’s once. Also the templates can be used continuously whenever new translations arrive at the Memsource. The project templates can also be specified for the customizing and optimizing of localization flow for every customer separately.

Now to answer the main question of how to separate the Memsource project templates between the different channels or customers, handling different workflows of localization? The system, offers an option where project templates list can be specified based on which specific channels can be accessible. As soon as the Memsource Integration Plugin is enabled for a channel, an additional step is taken towards the configuration of its templates.

During the automatic or manual content export of data from customer’s source to Memsource cloud, only the enabled templates for the channel can be used.