W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: v11-03 COMMENT: 18.48 Warning

From: Jeffrey Mogul <mogul@pa.dec.com>
Date: Tue, 14 May 96 16:14:09 MDT
Message-Id: <9605142314.AA14488@acetes.pa.dec.com>
To: Dave Kristol <dmk@allegra.att.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/488
    The second bullet says:
      .  Warnings in the user's preferred character set take priority over
	 warnings in other character sets but with identical warn-codes and
    How can the user agent tell which warning is in the user's preferred
    character set?  We haven't provided a way to specify character set.
Yes, we have.

Roy had to explain this point to me several times before I
understood it, but if you actually follow the reference mentioned
in 18.48:

    If a character set other than ISO-8599-1 is used, it must be encoded
    in the warn-text using the method described in RFC 1522 [14].

you would see examples like:

      From: =?US-ASCII?Q?Keith_Moore?= <moore@cs.utk.edu>
      To: =?ISO-8859-1?Q?Keld_J=F8rn_Simonsen?= <keld@dkuug.dk>
      CC: =?ISO-8859-1?Q?Andr=E9_?= Pirard <PIRARD@vm1.ulg.ac.be>
      Subject: =?ISO-8859-1?B?SWYgeW91IGNhbiByZWFkIHRoaXMgeW8=?=

which look really ugly here but are actually self-encoding in
a more or less useful way.

However, I'm not sure if we quite got the grammar right here;
i.e., I'm not sure if the "quoted-string" non-terminal is supposed
or allowed to follow the same encoding rules as the TEXT non-terminal.
Perhaps some language-lawyer can help out here.

That is, should we change this:
       Warning    = "Warning" ":" warn-code SP warn-agent SP warn-text
       warn-text  = quoted-string


       Warning    = "Warning" ":" warn-code SP warn-agent SP warn-text
       warn-text  = ( <"> *TEXT <"> )

Received on Tuesday, 14 May 1996 16:20:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC