From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Do you understand this?
Date: Mon, 07 Mar 2005 17:10:59 +0000 [thread overview]
Message-ID: <422C8B23.109@gnu.org> (raw)
In-Reply-To: <m1D8KIi-0004RGC@rattlesnake.com>
Robert J. Chassell wrote:
>Thanks to Andreas, Jason, and Nic I think I now understand the rfc2616
>HTTP specification a great deal better than before.
>
>Perhaps we should add the following to
>
> emacs/man/url.texi
>
>after the text saying:
>
> @node HTTP language/coding
> @subsection Language and Encoding Preferences
>
> HTTP allows clients to express preferences for the language and
> encoding of documents which servers may honour.
>
>Is this now an accurate description?
>
>
Yes.
>An @samp{Accept:} or @samp{Accept-Charset} statement or @samp{headers}
>allows you to specify the priority or weighing of the type of
>statement you would like to accept.
>
>
>
In the Emacs manual, we need to explain how the user configures this in
Emacs. Describing what RFC2616 says is not very useful if url provides a
higher level interface for configuring language preferences. If the
Emacs interface is simply providing a list of HTTP request headers, then
we need to say that, or the user will think that these two headers are
the only two they can configure.
next prev parent reply other threads:[~2005-03-07 17:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 19:11 Do you understand this? Richard Stallman
2005-03-06 20:44 ` Nic Ferrier
2005-03-06 22:32 ` Robert J. Chassell
2005-03-06 22:58 ` Andreas Schwab
2005-03-06 23:05 ` Jason Rumney
2005-03-07 15:37 ` Robert J. Chassell
2005-03-07 17:10 ` Jason Rumney [this message]
2005-03-07 23:46 ` Robert J. Chassell
2005-03-08 0:34 ` Nic Ferrier
2005-03-08 18:41 ` Robert J. Chassell
2005-03-09 16:58 ` Richard Stallman
2005-03-06 23:12 ` Nic Ferrier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=422C8B23.109@gnu.org \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).