Gnus development mailing list
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.cygnus.argh.org>
Subject: Re: Making message/rfc822 boundaries visible
Date: 13 Oct 1999 07:56:10 +0200	[thread overview]
Message-ID: <87yad7ls79.fsf@deneb.cygnus.argh.org> (raw)
In-Reply-To: =?iso-8859-1?q?Fran=E7ois?= Pinard's message of "11 Oct 1999 14:58:45 -0400"

François Pinard <pinard@iro.umontreal.ca> writes:

> Gnus is meant to create as many parts as necessary, on the fly.  But
> sadly, I too get "Can't encode a part with several charsets." with
> the HELLO file.

The composed characters in Hindi and Lao cause the problems.  I thought
several charsets in one line would be required to encode this file
(which isn't true, but can be handled using UTF-8).

> It is true that in many cases, UTF-8 support would allow for a single
> MIME part for everything, indeed.  In other cases, UTF-8 would not convey
> distinctions that Asian do want to make,

The main problem with Unicode was that in the official manual, only
Chinese glyphs were printed, which extremly annoyed some Japanese people
(who, on the other hand, are used to write short Chinese citations in
Japanese text using the Japanese glyphs ;).



  reply	other threads:[~1999-10-13  5:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-10 21:57 Robert Bihlmeyer
1999-10-11 16:13 ` Jack Vinson
1999-10-10 19:40   ` François Pinard
1999-10-11 21:29     ` Kai Großjohann
1999-10-11 22:11     ` Jack Vinson
1999-10-12  9:53       ` Toby Speight
1999-11-06 21:48         ` Lars Magne Ingebrigtsen
1999-10-12 16:36       ` Florian Weimer
1999-10-11 18:58         ` François Pinard
1999-10-13  5:56           ` Florian Weimer [this message]
1999-10-13  9:46             ` Toby Speight
1999-10-13 14:37             ` François Pinard
1999-11-06 21:47       ` Lars Magne Ingebrigtsen
1999-10-12 10:50   ` Robert Bihlmeyer

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=87yad7ls79.fsf@deneb.cygnus.argh.org \
    --to=fw@deneb.cygnus.argh.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).