Gnus development mailing list
 help / color / mirror / Atom feed
From: Ivan Shmakov <ivan@theory.asu.ru>
To: ding@gnus.org
Cc: Ivan Shmakov <oneingray@gmail.com>
Subject: Re: rfc2045-encode-string: should signal an error on non-ASCII strings
Date: Sat, 12 Jan 2008 00:07:49 +0600	[thread overview]
Message-ID: <m2prw8jkwa.fsf@cherry.siamics.int> (raw)
In-Reply-To: <b4mabnfsyuc.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 09 Jan 2008 08:04:59 +0900")

>>>>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>> Ivan Shmakov wrote:

 >> Shouldn't `rfc2045-encode-string' signal an error in case either
 >> PARAM or VALUE contain non-ASCII characters?

 > Gnus doesn't use `rfc2045-encode-string' for non-ASCII characters.  I
 > didn't find no Lisp module that uses it for non-ASCII characters in
 > the Emacs trunk either.

	Yes.  Indeed, it was my old Emacs 21.4.1 to use it that way and
	produce the MIME output damaged quite badly as a consequence.

	However, shouldn't the error be signalled, so that some useful
	diagnostics be shown instead of producing garbage on output (on
	this certain garbage on input)?  I guess, it's quite likely this
	library may get used by some other, not necessarily correct,
	code.

	(A wishlist priority item.)




      reply	other threads:[~2008-01-11 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08  9:49 Ivan Shmakov
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 [this message]

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=m2prw8jkwa.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).