• State Suggested Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 431 subscribers
  • Views 5265 views
  • Users 0 members are here
Options
Related

CDATA and HTML embedded content - need help with settings

Former Member
Former Member

Hello all,

I've been struggling with a settings file for an XML for the last 3 days.

I'm currently using Studio 2014 SP2 (I can also use Studio 2017 if that would be better, I'm just more familiar with 2014).

Windows 7 based PC.

The XML file has been created from FIRST_Spirit.

CDATA is NOT to be translated (it contains a string of alpha-numeric which should not be visible in the bilingual file).

There is HTML embedded content - currently, this is minimal, so I can live without these tags if necessary.

XML content:

 

I've got CMS_Values that should not be translated: "stImParams" - that part I can get to work right. But I cannot get the CDATA to NOT appear in the bilingual. I've used both settings types in Studio 2014.

Does anyone have any suggestions?

Thanks in advance, Mindy
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    Just wanted to close this one off as we seem to have resolved it by looking at the rules that were really needed and then creating the XML file with these rules only. As opposed to importing all the elements and then trying to adapt them all to get what was needed. The problem with working this way is it's easy to have overlapping requirements and in fact Studio did complain with errors that invalid XML might get generated. So keeping it simple was the answer.

    Also worth noting that it isn't possible (as far as I'm aware) to identify elements containing CDATA using XPath. This is only a mechanism for supporting a dump of anything including characters that would be illegal in XML normally and can't be traced using XPath. So we found a way to identify these unwanted CDATA sections using the content of the attribute value as this seemed to include the word 'link' somewhere in the value whenever CDATA sections were included.

    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

Reply
  • 0
    Hi ,

    Just wanted to close this one off as we seem to have resolved it by looking at the rules that were really needed and then creating the XML file with these rules only. As opposed to importing all the elements and then trying to adapt them all to get what was needed. The problem with working this way is it's easy to have overlapping requirements and in fact Studio did complain with errors that invalid XML might get generated. So keeping it simple was the answer.

    Also worth noting that it isn't possible (as far as I'm aware) to identify elements containing CDATA using XPath. This is only a mechanism for supporting a dump of anything including characters that would be illegal in XML normally and can't be traced using XPath. So we found a way to identify these unwanted CDATA sections using the content of the attribute value as this seemed to include the word 'link' somewhere in the value whenever CDATA sections were included.

    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

Children
No Data