Cart
[Home] [By Thread] [By Date] [Recent Entries]
Dan,
At 01:31 PM 8/26/2003, you wrote: Actually that brings up another point; Why when I translate with saxon is the é not getting translated to é and remains é? Actually it is getting translated. It's probably that when your processor serializes the output, it's saying "oh, a & #x00E9, that's an & eacute!" and changing it back (probably since you're writing HTML and it knows enough HTML to know this). I also noticed that the following entities: †, ♦, • are translated by saxon to †, ♦, • respectively when my character mapping is †, ♦, •? If you try it in your handy hexadecimal calculator you may find that 8224 in decimal notation is 2020 in hexadecimal. That is, it's the same character, even the same number, just a different way of representing it. (The 'x' in the reference is the tip, to the parser and to you, that's it's in hexadecimal.) Cheers, Wendell
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
