This is the mail archive of the docbook-apps@lists.oasis-open.org mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[docbook-apps] Can I make a XSLT not resolve CDATA sections for programlisting?


In my documents I have snippets like:

  <programlisting>
  <![CDATA[int foo = 0;
  foo++;
  ]]>

I want to keep this after running it through XSLT. xsltproc resolves it, 
so I lose the 
beginning and end markers of the CDATA section. 

This is very similar to the problem I had trying to keep entity references 
from being resolved,
which Bob Stayton helped me with a while ago.

Can I keep these CDATA sections in the XSLT output? Or is it impossible?

I know I can use external code files as illustrated at:

http://www.sagehill.net/docbookxsl/ProgramListings.html

but I'd like to keep the code listings in place if possible.

Taro

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]