[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: On a more pleasant note
Barry Paul writes: > 1. Use namespaces (seriously!) > 2. Encode '<', '>', etc using entities > 3. Enclose the HTML CDATA sections [snip] > 1. This is OK if you are sure that the HTML is valid and well formed > 2. What else would you have to encode? (HTML entities?) > 3. Maybe some whitespace issues > > Seems like number 3 would be a good way to go. Actually, it's by far the worst of the three. When someone is actually generating the markup (as Tim is in this case), then there are immense advantages to being able to process the HTML with the same software as the rest of the document, so #1 is far and away the winner. After all, the human-readable documentation is meant to be part of the document. #2 is also pretty awful, but at least it won't blow up if the HTML happens to contain the "]]>" character sequence (say, as an emoticon?). All the best, David -- David Megginson david@m... http://www.megginson.com/ xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|