Re: Encoding not detected, EncodingChangeException

It may depend on what the server replies in the HTTP header and not what is
in the actual text of the response.
Sorry. It may be just a misconfigured server.
Try debugging the return packet (the parser implements
HttpConnectionMonitor) and see what the HTTP header has in it.

On Fri, Jun 12, 2009 at 7:54 PM, Frank Langelage
<[email protected]>wrote:

>  Hello,
>
>
>
> parsing the page http://www.nbp.pl/Kursy/KursyA.html leads to an
> EncodingChangeException.
>
> The htmlparser uses the default encoding ISO-8859-1 and does not recognize
> the charset UTF-8 given in the head of this html-page.
>
> Setting the encoding to UTF-8 using Parser.setEncoding() works, but
> shouldn’t this work without?
>
> Regards
>
> Frank Langelage
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Htmlparser-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/htmlparser-user
>
>

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects

_______________________________________________
Htmlparser-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/htmlparser-user