Hi Yael,

If you have not sorted this yet I can suggest two ways to handle it:

1. 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
2. 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

Hi Yael,

If you have not sorted this yet I can suggest two ways to handle it:

1. 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
2. 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

VPP Blog-translation-job-2.rar

Hi Paul

I have a similar problem with an xliff file (from WPML, I know, they don't do a good job there) and I cannot figure out, how to import the file in Studio. Do you still have this BETA XLIFF filetype? I send you one of the files for you to give a look at. Thank you very much for your help.

Angelo

Unknown said:

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.

Why is it still the legacy regex-based processor instead of the "proper" one? If the Studio/parsers code is written at least a bit modularly, it should be a piece of cake to implement the "normal" content processor... so that we would be finally able to pass the element content through a proper HTML parser.