Rossana Triaca wrote:
WXR files (WordPress eXtended Rss) use a unique type of XML with varying namespaces (i.e. tag dictionaries) and, unfortunately, since they were not conceived for interchangeability (just for porting content between themes), they don't have any fixed standard schema or dtd that you can use to "read" them correctly with a CAT.
You can of course translate the .xml as is, but a lot of "code" will be imported and you'll have to decide what needs to be translated and what not. Moreover, this .wxr file will not include the theme strings, so even if you do a great job the client will still have a semi-localized website on their end (unless they are planning to use a theme they already have in the target language).
The good news: for translation, the workflow nowadays is different using either plugins as you mention (awful for translators!) or POEdit. Since Wordpress uses .PO and MO files (gettext) for everything, even themes, you can ask your client to send you the .PO file or files instead and you can translate them directly in POEdit (ew!) or, depending on your CAT of choice, you can work on the .PO files directly (Trados for example has a free OpenExchange addon that lets you work on them - haven't tried it yet though).
...i did something very similar for WP recently and used the PO Add-on for Studio and it worked properly. Delivered the job and got no complaints. I assume it was ok.
Installing the add-on may be a bit tricky as even after installation it won't show in the Filetype list unless you activate it, from the same Filetype screen and that option is not marked properly so you may skip it.
But i confirm it all works properly for Studio.