OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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.


From: Yves Savourel
Sent: ‎4/‎20/‎2015 7:42 PM
To: Ryan King; xliff@lists.oasis-open.org
Subject: RE: [xliff] Question on CDATA in Xliff

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 &lt;![CDATA[this is <pc dataRefEnd="d2" dataRefStart="d1"
> id="tag1">my cdata</pc>]]&gt;</source>

No. Not at all.

> Or is that not recommended and it means using entities? e.g.
> <source>no text &lt;![CDATA[this is &lt;b&gt;my cdata&lg;/b&lt;]]&gt;</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>


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 &lt;b>my cdata&lt;/b></source>

Or, if you want to alo escape > to &gt;:

<source>this is &lt;b&gt;my cdata&lt;/b&gt;</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,

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]