Re: HTML5 encodings (was: Re: BOCU patent)

From: Doug Ewell (
Date: Mon Dec 28 2009 - 22:19:46 CST

  • Next message: Doug Ewell: "Re: HTML5 encodings"

    Peter Krefting <peter at opera dot com> wrote:

    >> UTF-32 is stateful/poses a security risk?
    > If mistakenly interpreted as UTF-16 by a web browser that does not
    > support UTF-32, it would introduce nul characters into the character
    > stream, which may cause interesting problems.

    Creating standards that forbid conformant browsers to support certain
    encodings, discourage them from supporting others, and require them to
    interpret others as if they were something else, doesn't exactly seem
    like a constructive way to avoid problems like this.

    Doug Ewell  |  Thornton, Colorado, USA  |
    RFC 5645, 4645, UTN #14  |  ietf-languages @ ­

    This archive was generated by hypermail 2.1.5 : Mon Dec 28 2009 - 22:21:41 CST