[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Michael Kay wrote:
Well, there's no good way but it can be done. XOM hacks this for the less common character sets by trying to output the given character into a ByteArrayOutputStream and seeing whether it gets that character or a replacement character. It's an ugly hack, but I was pleasantly surprised at how well it performed. (For the more common character sets XOM uses algorithms or lookup-tables.)
Re: [xsl] xsl and toc.hhc (was xml -> htmlhelp and character 8220)
Subject: Re: [xsl] xsl and toc.hhc (was xml -> htmlhelp and character 8220) From: Elliotte Harold <elharo@xxxxxxxxxxxxxxx> Date: Fri, 12 Nov 2004 18:17:56 -0500 |
Michael Kay wrote:
As the passage above explains, the encoding most (a) be one that the JRE supports, and (b) be one that Saxon knows about. This is because the translation of unencodable characters into character references is done by Saxon, not by the JRE, and until recently there was no way of asking Java which encodings were available and which characters they supported.
Well, there's no good way but it can be done. XOM hacks this for the less common character sets by trying to output the given character into a ByteArrayOutputStream and seeing whether it gets that character or a replacement character. It's an ugly hack, but I was pleasantly surprised at how well it performed. (For the more common character sets XOM uses algorithms or lookup-tables.)
-- Elliotte Rusty Harold elharo@xxxxxxxxxxxxxxx XML in a Nutshell 3rd Edition Just Published! http://www.cafeconleche.org/books/xian3/ http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: [xsl] xsl and toc.hhc (was xml , Michael Kay | Thread | RE: [xsl] xsl and toc.hhc (was xml , Michael Kay |
RE: [xsl] document(), Pieter Reint Siegers | Date | RE: [xsl] XPath regular expression , Michael Kay |
Month |
Keywords