Re: Invalid code points

From: Bjoern Hoehrmann (derhoermi@gmx.net)
Date: Mon Jun 01 2009 - 11:27:52 CDT

  • Next message: Asmus Freytag: "Re: Invalid code points"

    * Hans Aberg wrote:
    >On 1 Jun 2009, at 16:56, Phillips, Addison wrote:
    >> Uh... the IETF does not define UTF-8. The Unicode Consortium does.
    >> But even if you want to build on the IETF documents, RFC 3629 was
    >> published six years ago. Basing a new implementation on something
    >> published 11 years ago and obsolete the last six years? Not a good
    >> idea.
    >
    >It says the date is November 2003, so it must be 2015 now :-).

    The history is thus:

      2044 UTF-8, a transformation format of Unicode and ISO 10646. F.
           Yergeau. October 1996. (Format: TXT=11932 bytes) (Obsoleted
           by RFC2279) (Status: INFORMATIONAL)
      
      2279 UTF-8, a transformation format of ISO 10646. F. Yergeau.
           January 1998. (Format: TXT=21634 bytes) (Obsoletes RFC2044)
           (Obsoleted by RFC3629) (Status: DRAFT STANDARD)
      
      3629 UTF-8, a transformation format of ISO 10646. F. Yergeau.
           November 2003. (Format: TXT=33856 bytes) (Obsoletes RFC2279)
           (Also STD0063) (Status: STANDARD) 

    -- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/

    This archive was generated by hypermail 2.1.5 : Mon Jun 01 2009 - 11:29:26 CDT