unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: emacs-devel@gnu.org
Subject: Re: smtpmail and ~/.authinfo
Date: Tue, 27 Sep 2011 21:33:37 +0900	[thread overview]
Message-ID: <8762ke2mhq.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <878vpauvm9.fsf@lifelogs.com>

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.



  reply	other threads:[~2011-09-27 12:33 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 10:26 smtpmail and ~/.authinfo Eli Zaretskii
2011-08-21  4:39 ` Lars Magne Ingebrigtsen
2011-08-21  6:12   ` Eli Zaretskii
2011-08-21 19:25     ` Lars Magne Ingebrigtsen
2011-08-21 19:59       ` Eli Zaretskii
2011-08-21 20:17         ` Lars Magne Ingebrigtsen
2011-08-22  5:35           ` Eli Zaretskii
2011-09-10 19:01             ` Lars Magne Ingebrigtsen
2011-09-25 12:33         ` Ted Zlatanov
2011-09-25 12:48           ` Eli Zaretskii
2011-09-25 13:21             ` Ted Zlatanov
2011-09-25 17:08               ` Eli Zaretskii
2011-09-26 14:41                 ` Ted Zlatanov
2011-09-26 16:18                   ` Eli Zaretskii
2011-09-26 16:53                     ` Ted Zlatanov
2011-09-26 17:15                       ` Eli Zaretskii
2011-09-26 17:23                         ` Eli Zaretskii
2011-09-26 17:31                         ` Ted Zlatanov
2011-09-26 17:00                     ` Stefan Monnier
2011-09-26 17:28                       ` Ted Zlatanov
2011-09-26 21:27                         ` Stefan Monnier
2011-09-26 18:04               ` Lars Magne Ingebrigtsen
2011-09-26 19:22                 ` Ted Zlatanov
2011-09-26 19:30                   ` Lars Magne Ingebrigtsen
2011-09-26 19:48                     ` Ted Zlatanov
2011-09-26 21:31                       ` Stefan Monnier
2011-09-26 21:43                         ` Lars Magne Ingebrigtsen
2011-09-26 21:54                           ` Ted Zlatanov
2011-09-27  4:07                           ` Stephen J. Turnbull
2011-09-27  6:11                             ` Lars Magne Ingebrigtsen
2011-09-27 10:29                             ` Ted Zlatanov
2011-09-27 12:33                               ` Stephen J. Turnbull [this message]
2011-09-27 20:15                                 ` Ted Zlatanov
2011-09-28  1:41                                   ` Stephen J. Turnbull
2011-09-28  8:38                                     ` Eli Zaretskii
2011-09-26 21:55                         ` Ted Zlatanov
2011-09-27  2:57                         ` Eli Zaretskii
2011-09-27 10:38                           ` Ted Zlatanov
2011-09-27 11:31                             ` Eli Zaretskii
2011-09-27 12:55                               ` Stefan Monnier
2011-09-27 14:02                             ` Jason Rumney
2011-09-26 19:34                   ` Eli Zaretskii
2011-09-26 19:40                     ` Ted Zlatanov
2011-09-27  2:51                       ` Eli Zaretskii
2011-09-27 13:54                   ` Jason Rumney

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=8762ke2mhq.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.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).