From: Adam Porter <adam@alphapapa.net>
To: tomas@tuxteam.de
Cc: Joseph Turner <joseph@ushin.org>, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, schwab@suse.de
Subject: Re: How to get buffer byte length (not number of characters)?
Date: Fri, 23 Aug 2024 01:28:19 -0500 [thread overview]
Message-ID: <3af7761b-a24a-47cd-9083-5f7795bdd971@alphapapa.net> (raw)
In-Reply-To: <ZsczR5Md5Lj3SvAW@tuxteam.de>
On 8/22/24 07:47, tomas@tuxteam.de wrote:
> Another point I haven't seen in this discussion is that HTTP also may
> carry metadata about what it thinks the content encoding is. This may
> involve the server configuration too.
>
> You may choose to ignore it, but then you need to convince all the
> moving parts to agree on that (i.e. an Apache on the other side might
> happily tell your client that it is sending "text/plain; charset=UTF-8"
> or something similarly funny (note: UTF-8 isn't a charset :-) depending
> on the web server config, the content of some mimetype database and
> so on.
>
> You'll have to make sure curl and Emacs do the right thing with that
> (which might be "nothing").
plz optionally decodes response bodies according to the content-type
header, depending on the :decode argument (although Joseph found a bug
in the implementation of that, and I'll merge his fix soon). plz does
not do anything else, e.g. setting a buffer's coding system variables.
If :decode is nil, plz does no decoding and leaves it to the user.
For HTML, with its potential for having a META tag that may also specify
encoding, that would be up to the user; plz offers no special support
for various content types.
If a user wants to handle these issues manually, the ":as 'response"
argument to plz should be used, which allows the user to process the
response headers and body directly.
next prev parent reply other threads:[~2024-08-23 6:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 7:10 How to get buffer byte length (not number of characters)? Joseph Turner
2024-08-20 7:51 ` Joseph Turner
2024-08-20 11:20 ` Eli Zaretskii
2024-08-20 11:15 ` Eli Zaretskii
2024-08-21 9:20 ` Joseph Turner
2024-08-21 17:47 ` Eli Zaretskii
2024-08-21 23:52 ` Joseph Turner
2024-08-22 4:06 ` Eli Zaretskii
2024-08-22 7:24 ` Joseph Turner
2024-08-22 11:04 ` Eli Zaretskii
2024-08-22 18:29 ` Joseph Turner
2024-08-22 18:44 ` Eli Zaretskii
2024-08-22 19:32 ` tomas
2024-08-23 3:56 ` Joseph Turner
2024-08-23 7:02 ` Eli Zaretskii
2024-08-23 7:37 ` Joseph Turner
2024-08-23 12:34 ` Eli Zaretskii
2024-08-23 7:43 ` Joseph Turner
2024-08-23 12:38 ` Eli Zaretskii
2024-08-23 16:59 ` Joseph Turner
2024-08-23 17:35 ` Eli Zaretskii
2024-08-23 20:37 ` Joseph Turner
2024-08-24 6:14 ` Joseph Turner
2024-08-22 12:26 ` Adam Porter
2024-08-22 12:47 ` tomas
2024-08-23 6:28 ` Adam Porter [this message]
2024-08-22 13:50 ` Eli Zaretskii
2024-08-23 6:31 ` Adam Porter
2024-08-23 6:51 ` Eli Zaretskii
2024-08-23 7:07 ` Joseph Turner
2024-08-23 7:58 ` Joseph Turner
2024-08-22 7:09 ` Andreas Schwab
2024-08-22 7:30 ` Joseph Turner
2024-08-22 11:05 ` Eli Zaretskii
2024-08-26 6:37 ` Joseph Turner
2024-08-26 6:49 ` Joseph Turner
2024-08-26 11:22 ` Eli Zaretskii
2024-08-27 4:48 ` Joseph Turner
2024-08-26 11:20 ` Eli Zaretskii
2024-08-20 11:24 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3af7761b-a24a-47cd-9083-5f7795bdd971@alphapapa.net \
--to=adam@alphapapa.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joseph@ushin.org \
--cc=schwab@suse.de \
--cc=tomas@tuxteam.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.