There's a subtle distinction going on here. Character 160 (0xA0) is a non-breaking space in both Latin-1 and Unicode. However the binary representation of a Unicode character depends on what encoding you use:
Note also, that the Windows 1252 character set is not a super-set of Latin-1. Latin-1 is an 8 bit character set in which every character position has been assigned. Microsoft decided the the control characters in the 0x80-0x9F range were not useful so in CP1252 they removed those character assignments and replaced them with other characters (such as 'smart quotes').
I think we'd all agree that 7-bit ASCII is insufficient for general use outside of the US (in fact it can't even represent the US 'cent' symbol: ¢). The 8-bit Latin-1 character set is a 'point solution' for western european nations but it is no longer sufficient for them either (eg: no Euro symbol: €). The clear way forward is widespread adoption of Unicode - it's here now and it works already. Clinging to and tweaking region-specific 8 bit encodings is a dead-end strategy.
Sorry if this sounds like a rant - it's not intended to be personal. People just seem to waste a lot of time trying to translate perfectly good Unicode characters back into 'legacy' encodings instead of just using them as they are.
In reply to Re: Re: libXSLT and  
by grantm
in thread libXSLT and  
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |