Variations and Multiple Languages Sites in SharePoint Server 2010 (ECM)
Many companies operate globally, and even in their home markets they often must appeal to a diverse customer base that speaks multiple languages. This diversity often requires that their Web presence sites be customized for markets of different cultures and geographic regions.
Maintaining many similar versions, or variations, of a Web presence site is difficult and time-consuming because of the need to coordinate the creation and updating of content among all of the different variations.
To simplify this process, Microsoft SharePoint Server 2010 provides a site variation management system. Site managers can define a series of site variations and mark one variation as the primary variation. This ensures that changes made in the sources are properly reconciled in all other variations. This system is integrated with workflow and content import or export to enable integration with third-party translation services. New updates to target variations can use the workflow system to automatically send updates for translation. When translation is completed, updates can be imported and set for final approval through the workflow system.
Variations can be used for publishing related sites or pages, either for use in multilingual content or for device targeting.
Hello All,
We maintain multilingual site using Variation. We have a master page in each language, which is specified at the root site of each language. To be more precise, English site root is hostname/en/, hostname/fr for French etc. And mymasterpage-en.master is specified at the /en/ site, mymasterpage-fr.master is at /fr/ etc.
The problem is that when a new site in the source English hierarchy e.g. as /en/subsite1 is created and propagated to target sites as /fr/subsite1 etc, the masterpage used is mymasterpage-en.master rather than -fr.master.
The Site Master Page Settings of /fr/subsite1 shows that the option "Inherit site master page from parent of this site" is selected. However, you see mymasterpage-en.master is selected although greyed-out (greyed-out obviously because the option is not active).
It is ridicuous, isn't it?
I am pretty certain that we did not have this issue with MOSS 2007. We migrated the site to 2010 and now have the issue. Verified also that it exists even with a fresh installation.
If someone here had the issue and has overcome it, please share the solution with me.
Thanks a lot in advance for your help.
Kazu
- 6/14/2011
- kazutsugu