Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Cc: ding@gnus.org
Subject: Re: Gnus coming with Emacs 21pre-release: iso-8859-{1,15}
Date: 27 Jul 2001 07:20:49 +0200	[thread overview]
Message-ID: <shvgkfne1a.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <sh8zhbot26.fsf@tux.gnu.franken.de>

Just found the old mail by Dave again; here's some more background info:

From: Dave Love <d.love@dl.ac.uk>
Subject: Re: Unicode/Mule (Re: null-device)
To: Karl Eichwalder <keichwa@gmx.net>
Cc: rms@gnu.org, eliz@is.elta.co.il, haible@ilog.fr,
	pinard@iro.umontreal.ca, emacs-devel@gnu.org, gerd@gnu.org
Date: 22 Jul 2001 19:17:38 +0100

[...]

 KE> The consequence is, Gnus often 

[I'd dispute ‘often’.]

 KE> thinks it has to create a multipart message...  

[Is that necessarily wrong?]

I'll eval into my message buffer

(string (make-char 'latin-iso8859-1 ?\xe9)
        (make-char 'latin-iso8859-14 ?\xe9)
        (make-char 'latin-iso8859-15 ?\xe9))
  => "ééé"

You may choose not to believe me that it results in a string with
three different Emacs characters and that Gnus will post this silently
in utf-8, but it's so.  I unify on encoding to utf-8 in what might as
well be a stock Emacs 21⁴.  For just the three ‘e’s, Latin-1 could
have been chosen.

What you normally see is not a consequence of Emacs forcing anything.
It can be customized.

 KE> Yes, it will only do so if you'll enter three 'y' (yes) in a row
 KE> -- this isn't "user-friendly" (Eli).

I made Gnus fixes in this general area (_not_ on the basis of bug
reports), at least some of which aren't installed.

Footnotes: 

[...]

⁴ I know Eli disagrees.

-- 
DOMINUS ILLUMINATIO MEA


-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.suse.de/~ke/                                  |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)


  reply	other threads:[~2001-07-27  5:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-27  5:10 Karl Eichwalder
2001-07-27  5:20 ` Karl Eichwalder [this message]
2001-07-27  8:45 ` Eli Zaretskii
2001-07-27 18:22   ` Karl Eichwalder
2001-07-27 19:18     ` Eli Zaretskii
2001-09-01 16:27     ` Dave Love
2001-09-01 16:30   ` Dave Love
2001-08-04 15:46 ` Florian Weimer
2001-08-04 16:54   ` Kai Großjohann
2001-08-04 17:15     ` Florian Weimer
2001-08-04 17:57       ` Kai Großjohann
2001-08-04 18:02       ` Eli Zaretskii
2001-08-04 18:44         ` Florian Weimer
2001-08-05  7:15           ` Eli Zaretskii
2001-09-01 16:29           ` Dave Love
2001-09-02 11:01             ` Eli Zaretskii
2001-09-02 11:39               ` Florian Weimer
2001-08-04 18:07   ` Eli Zaretskii
2001-08-04 19:11     ` Florian Weimer
2001-08-05  7:15       ` Eli Zaretskii
2001-09-01 16:28         ` Dave Love
2001-09-01 16:30   ` Dave Love
2001-09-01 16:26 ` Dave Love

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=shvgkfne1a.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    --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).