--- Comment #10 from Lazar <> ---
Thanks Mark! I tried the fix from 8.5 trunk and it works.

Something I noticed while debugging, probably it is not a problem, but I prefer
to mention it:

In EncodingDetector's constructor, on line 61

The buffered input stream is being reset, but on the next lines the number of
bytes which should be skipped are read from the initial input stream and not
from the buffered input stream. Is this intended? Because when the buffered
input stream is reset, the underlying input stream is not reset and its
position stays where it was - e.g., at 4. And then when the bytes which should
be skipped are read from it its position goes to e.g. 8. Is this intended?

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to