From: Ivan Shmakov <ivan@theory.asu.ru>
To: ding@gnus.org
Cc: Ivan Shmakov <oneingray@gmail.com>
Subject: rfc2045-encode-string: should signal an error on non-ASCII strings
Date: Tue, 08 Jan 2008 15:49:51 +0600 [thread overview]
Message-ID: <m2myrgr6io.fsf@cherry.siamics.int> (raw)
Shouldn't `rfc2045-encode-string' signal an error in case either
PARAM or VALUE contain non-ASCII characters?
BTW, [1] specifies CVS as the mean of obtaining the development
sources for Gnus. However, looking at [2] makes me think that
it's GNU Arch that is used to hold the sources nowadays. Can
the appropriate GNU Arch archive be mentioned on [1] as well?
[1] http://gnus.org/distribution.html
[2] http://quimby.gnus.org/cgi-bin/cvsweb.cgi/gnus/lisp/rfc2045.el?rev=7.8&content-type=text/x-cvsweb-markup
next reply other threads:[~2008-01-08 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 9:49 Ivan Shmakov [this message]
2008-01-08 22:05 ` Miles Bader
2008-01-11 18:01 ` Ivan Shmakov
2008-01-11 18:28 ` Arch repository for Gnus (was: rfc2045-encode-string: should signal an error on non-ASCII strings) Reiner Steib
2008-01-08 23:04 ` rfc2045-encode-string: should signal an error on non-ASCII strings Katsumi Yamaoka
2008-01-11 18:07 ` Ivan Shmakov
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=m2myrgr6io.fsf@cherry.siamics.int \
--to=ivan@theory.asu.ru \
--cc=ding@gnus.org \
--cc=oneingray@gmail.com \
/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.
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 NNTP newsgroup(s).