- Those who request website translations often have no idea what platform is used nor do they really know how much content is present.
- They have very little understanding of the technical details or importance of translatable information hidden in tag attributes, selection lists, etc. and so there are often misunderstandings about the true volume to be translated.
- There are a lot of sloppy cowboys slogging through the bog, glibly bidding low rates to translate sites they neither understand nor truly care about, and their victims... uh, prospects, customers, whatever... usually lack the expertise or the patience to understand the difference between a wild-ass lowball guess from someone lacking the skills and tools to do the job right and a carefully researched, reasonably accurate estimate of time and effort from a professional.
Three or four years ago I translated a small web site for a friend's company. At the time, the site used the Typo3 content management system, which proved to be troublesome. Not so much because of the technology, but because of the service provider using it, who rejected any suggestions for providing the content to be translated in a form that would not require his manual intervention at the text level. He copied, pasted and improved (German: verschlimmbesserte) my translation as only a German with full confidence in his grade school English skills could. It was... not what anyone had hoped for, and I never found the heart to mention all the mistakes in the final result.
So now, when someone asked me to have a look at their new site, I felt a bit queasy. Nunca mais, I thought. No way, José. Or Wolfgang as it were. But in the meantime, unbeknownst to me, he had switched service providers and CMS platforms, and the new provider managing his web content is a professional with a professional understanding of sites for international clients in many languages. And he uses WPML. The right way!
So now it was up to me to figure out what's what in memoQ. So first I used the memoQ XLIFF filter on all the little XLIFFs supported by the plug-in. I quickly saw that a few other things were needed, like a cascaded HTML filter...
Somewhat messy, but doable once the HTML tags get properly protected by a chained filter.
Then I tried again, this time applying memoQ's WordPress (WPML) filter. And this was the result:
That was easy. Hmm. I think I know which method I prefer.
So for translations of WordPress websites properly configured to use WPML technology, the new memoQ filter looks like a winner!