New in Teamsite 7.2 is the “Globalized Content Manager” which is a marketing name for the long waiting support for localisations and translations. From the 7.2 manual:
“With TeamSite’s Globalized Content Management (GCM) solution, site authors, owners, and editors can quickly and easily launch a Web site into different markets on an international basis and then maintain the family of localized sites. Using ContentCenter Professional, an author can initiate the localization process for a Web site and then monitor the progress of that localization effort.”
The idea behind the tool is that every file (.page, dcr, site(-map), …) has a master ‘copy’ and 0 or more localised ‘copies’. Teamsite manages the relation between them and can thus ‘manage’ the translation (e.g. take action when a master-copy is updated so that the change is propagated to the localised copies). The localised version are stored with the locale in the name or directory path.
Each localised site has it own site-map and every localised page must be created and updated by the content editor. This is a crucial remark. The localised version of the page is NOT generated at request time but MUST be created beforehand. There is not fallback to default language mechanism. I am not sure which mechanism I like best.
See chapter 14 of the “ContentCenter Professional User Guide Version 7.2″ for more detail.
