From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.help Subject: Re: Very basic question regarding encoding and `open-network-stream' Date: Tue, 27 Nov 2018 18:17:43 -0500 Message-ID: References: <87efb65hn0.fsf@ericabrahamsen.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1543360746 23062 195.159.176.226 (27 Nov 2018 23:19:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 27 Nov 2018 23:19:06 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Nov 28 00:19:02 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gRmdB-0005pF-TX for geh-help-gnu-emacs@m.gmane.org; Wed, 28 Nov 2018 00:19:02 +0100 Original-Received: from localhost ([::1]:44998 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRmfI-0001hR-H6 for geh-help-gnu-emacs@m.gmane.org; Tue, 27 Nov 2018 18:21:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49961) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRmc7-000795-Te for help-gnu-emacs@gnu.org; Tue, 27 Nov 2018 18:17:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRmc3-0001tX-BW for help-gnu-emacs@gnu.org; Tue, 27 Nov 2018 18:17:55 -0500 Original-Received: from [195.159.176.226] (port=60660 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gRmc3-0001sc-3r for help-gnu-emacs@gnu.org; Tue, 27 Nov 2018 18:17:51 -0500 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1gRmZu-0001od-BX for help-gnu-emacs@gnu.org; Wed, 28 Nov 2018 00:15:38 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 16 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:qbvCuoMrCurZGSeomuTl5WW5Ryo= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118778 Archived-At: > The NNTP RFC notes that the default character set for the protocol has > changed from ascii to utf-8. > (https://tools.ietf.org/html/rfc3977#section-1) > > What I don't grasp is: if the process buffers are left multibyte, and > the `coding-system-for-read/write' variables are changed to 'utf-8 (or > 'undecided?), will this simply do the right thing? No: the stream of bytes includes NNTP protocol commands as well as other contents (typically actual messages) and they don't all use utf-8. So the stream process needs to communicate in bytes (aka "unibyte"), and then the Elisp code needs to decode/encode each part manually according to the coding system that applies to each part. Stefan