Overview
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.
If customer 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?
With ‘Multiple Channel Configuration’ 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.
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 Translation tool 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
Default behaviors
Very often business case required to create many configurations to handle specific type of settings. At the same time you still need to update and keep sync other configuration properties. This might be challenged tasks when you have many configurations. Each time when you change configuration property you need to apply changes to all relevant configuration. To solve this problem our system support default behaviors for excluded content, content type, text and tag encoding settings. You can create a new configuration and mark some settings like default. In this case our system will use settings from 'Default configuration'. All what you need to do is to keep updated only 'Default' configuration and changes will affect to all setting with enabled default behavior for all other configurations.
