I probably won't be able to help much, but the first place I would check would be the segmentation rules, which in Studio are defined inside the translation memory used. If you've been messing with segmentation, maybe check that the default segmentation rules are still being used (one should be called "Full stop", which should usually break segments at a period). Otherwise, it will have to do with something deeper, i.e. perhaps how the tags are being parsed.

Thank you! I've already gone back to the default settings just in case, but it didn't help.

Claudia Ciaschini

Your screenshots are far too small to be able to read anything, but I imagine the problem is that the content of the file has been dropped into one big CDATA section inside a single translation unit in the XLIFF.  This means you are going to have to be creative to handle this.  It's been discussed many times in this community.  Perhaps review some of these posts:

https://community.sdl.com/product-groups/translationproductivity/f/studio/34087/why-embedded-content-in-cdata-is-not-processed-in-a-custom-xml-filetype-used-for-xliff-from-wordpress

https://community.sdl.com/product-groups/translationproductivity/f/studio/38102/cdata-tags-in-trados-studio-not-working-properly

https://community.sdl.com/product-groups/translationproductivity/f/studio/12708/how-to-fix-very-large-segments-in-studio-in-xliff-projects-from-wordpress-wpml/82354#82354

https://community.sdl.com/product-groups/translationproductivity/f/studio/9222/xliff-filetype-that-can-handle-embedded-content

... and many more.

Thank you Paul, yes that was it! It was indeed one big CDATA section and I finally managed to create a custom filetype that worked. The way it worked for me was, under embedded content processor settings, instead of using the <within CDATA element: Html Embedded Content 5 2.0.0.0> option, I had to set the <defined by document structure information> option and play with the configuration over there to get the tags right, but it finally worked, thanks!

Excellent… glad you figured it out Claudia Ciaschini

Excellent… glad you figured it out Claudia Ciaschini

I seem to have more or less the same problem. Activated the CDATA selection for document structure (see screenshot), but have no clue what else I could do to get a smaller segmentation. I have a huge text between CDATA tags and the file reacts quite clumsy on opening, scrolling etc. Any hint?

Alejandro Mestre Vives 

You should declare list item (li) to exclude in the advanced options.

I guess you mean this,

but unfortunately it looks the same

Alejandro Mestre Vives 

Are you sure your xliff is a xliff 2.0? As you are using this file type. To check this, either select TAG ID in the view menu or look at the file type shown in Files section. Or use the preview to see which file type is being used. And of course make sure, that you are adapting the file type in your project settings and NOT in File -> Options.

Seems to be the right version. For good measure, I also added the changes in the 1.2 version. But it doesn`t seem to help:

 Alejandro Mestre Vives 

Maybe ensure your rule is set to exclude BEFORE you create your project and make sure that you apply the change in the settings you use for your project.  So if you use a project template then make the change to the rule in the project template.  If you use a previous project then make the change in the project settings for the previous project.  If you use the default then make the change in either Tools -> Options or the default project template.

But most importantly do this BEFORE you create your project.

You could also consider working with the Multilingual XML filetype?

Ok, the project is already created. Is there any possibility to update it or do you mean I should delete anything (also other files I already translated) and start from scratch? Not quite a pleasant idea ...

On the other hand, may be I could start a new project for those CDATA files. May be that would be better ...(?)

Alejandro Mestre Vives 

Alejandro Mestre Vives said:

Ok, the project is already created. Is there any possibility to update it or do you mean I should delete anything (also other files I already translated) and start from scratch?

Other files are fine, just leave them.  You have two choices.

1. create a new project with only the files you have problems with
2. remove the files you have problems with, update the project settings, then add them again to the same project

If it was me I'd create a new project for the ones I had problems with so I didn't change existing project settings and risk causing a problem for existing files.  Chances are you wouldn't have a problem given you managed to handle them ok already, but I prefer belt and braces. Certainly I would take a copy of the entire project first and zip it somewhere safe!

Alejandro Mestre Vives said:

Not quite a pleasant idea ...

Trivial though seeing as you've already translated them.

Ok, that's a fine idea and exactly what I'll do now, and I'll also take out the exclude rule from the old project hoping the best for the new one

Thanks a lot! (If it doesn't work I'll get back :)

Sorry, it's me again. Just to be sure: exclude rule should be for Tag-PAIRS, right?

Thank you