WordPress eXtended RSS file - Exported XML file from WordPress

Question

Hi, 
 
 I need your help on creating a filetype for XML file which was exported from WordPress. 
 The XML file contains many tags, and some of them contains CDATA, which has the content for translation. 
 I've read about it in many website, also tried to follow few guidelines - but still can't manage to view only the CDATA Content in SDL Studio 2014. 
 
 Can someone please help? 
 
 Best Regards 
 Fouad

Paul · Answer

Hi Yael, 
 If you have not sorted this yet I can suggest two ways to handle it: 
 
 If there is no translated content in the target yet, but just a copy of the source, then create an XML filetype using the target element. Then you can apply the embedded content filter to handle the CDATA, or 
 I can make available a BETA XLIFF filetype we are working on that can handle embedded content. It needs some work to copmplete it, but if the content of your file is not too tricky it may be suitable for your needs. I'd be happy to let you have a play anyway. 
 
 If it was me I think I'd go with the first option as it will make a better job of it if you only have untranslated content in the target so far. 
 Regards

Paul · Answer

Hi Tom, 
 
Based on your response it sounds as though you may be trying to import rules from an invalid xml file, or maybe a file that isn't xml at all. You'd need to share the file for me to give you a proper response to this one. 
 
email it to pfilkin@sdl,com if you like and I'll take a quick look. 
 
Regards 
 
Paul

Angelo Caltagirone · Answer

Hi Evzen. You made my day! 
Thank you so much for your help! 
Warm regards 
Angelo

Paul · Answer

Hi Angelo Caltagirone , 
 
Just to add to the response from Evzen which I agree with. The XLIFF filetype you mentioned never made it out of Beta because the current version of Studio has an embedded content processor in the XLIFF filetype. However, you need to use regex for this, so it's similar to the legacy XML filetype and it won't help you with the segmentation since the wordpress XML from WPML contains populated source and target which prevents Studio from applying its own segmentation. If they left out the target altogether it would be better, but I still prefer the XML approach since you'll need a lot of messing around to prepare the file using regex. 
 
I did have a call with a developer from WPML a few weeks ago and showed him how the XLIFF should be prepared in order to make it easier for CAT tools to handle correctly. Whilst I don't have any timescales on it I do think they are going to address their export since this is clearly affecting vendors in their own translation workflow. 
 
Perhaps we'll see an improved solution in due course. 
 
Regards 
 
Paul

Paul · Answer

Well Evzen, as you have told me many times, you are not a developer. If it was a piece of cake you can be sure it would have been done already. Perhaps you can speak to Patrik Mazanek on this and he can explain to you why it's more of a smorgasbord ;-)

Trados Studio > 1. Trados Studio

WordPress eXtended RSS file - Exported XML file from WordPress