Thanks for replying. Yes - absolutely, in fact using CDATA's is ideal for XML code comments and for conceptual-content <code/> blocks, because you don't have to HtmlEncode it, you can just copy/paste right in there. For example, in XML code comments,
you can do something like this:
/// Summary goes here...
<threadsafety static="true" instance="false"/>
/// <?xml version="1.0" encoding="utf-8"?>
and it works great. In conceptual content, you can do this:
title="Sample web.config or app.config">
<?xml version="1.0" encoding="utf-8" ?>
and that also works as expected. That is, the CDATA parts aren't shown, and the XML is formatted and color-coded like normal. This is ideal because if you have a change in that sample code later, you can literally just paste it in - you don't have to
worry about re-HtmlEncoding it again. So, the only hitch is using this technique in a token.
Within conceptual content, can you point me in the direction to learn more about that source attribute? I searched and coudn't find much. I assume it's similar to how it works for XML code comments, but couldn't find the exact syntax. Thanks again - and
by the way, I've been heavily using SHFB I believe since it came out, and I'm a big fan. Thanks for doing what you do, this is a great tool!!