Garbage in Save Target XML files

I have a series of XML files that open file in Trados Studio. But when I save as target it saves the file with markup garbage text. Here is a sample:

<![CDATA[[vc_row layout="normal" mp4="" webm="" video_overlay="rgba(0,0,0,0.45)" video_placeholder=""][vc_column][layerslider_vc id="34"][vc_empty_space height="20px"][vc_column_text]
<p style="font-size: 14px;"> Technologies 提供最可靠和多样化的光学镜片实验室,以满足各种需求和预算。我们多样化的配置提供了一个完整的解决方案,与同类产品相比,占地面积更小,价格也更实惠。</p>
<p style="font-size: 14px;">立即致电 1-800-262-8761 或<strong><span style="color: #1e73be;"><a style="color: #1e73be;" 

These files are to be imported into Wordpress, but as is they do not import correctly. How do I save the files without the markup garbage? Thanks in advance for your help.

PS I tried to use difference encoding formats but the result is the same every time.

emoji
  • I would like to say however that as Wordpress is the number 1 CMS in the world, it would behoove Trados to have an out-of-the box filetype which does not need a Paul Filkin to oversee the localization process.

    I think there are  couple of things to take from this comment.  First of all it doesn't take a "Paul Filkin" or any specific person to handle this.  The solution I provided is out of the box basic functionality available to anyone who knows how to create custom XML files in Trados Studio.  You can even see from my response that there was nothing difficult or complicated to achieve this.

    I'd also note that the localization format from Wordpress, which is also problematic, is XLIFF and not XML.  The files you are handling look like their backup XML format which is a sort of exported RSS feed not designed for localization at all.

    I am always amazed by comments like this where you don't think Wordpress should do something about their localization capabilities.  Wordpress is one of the largest platforms in the world... I won't use the term CMS because I think this is too much of a stretch for me... and yet they still don't support localization properly.  Anyone looking for a serious CMS platform for a multilingual environment shouldn't choose Wordpress in my opinion.

    Notwithstanding all of this, given the array of files we see from Wordpress all of which normally present a problem because of their lazy approach to managing content for localization it may well be that we could try to resolve this on our side and try to accommodate their crap for less technical users.  So... if you, or anyone else, can provide a specification for a Wordpress XML and XLIFF, then I will commit to developing filetypes to support them via the appstore.  I think that's a fair compromise... I could probably do it, but instead of me digging around to find out how these files should be handled, you do that bit and we'll create the filetypes and provide them for free.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!

    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji