(2012/11/22 1:58), Shawn Steele wrote: > We aren’t going change names (since that’ll break > anyone already using them), we probably won’t recognize new names (since > anyone trying to use a new name wouldn’t work on millions of existing > computers, so no one would add it). Hey, why Microsoft changed "unicodeFFFE" to "unicodeFEFF"? What's the benefit of sacrificing the backword compatibility? According to Michael S. Kaplan, once some Microsoft people (including you) said that they wouldn't change it because of compatibility. https://blogs.msdn.com/b/michkap/archive/2005/09/11/463444.aspx?Redirected=true I admit your have a valid point, but why don't you do what you says? -- [email protected]
- Re: cp1252 decoder implementat... Buck Golemon
- Re: cp1252 decoder implementation Martin J. Dürst
- Re: cp1252 decoder implementation martin
- Re: cp1252 decoder implementation Buck Golemon
- Re: cp1252 decoder implementation Doug Ewell
- Re: cp1252 decoder implementation Philippe Verdy
- RE: cp1252 decoder implementation Murray Sargent
- Re: cp1252 decoder implementation Philippe Verdy
- Re: cp1252 decoder implementation Andrew Cunningham
- RE: cp1252 decoder implementation Shawn Steele
- Re: cp1252 decoder implementation Masatoshi Kimura
- RE: cp1252 decoder implementation Shawn Steele
- Re: cp1252 decoder implementation Buck Golemon
- Re: cp1252 decoder implementation Doug Ewell
- Re: cp1252 decoder implementation Peter Krefting
- Re: cp1252 decoder implementation Martin J. Dürst
- RE: cp1252 decoder implementation Doug Ewell
- RE: cp1252 decoder implementation Doug Ewell
- Re: cp1252 decoder implementation Philippe Verdy
- Re: cp1252 decoder implementation Peter Krefting
- RE: cp1252 decoder implementation Shawn Steele

