encoding and saxparser 2003-01-16 - By neilg@(protected)
Hi Joseph,
I had a feeling something like that might have been the case. I'll bet
there's some difference in the way you're viewing the SAX output as
compared to the DOM output. If you look at the integer values of the chars
your ContentHandler is getting, I'll bet 63 (0x3f) isn't among them...
Cheers,
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: neilg@(protected)
|---------+---------------------------->
| | Joseph Shraibman |
| | <jks@(protected)|
| | net> |
| | |
| | 01/16/2003 04:21 |
| | PM |
| | Please respond to|
| | xerces-j-user |
| | |
|---------+---------------------------->
>----------------------------------------------------------------------------
-----------------------------------------------------------------|
|
|
| To: xerces-j-user@(protected)
|
| cc:
|
| Subject: Re: encoding and saxparser
|
|
|
|
|
>----------------------------------------------------------------------------
-----------------------------------------------------------------|
neilg@(protected) wrote:
> Hi Joseph,
>
> In order to be of help, we'll need to know exactly what behaviour you're
> observing, how you're observing it, and why it's at variance with what
you
> expect.
My xml has this in it:
<?xml version="1.0" encoding="ISO-8859-1"?>
<data>
<firstname>D�cio</firstname>
</data>
Using a DOMParser on the file I get D�cio out, but using a SAXParser I get
D?cio
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
|
|
