Funky KB Errata
Unlike the good ol’ days of the early, nerd-infested Internet, I am correcting most of my own mistakes posted online. Part of this has to do with the rise of commercialism and part is the rise of my technical abilities relative to, say, your grandmother (this assumes that your grandmother is not a doctor or somethin’).
So anyway, I was wrong about the stuff mentioned in “System.Xml.Xsl.XslTransform PROBLEM: Document Type Declarations Are Ignored; xsl:output Element; DOCTYPE; .NET Framework 1.1.” In fact, the xsl:output element is supported by the .NET Framework. My misunderstanding came from not knowing the following (from “Outputs from an XslTransform” at MSDN):
The
<xsl:output>statement is ignored when the output of the XslTransform.Transform method is an XmlReader or XmlWriter.The common language runtime uses Unicode UTF-16 (Unicode Transformation Format, 16-bit encoding form) to represent characters.
Behind all of this is the issue of encoding. Every beginning, .NET XML programmer should know that the default encoding for all strings is UTF-16. This is a fundamental that Microsoft “hides” from developers in favor of other conversations with ‘higher’ priority. I am sure that Don Box would have talked about this on MSDN TV but he does not have the time—and Dare Obasanjo is busy defending the beauty of MSN. My certainty comes from this quote from the WinFX SDK Beta 1:
The common language runtime uses Unicode UTF-16 (Unicode Transformation Format, 16-bit encoding form) to represent characters.
Needless to say that the mistake will be corrected. The Funky article will be rewritten. Eventually…