From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Robert J. Chassell" Newsgroups: gmane.emacs.devel Subject: Re: Do you understand this? Date: Mon, 7 Mar 2005 23:46:52 +0000 (UTC) Message-ID: References: <87sm38jyhm.fsf@tapsellferrier.co.uk> <422C8B23.109@gnu.org> Reply-To: bob@rattlesnake.com NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1110240140 1064 80.91.229.2 (8 Mar 2005 00:02:20 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2005 00:02:20 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 08 01:02:19 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D8SAZ-0005eN-Tx for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2005 01:01:52 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D8SUR-0004y2-7D for ged-emacs-devel@m.gmane.org; Mon, 07 Mar 2005 19:22:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D8SRk-0003h4-9M for emacs-devel@gnu.org; Mon, 07 Mar 2005 19:19:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D8SRd-0003dw-6d for emacs-devel@gnu.org; Mon, 07 Mar 2005 19:19:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D8SRb-0003Gk-6z for emacs-devel@gnu.org; Mon, 07 Mar 2005 19:19:27 -0500 Original-Received: from [69.168.108.225] (helo=rattlesnake.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D8RwF-0005KZ-B2 for emacs-devel@gnu.org; Mon, 07 Mar 2005 18:47:03 -0500 Original-Received: by rattlesnake.com via sendmail from stdin id (Debian Smail3.2.0.115) Mon, 7 Mar 2005 23:46:52 +0000 (UTC) Original-To: emacs-devel@gnu.org In-reply-to: <422C8B23.109@gnu.org> (message from Jason Rumney on Mon, 07 Mar 2005 17:10:59 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34294 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34294 Jason Rumney rightly noted that In the Emacs manual, we need to explain how the user configures this in Emacs. Describing what RFC2616 says is not very useful ... Good point. How about putting the explanation in a comment in emacs/lisp/url/url-vars.el just after (defvar url-mime-accept-string nil "String to send to the server in the Accept: field in HTTP requests.") ? Or perhaps in the `Commentary:' section of emacs/lisp/url/url.el with some other remarks, too. (I do not know enough to have any idea what the `other remarks' should say.) Here is the explanation, slightly changed from before, in a format for an Emacs Lisp library. Please check this wording. I think it is a little clearer than before. ;; An `Accept:' or `Accept-Charset' statement, or a `headers' as it is ;; often called, allows you, a client, to specify the priority or ;; weighing of the type of statement you would like a server to ;; accept. ;; ;; In contrast to their precedence in English text, commas separate ;; _bigger_ groupings than semi-colons, which are used to prefix ;; weightings or priority values. Priority values go from 0.0 to 1.0, ;; with 1.0 being highest. When a priority or weighting value is not ;; listed the value is presumed to be 1.0. Moreover, an `Accept:' or ;; `Accept-Charset' list need not be in priority or precedence order. ;; ;; Thus, an accept statement such as ;; ;; Accept: text/plain; ;; q=0.5, text/html, text/x-dvi; ;; q=0.8, text/x-c ;; ;; could be reformatted as ;; ;; Accept: text/plain; q=0.5, ;; text/x-dvi; q=0.8, ;; text/html ; q=1.0, ;; text/x-c ; q=1.0 ;; ;; This latter expression shows the list in order from lower to higher ;; priority. Both `text/html' and `text/x-c' are of equal (and ;; highest) priority. ;; ;; When a client sends in an HTTP request for a resource, the above ;; `Accept:' statement tells the server that the user prefers either ;; an HTML or text/x-c document. If neither of those reprsentations ;; is available, then DVI is next preference. If none of those three ;; are available, then plain text should be sent. If neither plain ;; text, DVI, HTML nor x-c are available, then the server's response ;; should indicate that it is failing to find a representation that ;; satisfies the request. -- Robert J. Chassell bob@rattlesnake.com GnuPG Key ID: 004B4AC8 http://www.rattlesnake.com http://www.teak.cc