From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: Re: Automatic part insertion: åäö and 吃哪塞 on the same line
Date: 02 Dec 1998 22:41:07 +0300 [thread overview]
Message-ID: <m367bubacs.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "02 Dec 1998 20:12:57 +0100"
"LMI" == Lars Magne Ingebrigtsen writes:
LMI> Quoth RFC2046:
thanks. gnus now supports empty lines in mime almost fine, but it
seems to be a bit more `aggressive' in:
* ignoring empty lines in MIME parts when displaying. e.g the message
which started this thread contained in the last part:
> --==-=-=
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: 8bit
>
>
>
> Couldn't this be quickly scanned to have #part's automatically added?
> I.e. one starts out with the group default coding and then goes
i.e., as i understand, gnus should have leaved two empty lines before
the last paragraph when displaying the message, but it showed only one
empty line.
* putting some extra empty lines in MIME when composing
messages. E.g. if i create a text/plain us-ascii part, gnus puts two
or three empty lines after part boundary, instead of just one.
LMI> I don't really know about this one. If I'm composing a message
LMI> using Scandianvian and Sami characters (which would be
LMI> iso-8859-1 and iso-8859-9 if I'm responsing to someone using
LMI> iso-8859-9,) I want to respons using iso-8859-9 and iso-8859-1,
LMI> not Unicode, no matter whether Emacs supports it or not. What's
LMI> important is what the recipient supports, and one can't assume
LMI> that the recipient supports these megacharsets.
LMI> MIME is widely implemented, if (ahum) slightly shakily here and
LMI> there. Unicode is not. So it's better to Mimetilate a message
LMI> than to Unicodelate the messege.
Well, maybe, gnus should decide how to behave in these situations
based on the mm-mime-mule-charset-alist? i.e., you can just remove
unicode line from that list (if it were there), but someone else would
want to leave it there? So, gnus should _first_ look in the
mm-mime-mule-charset-alist, and try to encode the whole part with a
single charset, and _if_ it could not find a single charset, only then
it should try to insert automagical parts?
Best regards, -- Vladimir.
next prev parent reply other threads:[~1998-12-02 19:41 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6f67buzzff.fsf@dna.lth.se>
1998-12-02 9:41 ` Lars Magne Ingebrigtsen
1998-12-02 10:00 ` Russ Allbery
1998-12-02 12:49 ` Kurt Swanson
1998-12-02 17:19 ` Automatic part insertion: åäö and ÔÄû " François Pinard
1998-12-02 17:30 ` Hrvoje Niksic
1998-12-02 17:55 ` Richard Coleman
1998-12-03 8:53 ` Automatic part insertion: åao and ÔAû " Jari Aalto+list.ding
1998-12-02 18:02 ` Automatic part insertion: åäö and 吃哪塞 " Lars Magne Ingebrigtsen
1998-12-02 19:32 ` Lars Magne Ingebrigtsen
1998-12-02 10:27 ` Matt Armstrong
1998-12-02 18:03 ` Lars Magne Ingebrigtsen
1998-12-02 19:12 ` Lars Magne Ingebrigtsen
1998-12-02 20:39 ` Simon Josefsson
[not found] ` <6fyaopd2dz.fsf@dna.lth.se>
1998-12-03 18:39 ` Simon Josefsson
1998-12-02 16:59 ` Hrvoje Niksic
1998-12-02 22:19 ` Karl Kleinpaste
1998-12-02 22:40 ` Hrvoje Niksic
1998-12-02 23:07 ` Lars Magne Ingebrigtsen
1999-02-13 2:17 ` Neil Crellin
1999-02-13 6:00 ` Dmitry Yaitskov
1999-02-13 12:59 ` Kai.Grossjohann
1999-02-19 13:58 ` Lars Magne Ingebrigtsen
1999-02-19 17:04 ` Neil Crellin
1998-12-03 0:10 ` Kai.Grossjohann
1998-12-03 6:38 ` Graham Murray
1998-12-03 10:46 ` Kai.Grossjohann
1998-12-03 11:50 ` Lars Magne Ingebrigtsen
1998-12-02 12:39 ` Vladimir Volovich
1998-12-02 17:38 ` Shenghuo ZHU
1998-12-02 18:34 ` Vladimir Volovich
1998-12-02 18:59 ` Shenghuo ZHU
1998-12-02 19:43 ` Lars Magne Ingebrigtsen
1998-12-02 23:34 ` Info on Internationalization Richard Coleman
1998-12-03 0:05 ` Lars Magne Ingebrigtsen
1998-12-03 0:17 ` Shenghuo ZHU
1998-12-03 11:39 ` Lars Magne Ingebrigtsen
1998-12-03 16:49 ` Shenghuo ZHU
1998-12-03 0:27 ` Richard Coleman
1998-12-06 14:11 ` François Pinard
1998-12-03 0:06 ` Shenghuo ZHU
1998-12-03 0:12 ` Hrvoje Niksic
1998-12-03 11:38 ` Lars Magne Ingebrigtsen
1998-12-03 13:18 ` Hrvoje Niksic
1998-12-03 16:39 ` Shenghuo ZHU
1998-12-03 16:38 ` Shenghuo ZHU
1998-12-04 1:15 ` Lars Magne Ingebrigtsen
1998-12-04 7:10 ` Shenghuo ZHU
1998-12-02 21:19 ` Automatic part insertion: åäö and 吃哪塞 on the same line Vladimir Volovich
1998-12-02 21:37 ` Shenghuo ZHU
1998-12-02 22:18 ` Vladimir Volovich
1998-12-02 23:29 ` Lars Magne Ingebrigtsen
1998-12-02 17:50 ` Hrvoje Niksic
1998-12-02 18:19 ` Lars Magne Ingebrigtsen
1998-12-02 19:12 ` Lars Magne Ingebrigtsen
1998-12-02 19:41 ` Vladimir Volovich [this message]
1998-12-02 21:34 ` Hrvoje Niksic
1998-12-02 22:29 ` Lars Magne Ingebrigtsen
1998-12-04 8:31 ` Vladimir Volovich
1998-12-02 21:33 ` Hrvoje Niksic
1998-12-02 16:26 ` Michael Harnois
1998-12-02 17:02 ` Michael Harnois
1998-11-14 15:30 Scriptin' MIME Lars Magne Ingebrigtsen
1998-11-14 18:07 ` Bruce Stephens
1998-11-14 18:27 ` Lars Magne Ingebrigtsen
1998-11-14 18:38 ` Bruce Stephens
1998-11-14 20:48 ` Richard Coleman
1998-11-14 19:55 ` Hrvoje Niksic
1998-11-14 20:45 ` Lars Magne Ingebrigtsen
1998-11-14 20:45 ` Hrvoje Niksic
1998-11-14 18:29 ` Andi Kleen
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=m367bubacs.fsf@vvv.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).