ISSUE-31: invalid bytes and default character encoding from Web APIs Issue Tracker on 2006-02-24 (public-webapi@w3.org from February 2006)

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Fri, 24 Feb 2006 13:36:50 +0000 (UTC)
To: public-webapi@w3.org
Message-Id: <20060224133650.79349DAFBE@w3c4-bis.w3.org>

ISSUE-31: invalid bytes and default character encoding

http://www.w3.org/2005/06/tracker/webapi/issues/31

Raised by:  Everyone
On product: XHR

During the Oslo F2F the following text was discussed:

   Otherwise, returns the body of the data received
   so far, interpreted using the character encoding
   specified in the response, or UTF-8 if no
   character encoding was specified. Invalid bytes
   must be converted to U+FFFD REPLACEMENT
   CHARACTER.

... several people suggested that instead of UTF-8 we should probably state
ISO-8859-1 (per RFC2616?) and that "invalid bytes" should be clarified.

Received on Friday, 24 February 2006 13:37:09 UTC