From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>,
galex-713@galex-713.eu, emacs-devel@gnu.org
Subject: Re: smtpmail support of unicode passwords
Date: Mon, 14 Apr 2014 21:14:50 +0900 [thread overview]
Message-ID: <871tx0glad.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <83ha5wl5iw.fsf@gnu.org>
Eli Zaretskii writes:
> My reading if the relevant RFCs is that UTF-8 must be used, but I'm no
> expert in this area.
By relevant RFCs I assume you mean RFC 4616 (aka SASL "PLAIN")?
Indeed, the receiving server is going to expect that the string is
valid UTF-8. That doesn't necessarily mean that Emacs has the string
as characters in internal encoding, appropriate to be encoded via the
utf-8 coding system before being sent on the wire. It might also have
it as bytes read from a file using the binary codec (the main use case
I'm worried about), or the user may have learned to type it that way,
etc.
Of course if you know you have a string decoded using binary, you can
translate it using utf-8 before sending it back through utf-8 and then
onto the wire.
I guess it's actually quite likely that the binary file contains
Latin-N or some form of Cyrillic, etc, so if needed the decode-encode
cycle is probably the way to go. So you may as well hard-code utf-8
here after all.
next prev parent reply other threads:[~2014-04-14 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 18:27 smtpmail support of unicode passwords Garreau, Alexandre
2014-04-13 19:11 ` Eli Zaretskii
2014-04-14 1:18 ` Stefan Monnier
2014-04-14 5:50 ` Stephen J. Turnbull
2014-04-14 8:18 ` Eli Zaretskii
2014-04-14 7:44 ` Eli Zaretskii
2014-04-14 12:14 ` Stephen J. Turnbull [this message]
2014-04-14 12:27 ` Eli Zaretskii
2014-04-14 12:55 ` Stefan Monnier
2014-04-14 14:57 ` Harald Hanche-Olsen
2014-04-14 15:36 ` Eli Zaretskii
2014-04-14 16:55 ` Harald Hanche-Olsen
2014-04-14 18:03 ` Stephen J. Turnbull
2014-04-14 21:01 ` Eli Zaretskii
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=871tx0glad.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=galex-713@galex-713.eu \
--cc=monnier@IRO.UMontreal.CA \
/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.