Crash in PDF code when script has illegal UTF-8 or UTF-16 sequences
Created attachment 113175 [details] Patch
Comment on attachment 113175 [details] Patch Clearing flags on attachment: 113175 Committed r98970: <http://trac.webkit.org/changeset/98970>
All reviewed patches have been landed. Closing bug.
Is it correct to only support UTF-8 and UTF-16 with BOM? Where should the encoding information come from?
(In reply to comment #4) > Is it correct to only support UTF-8 and UTF-16 with BOM? Where should the encoding information come from? That’s a good question, and it occurred to me too. But far, far less important than this bug.