Hi Frank,
Please reply to the list, not to me directly.
Your problem is a parsing issue, not a serialization issue. Any entities
defined in HTMLEntities.res are used for serializing the result of a
transformation, not for parsing. You'll still have to define any HTML
entities you want to use in the DOCTYPE. The processes are in no way
connected.
Dave
"Frank E. Weiss"
<[EMAIL PROTECTED] To: David N
Bertoni/Cambridge/[EMAIL PROTECTED]
> cc:
Subject: Re: Native char, not
entity representation?
02/12/2002 03:42
PM
That's funny, in 2_3_D1, the pound entity is already in the
HTMLEntities.res file. However, the error seems to be
file:///U:/Projects/Computer/xalan/entities/entities.xml; Line 6; Column
16; XSLT Error
(javax.xml.transform.TransformerException): org.xml.sax.SAXParseException:
The entity "pound" was referenced, but not
declared.
David N Bertoni/CAM/Lotus wrote:
> Xalan-J's behavior conforms to the XSLT recommendation, which requires
> using such entities when they are known.
>
> If you want non-standard behavior, then you can change the resource file
> that Xalan uses to determine what entities are used. Go here, and search
> for "HTMLEntities.res" for more information:
>
> http://xml.apache.org/xalan-j/readme.html#done
>
> Dave
>
>
> Jay Burgess
> <[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
> h.com> cc:
> Subject: RE: Native char,
not entity representation?
> 02/12/2002 02:10
> PM
>
>
>
> Thanks for replying, but I don't understand your answer. My output
> encoding is 8859-1:
>
> <xsl:output method="html" encoding="ISO-8859-1"/>
>
> As I said in my previous email, I need something like "�" instead of
> "£". As far as I know, "�" is a valid character in the 8859-1
> character set (decimal 163), so I'm not sure what changing the encoding
> would do for me. It seems that because my output method is HTML, Xalan
is
> automatically turning it into the entity "£".
>
> Since Saxon has the ability to do what I need, I was hoping that I could
> accomplish the same thing with Xalan.
>
> Jay
>
> -----Original Message-----
> From: Joseph Kesselman/CAM/Lotus [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 12, 2002 3:54 PM
> To: Jay Burgess
> Cc: [EMAIL PROTECTED]
> Subject: Re: Native char, not entity representation?
>
> Native to whom? Unless the character is in the encoding, there is no
> "native representation". If it is, simply use xsl:output to specify that
> encoding, and everything should work as you intend.
