Getting warning about not detecting encoding when there is a charset declarartion
Original [issue 58](https://code.google.com/p/okapi/issues/detail?id=58) created by @ysavourel on 2009-04-24T03:03:43.000Z:
The attached file has a charset declaration but the HTML filter generates a warning saying no encoding could be detected.
Comments (4)
-
Account Deleted -
Account Deleted Comment [2.](https://code.google.com/p/okapi/issues/detail?id=58#c2) originally posted by @ysavourel on 2009-04-24T04:50:42.000Z:
Probably related to the new stream parser changes - text now comes in chunks rather than in the largest contiguous unit. I may be making some assumptions that are no longer true. Will squash this first thing tomorrow tomorrow.
-
Account Deleted - changed status to open
Comment [3.](https://code.google.com/p/okapi/issues/detail?id=58#c3) originally posted by @ysavourel on 2009-04-24T18:47:36.000Z:
-
Account Deleted - changed status to resolved
Comment [4.](https://code.google.com/p/okapi/issues/detail?id=58#c4) originally posted by @ysavourel on 2009-04-27T18:04:58.000Z:
fixed in jericho 3.1 Dev 5. Added unit test for this bug.
- Log in to comment
Comment [1.](https://code.google.com/p/okapi/issues/detail?id=58#c1) originally posted by @ysavourel on 2009-04-24T03:12:27.000Z:
I confirm, this seems to be a new problem: we seems to have the warning on every file now.