From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel Subject: Re: smtpmail and ~/.authinfo Date: Tue, 27 Sep 2011 21:33:37 +0900 Message-ID: <8762ke2mhq.fsf@uwakimon.sk.tsukuba.ac.jp> References: <83ippsqsz8.fsf@gnu.org> <83hb5ay1rs.fsf@gnu.org> <87litc7qen.fsf@lifelogs.com> <87pqio69lr.fsf@lifelogs.com> <87vcsf1537.fsf@lifelogs.com> <8739fj13vb.fsf@lifelogs.com> <87bou639wx.fsf@uwakimon.sk.tsukuba.ac.jp> <878vpauvm9.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1317126843 20039 80.91.229.12 (27 Sep 2011 12:34:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 27 Sep 2011 12:34:03 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Sep 27 14:33:54 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1R8WrC-0007Qi-8g for ged-emacs-devel@m.gmane.org; Tue, 27 Sep 2011 14:33:54 +0200 Original-Received: from localhost ([::1]:55588 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8WrB-0004lX-OF for ged-emacs-devel@m.gmane.org; Tue, 27 Sep 2011 08:33:53 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:49581) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8Wr5-0004lF-41 for emacs-devel@gnu.org; Tue, 27 Sep 2011 08:33:52 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R8Wr0-00043y-Sc for emacs-devel@gnu.org; Tue, 27 Sep 2011 08:33:47 -0400 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:51167) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R8Wr0-000429-DE for emacs-devel@gnu.org; Tue, 27 Sep 2011 08:33:42 -0400 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id A4C289707B1 for ; Tue, 27 Sep 2011 21:33:37 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 9EC2A1A26F7; Tue, 27 Sep 2011 21:33:37 +0900 (JST) In-Reply-To: <878vpauvm9.fsf@lifelogs.com> X-Mailer: VM 8.2.0a1 under 21.5 (beta31) "ginger" 6c76f5b7e2e3 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.158.97.224 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:144403 Archived-At: Ted Zlatanov writes: > UTF-8 is an encoding; you're talking about charsets. No, I'm talking about encodings. I'm not entirely sure about GB 2312, but I believe it has a defined preferred encoding (the one registered as the MIME charset GB2312 -- MIME charsets are all encodings, they specify what *bytes* will appear in the stream, not just an abstract character to abstract integer mapping). Shift JIS is most definitely an encoding for the JIS character set (although which JIS character set is poorly defined). > Can you explain more precisely what you mean by "not UTF-8-ey in > several ways"? In the case of Shift JIS, I already did: octets in the ASCII range are used in multibyte characters. That *never* happens in valid UTF-8. The distinctions for GB2312 are more nebulous. But Lars meant something different, so it's not relevent. > Would it be enough to let the user override that coding system choice > through a defcustom? No. That requires a huge amount of user sophistication, and is too global; different applications might very well use different coding systems for non-ASCII characters. > For all the use cases I have seen, UTF-8 is enough, so I'd rather > use it by default. Isn't that what I said? > SJT> If you already have a password, it should be read verbatim (binary, or > SJT> raw-text should do given the line-oriented nature of these > SJT> configuration files) and treated as a binary blob. > > That's not helpful when you need to encode it for IMAP, for instance. > You have to know the actual characters that make up the binary blob. Since when? I haven't paid much attention to IMAP since RFC 3501 was an internet-draft, but in that document there are a few commands that accept a CHARSET parameter. LOGIN and AUTHENTICATE aren't among them. So you're just passing along binary blobs, which in the case of LOGIN will often look like somebody's birthday or a child's name, but that's just an unfortunate accident.