One more point of clarification. If I choose to “escape” and drop the CDATA marker:
<source>this is <b>my cdata</b></source>
Then it is also recommended, I assume, to encode using inline codes at that point as well:
<originalData>
<data id-“d1”> <b></data>
<data id-“d2”> <b></data>
</originalData>
…
<source>this is <pc dataRefStart="d1" dataRefEnd="d2" id=”tag1”>my cdata</pc></source>
But of course, I don’t really want to mess with CDATA anyway, so I’ll just leave it as a CDATA block
J.
Thanks again!
From: Ryan King
Sent: Tuesday, April 21, 2015 12:31 AM
To: Yves Savourel; xliff@lists.oasis-open.org
Subject: RE: [xliff] Question on CDATA in Xliff
Thanks Yves, that answers my question. It wasn't clear to me what escaped meant in this context and now I see it means using entities AND removal of the CDATA marker.
Ryan
Hi Ryan, all,
> What does "but on output they MAY be changed into normal escaped content" mean?
> Can it mean using inline tags? E.g.
> <source>no text <![CDATA[this is <pc dataRefEnd="d2" dataRefStart="d1"
> id="tag1">my cdata</pc>]]></source>
No. Not at all.
> Or is that not recommended and it means using entities? e.g.
>
> <source>no text <![CDATA[this is <b>my cdata≶/b<]]></source>
Yes, but it's not a CDATA section anymore, so the CDATA marker should not be there.
> I'm assuming since it says MAY, that it is also valid to not escape it at all:
>
> <source><![CDATA[this is <b>my cdata</b>]]></source>
Yes.
In summary, it means you can output:
a) like the original (preserve the CDATA notation):
<source><![CDATA[this is <b>my cdata</b>]]></source>
b) use the normal content notation, and in that case, any XML meta character (like <, or &) would be escaped:
<source>this is <b>my cdata</b></source>
Or, if you want to alo escape > to >:
<source>this is <b>my cdata</b></source>
Those three notations result in the exact same parsed string: "this is <b>my cdata</b>", which is what you had in input.
I hope this helps,
-yves