Multiple languages for SP

Andy Knipp

How many people have done multi-lingual sites in SP when integrating with a translations utility ?

I am curious on the approaches used.

Since tools have to be able to parse the date (usually can do .html or .xml), a SP approach would require either using DCRs or a translation preprocessor that can read .page files.

The DCR approach is standard and easy, but users would hate it. Why bother with SP when you are using DCRs for every freaking page on the site ? During the sales process, the users all saw the sexy drag and drop SP interface, using DCRs would not be popular.

So I am left with a preprocessor approach for the .page. For grins I sent a translations company a .page and their reply was: WTF is that ?

Are there other approaches ?