Approach to Translate Sitepublisher based pages.

ranjeeth

Hello Folks,

 

We have recently built a new responsive site which is primarily US but we are planning to  build in more local sites.We are planning to work with some transaltions vendor. Before the new site launch we used to send DCR's for translation and the dcrs's are returned back with translated content without much hasle.The problem now is we are using .pages where the content is fed from DCR's as well as Datums(some of which contains DCR datums).

We are basically planning to fetch all the dependent files for a .page and send it for translation but the problem is the .pages might even have the datum content which makes it very diffcult to map the feilds on .page XML to be converted when they are send for translation. We have thought of an approach but wanted to know few inputs regarding the best implementation approach. 

 

Please advise.Thanks for your inputs.

Rick Poulin

Personally, I think the simplest way would be to send the generated page (HTML) rather than all the fragments, and identify the portions of the page that require translation. Or, if necessary, send the HTML through a post-processor and strip out what you don't want.

 

If you do have to send a .page through, I'd say process it in workflow with an XSL that converts it into an XML format that is more legible for the translation service, with tags and IDs that you can use to map the translated text back into the original file later.