W3C home > Mailing lists > Public > public-webapi@w3.org > May 2006

Re: ACTION-148: responseText and encoding

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 15 May 2006 11:32:48 +0200
To: "Ian Hickson" <ian@hixie.ch>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.s9k54y0b64w2qv@id-c0020.oslo.opera.com>

On Mon, 15 May 2006 01:54:02 +0200, Ian Hickson <ian@hixie.ch> wrote:
>>    If the <code><term>readyState</term></code> attribute has a value
>>    other than 3 (Receiving) or 4 (Loaded), it MUST be the empty string.
> "it" here refers to readyState, which is wrong.


>>    Otherwise, it MUST be the fragment of the entity body received so
>>    far (when <code>readyState</code> is 3 (Receiving)) or the entity
>>    body when <code>readyState</code> is 4 (Loaded)), interpreted as a
>>    stream of characters.
> "or the complete entity body", or "or the entire body returned" or some
> such would make more sense.

Used "complete."

>>    If the response includes a <code>Content-Type</code> understood by
>>    the UA, with the exception that the rule in the final paragraph of
>>    section 3.7.1 of [RFC2616], and the rules in section 4.1.2 of
>>    [RFC2046] MUST be treated as if they specified the default character
>>    encoding as being UTF-8.
> That makes no sense at all. There's a missing verb as far as I can tell.

That part now reads:

     If the response includes a <code>Content-Type</code> understood by
     the UA the characters are encoded following the relevant media type
     specification, with the exception that the ...

>> [...]
> Doesn't really matter, IMHO. References are important when the reader
> might not know what was being referenced, but for this kind of thing...

Fine by me. Thanks for your comments.

Anne van Kesteren
Received on Monday, 15 May 2006 09:33:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:21 UTC