This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Character encoding in MSXML 3.0 from VB
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] Character encoding in MSXML 3.0 from VB
- From: Mike Brown <mike at skew dot org>
- Date: Wed, 10 Jan 2001 12:32:02 -0700 (MST)
- Reply-To: xsl-list at lists dot mulberrytech dot com
Christopher R. Maden wrote:
> Not to attempt to defend Microsoft's standards record
In this area MS just built on what IBM did. So did Apple. And those
companies are guilty of moving characters around. Why not beat up on them,
too? Oh, I forgot, it's cool to bash Microsoft every chance we get,
because they are the only company that subverts open standards. Right.
Also, to clarify, the ISO/IEC 8859-1 *standard* only defines characters
for the (decimal, 8-bit based) code space 160-255. The IETF/IANA-approved
"iso-8859-1" coded character set for the Internet defines characters for
the entire 0-255 range. The (very recently) IETF-approved "windows-1252"
coded character set isn't subverting any *standards* because the
"iso-8859-1" coded character set is not a standard. It is just a character
set that was named after one. If anything, we should blame whoever came up
with iso-8859-1 because they subverted the ISO/IEC 8859-1 standard when
they included ASCII characters in it :)
- Mike
____________________________________________________________________
Mike J. Brown, software engineer at My XML/XSL resources:
webb.net in Denver, Colorado, USA http://skew.org/xml/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list