Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Charset encoding brokenness
Date: Fri, 31 Oct 2003 17:29:24 +0100	[thread overview]
Message-ID: <iluekwtl6aj.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m37k2q5p1b.fsf@defun.localdomain> (Jesper Harder's message of "Mon, 27 Oct 2003 22:49:52 +0100")

Jesper Harder <harder@ifa.au.dk> writes:

> Charset encoding is currently broken in quite a few places, viz.
>
> · Forwarding.  `C-u N C-c C-f' for N=1,2,4 is broken if the CTE of
>   the forwarded message is 8bit.

I believe I fixed N=1 before, but cannot find any problem with N=4?  I
can reproduce the problem with N=2 though, and it could be worked
around by using

<#part type=message/rfc822 disposition=inline raw=t buffer=" *Original Article*">
<#/part>

although one has to be careful so the buffer isn't modified between
when you press C-c C-f and when you post the message.  So it should
create a new buffer and copy gnus-original-article-buffer there,
instead of referncing g-o-a-b directly.  Perhaps that buffer even
should be marked read-only, because if you add a some non-ASCII text
you will likely break the message, since it is not MIME encoded, which
novices might not realize (and experts know how to disable the
read-only flag).  What do you think?

I tested using <ilur80tmlcq.fsf@latte.josefsson.org> in gnus.test.




  parent reply	other threads:[~2003-10-31 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 21:49 Jesper Harder
2003-10-28  0:48 ` Simon Josefsson
2003-10-28  1:42   ` Jesper Harder
2003-10-28  3:01     ` Jesper Harder
2003-10-28  7:07       ` Vasily Korytov
2003-10-28 16:41         ` Jesper Harder
2003-10-29  7:03           ` Vasily Korytov
2003-10-29 12:39             ` Vasily Korytov
2003-10-29 21:22             ` Simon Josefsson
2003-10-29 21:30       ` Simon Josefsson
2003-10-29 21:17     ` Simon Josefsson
2003-10-31 16:29 ` Simon Josefsson [this message]
2003-10-31 22:23   ` Jesper Harder

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=iluekwtl6aj.fsf@latte.josefsson.org \
    --to=jas@extundo.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).