This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: [xsl] RE: [xsl] RE: [xsl] Handling of special characters like © etc
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: [xsl] RE: [xsl] RE: [xsl] RE: [xsl] Handling of special characters like © etc
- From: "Yogesh Dare" <yogeshd at cybage dot com>
- Date: Thu, 3 May 2001 13:28:27 +0530
- Reply-To: xsl-list at lists dot mulberrytech dot com
No I am not parsing .wml file as such It is a byte[] converted to
Inputsource and DefaultHandler.
Thanx
Yogesh.
-----Original Message-----
From: owner-xsl-list@lists.mulberrytech.com
[mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Robert
Nicholson
Sent: Thursday, May 03, 2001 1:05 PM
To: xsl-list@lists.mulberrytech.com
Subject: [xsl] RE: [xsl] RE: [xsl] Handling of special characters like ©
etc
Well if he's parsing .wml files that's not going to be possible.
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Tim Watts
> Sent: Thursday, May 03, 2001 12:09 AM
> To: xsl-list@lists.mulberrytech.com
> Subject: [xsl] RE: [xsl] Handling of special characters like © etc
>
>
>
>
> > I face problem for characters like &,<,> © etc.
> > Well I can actually replace these known characters by there equivalents
> like
> > for & i can put & and so on.
> > But I want some generic way to handle this.
>
> © has a number value of 169 (&169;)
>
> Or maybe you would like to use <![CDATA[ ]]> to avoid using replacement
> values
>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list