[rfc][icedtea-web] alowing bom character in basic parser

Jiri Vanek jvanek at redhat.com
Wed Jan 6 11:28:00 UTC 2016

Thsi is fix for

In bugI stated that no direct action will be taken, but then I realised that yes, tagsoup is 
removeing this for us, but maybe it is doing it wrongly - as the character is mandatory for utf 16 
and 32

So I think its a bit better to add it to switches in parser.

I hope I had refactored all the scanWhitespaces corresctly.


note - the patch contains he bom character. I dont know it it survives sending by email.
Eg in hexa edior, you should see the bytes right in front of first <!-- of EFBBBF.jnlp file:

-0,0 +1,59 @@.+<!--.+.+This f
-------------- next part --------------
A non-text attachment was scrubbed...
Name: enbaleBomForDefaultParser.patch
Type: text/x-patch
Size: 7654 bytes
Desc: not available
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20160106/153320d8/enbaleBomForDefaultParser.patch>

More information about the distro-pkg-dev mailing list