Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vvv.vsu.ru>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: MML: The Summation
Date: 18 Nov 1998 21:30:30 +0300	[thread overview]
Message-ID: <m3hfvwc0qh.fsf@vvv.vsu.ru> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Wed, 18 Nov 1998 11:36:38 -0500"

"EJS" == Edward J Sabol writes:


 >> I think that this is a BAD THING (TM) Gnus MUST NOT try to change
 >> the structure of a message if user did not asked this
 >> explicitly. For example, what should happen if one writes a mixed
 >> chinese-japanese-russian-norwegian text? In which each paragraph
 >> and each sentence contains quotes from all those languages (e.g. a
 >> multilingual dictionary). Gnus in no way should try to divide that
 >> message into parts.
 EJS> Why not? Seriously, I see nothing wrong with it. Please
 EJS> enlighten me as to why it is so horribly bad.

Just imagine how many parts will result from a mixed text of the form:

[word_in_chinese] [word_in_japanese] [word_in_russian] [word_in_norwegian]
[word_in_chinese] [word_in_japanese] [word_in_russian] [word_in_norwegian]
[word_in_chinese] [word_in_japanese] [word_in_russian] [word_in_norwegian]
[word_in_chinese] [word_in_japanese] [word_in_russian] [word_in_norwegian]
[word_in_chinese] [word_in_japanese] [word_in_russian] [word_in_norwegian]

;-) And would it be possible at all to reconstruct the original
message (recover from all those parts)? If the user did not explicitly
specify a part structure of a message, who can do this?

 EJS> There's no single charset that includes Chinese, Japanese,
 EJS> Russian, and Norwegian glyphs, is there? (I'm showing my
 EJS> international charset ignorance here. My apologies.)

Well, i'm also not sure whether MIME officially registered some of
Unicode encodings as allowable charsets for MIME parts, but if it is
so, then yes, there is a single charset which includes all those
languages, and much more. :-)

	Best regards, -- Vladimir.


  reply	other threads:[~1998-11-18 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-17 11:31 Lars Magne Ingebrigtsen
1998-11-17 15:18 ` Norman Walsh
1998-11-17 18:52 ` Matt Armstrong
1998-11-17 20:43 ` Edward J. Sabol
1998-11-17 22:52   ` Matt Armstrong
1998-11-18  0:45     ` Lars Magne Ingebrigtsen
1998-11-18  0:49   ` Lars Magne Ingebrigtsen
1998-11-18  9:55     ` Graham Murray
1998-11-18 10:04       ` Kai.Grossjohann
1998-11-20 14:59         ` George J McNinch
1998-11-20 15:31           ` Kai.Grossjohann
1998-11-18 11:14     ` Vladimir Volovich
1998-11-18 13:15       ` Lars Magne Ingebrigtsen
1998-11-18 18:21         ` Vladimir Volovich
1998-11-18 16:36       ` Edward J. Sabol
1998-11-18 18:30         ` Vladimir Volovich [this message]
1998-11-18 20:29           ` Raja R Harinath
1998-11-19  2:54           ` Lars Magne Ingebrigtsen
1998-11-19  5:53             ` Norbert Koch
1998-11-18 15:50     ` Edward J. Sabol
1998-11-18 18:23       ` Vladimir Volovich
1998-11-19  2:46       ` Lars Magne Ingebrigtsen

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=m3hfvwc0qh.fsf@vvv.vsu.ru \
    --to=vvv@vvv.vsu.ru \
    --cc=ding@gnus.org \
    /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).