Hi Brad,

Depending on what file type are you using for parsing XML files (new or legacy), you might need to set the options as in the following screenshots:

1. Legacy:

2. New:

In the legacy file type, under tag definition you have to add: (\<(/?[^\>]+)\>) as a placeholder.

Regards,

Magda

Hello Paul,

we are struggeling with the same problem.

Here is a sample of the XML code:

<xsl:variable name="hinweis-platzhalter">Bei den Operatoren <![CDATA[<em>]]>ist gleich (=)<![CDATA[</em>]]> und <![CDATA[<em>]]>ungleich<![CDATA[</em>]]> können die
Platzhalter <![CDATA[<em>]]>*<![CDATA[</em>]]> und <![CDATA[<em>]]>?<![CDATA[</em>]]> verwendet werden.</xsl:variable>

We use a custom filetype liek this:

But that is the result:

As you can see segment 14 to 22 should be normally just one segment. The tags are not the problem, but we are not able to avoid the splitting after every CDATA-tag.

Thank you very much in advance.

Hello Paul,

we are struggeling with the same problem.

Here is a sample of the XML code:

<xsl:variable name="hinweis-platzhalter">Bei den Operatoren <![CDATA[<em>]]>ist gleich (=)<![CDATA[</em>]]> und <![CDATA[<em>]]>ungleich<![CDATA[</em>]]> können die
Platzhalter <![CDATA[<em>]]>*<![CDATA[</em>]]> und <![CDATA[<em>]]>?<![CDATA[</em>]]> verwendet werden.</xsl:variable>

We use a custom filetype liek this:

But that is the result:

As you can see segment 14 to 22 should be normally just one segment. The tags are not the problem, but we are not able to avoid the splitting after every CDATA-tag.

Thank you very much in advance.

This is really dumb format... I wonder who "invented" something like this... :(

If the CDATA is always internal, you can perhaps use the legacy embedded XML filetype and make the CDATA a placeholder.
Otherwise I'm afraid that you would need some pre-/post-processing - a script to convert this crap to something more sensible for translation, and then convert back to this.