Strange coding bug.

Strange coding bug.

[Kai Großjohann]

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

Note the word "oeuvre" in Rolf's posting.  It displays properly with
the ligature.  I used Gnus to create a followup to Rolf's posting, and
in the followup, the word "oeuvre" is b0rked.

What's wrong?

kai
-- 
~/.signature: No such file or directory


[-- Attachment #2.1: Type: text/plain, Size: 2704 bytes --]

Subject: Topics
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="====-=-="

--====-=-=

Topics:
   Re: Umlautkodierung
   Re: Umlautkodierung


--====-=-=
Content-Type: message/rfc822

Date: 25 Jun 2001 08:54:30 GMT
From: rolf.krahl@gmx.net (Rolf Krahl)
Subject: Re: Umlautkodierung
Message-ID: <9h6u86$1lf$3@rotkraut.de>
References: <3B338B4D.4E40ED37@gmx.de>
    <9h07lt$blt4t$1@ID-4109.news.dfncis.de> <3B33B937.BC354E1F@gmx.de>
    <deathsquad.m3sngsw3u0.fsf@socha.net> <3B351444.D1774C09@gmx.de>
    <pl63h9.fl3.ln@ID-75191.user.dfncis.de>
    <9h6l7f$cgdr0$1@ID-65464.news.dfncis.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable

In Artikel <9h6l7f$cgdr0$1@id-65464.news.dfncis.de>
	schrieb Michael Dahms <michael.dahms@gkss.de>:
> Andreas Kneib =E4nderte die Umlautkodierung von "iso-8859-1" auf
> "charset=3Diso-8859-15"
>=20
> Moin Andreas, durch Deine IMHO un=FCbliche Kodierung ist bei mir im
> Subject "f=FCr" zu "f=B8r" geworden.
>=20
> Ist das ein Bug meines Netscape? Warum arbeitest Du mit der
> "-15"-Kodierung?

Das ist wohl ein Bug Deines Netscape.  In beiden Charsets, in
"iso-8859-1" und in "iso-8859-15" liegt das "=FC" auf der selben
Codeposition.  Das Netscape "iso-8859-15" nicht kennt, da kann er
nichts f=FCr.  Aber wie er dann darauf kommt, dann aus dem "=FC" (Zeichen
252) ein "=B8" (Zeichen 184) zu machen, das wird wohl sein Geheimnis
bleiben.

Warum Andreas "iso-8859-15" benutzt?  Keine Ahnung, vielleicht m=F6chte
er Worte wie "=BDuvre" (wie "oeuvre", aber mit oe-ligatur) korrekt
schreiben k=F6nnen.

--=20
		   Rolf Krahl <rolf.krahl@gmx.net>


--====-=-=
Content-Type: message/rfc822

Date: Mon, 25 Jun 2001 23:07:59 +0200
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=)
Subject: Re: Umlautkodierung
Message-ID: <vaflmmgfets.fsf@lucy.cs.uni-dortmund.de>
References: <3B338B4D.4E40ED37@gmx.de>
 <9h07lt$blt4t$1@ID-4109.news.dfncis.de> <3B33B937.BC354E1F@gmx.de>
 <deathsquad.m3sngsw3u0.fsf@socha.net> <3B351444.D1774C09@gmx.de>
 <pl63h9.fl3.ln@ID-75191.user.dfncis.de>
 <9h6l7f$cgdr0$1@ID-65464.news.dfncis.de> <9h6u86$1lf$3@rotkraut.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 25 Jun 2001, Rolf Krahl wrote:

> Warum Andreas "iso-8859-15" benutzt?  Keine Ahnung, vielleicht
> m=C3=B6chte er Worte wie "=C5=9E=D3=B5vre" (wie "oeuvre", aber mit oe-lig=
atur)
> korrekt schreiben k=C3=B6nnen.

Aber das geht doch auch mit iso-8859-1, oder nicht?  Ich dachte, *-1
und *-15 unterschieden sich nur an der Stelle f=C3=BCr das Euro-Zeichen.

kai
--=20
~/.signature: No such file or directory


--====-=-=--

Re: Strange coding bug.

[Kai Großjohann]

On Tue, 26 Jun 2001, Kai Großjohann wrote:

> Note the word "oeuvre" in Rolf's posting.  It displays properly with
> the ligature.  I used Gnus to create a followup to Rolf's posting,
> and in the followup, the word "oeuvre" is b0rked.
> 
> What's wrong?

I wonder, maybe Mule-UCS and the UCS support in Emacs 21 step on each
other's toes?

kai
-- 
~/.signature: No such file or directory

what's wrong with viewing multipart messages in current gnus? (was: Strange coding bug.)

[Vladimir Volovich]

Hi,

current version of gnus (from cvs) is badly broken in displaying some
multipart messages. in particular, the Kai Großjohann's article to
gnus-ding to which i reply now (with message-id
vaf8zifa1kk.fsf@lucy.cs.uni-dortmund.de and with subject "Strange
coding bug.") is displayed without any headers!

The text which i get in the beginning Article buffer is after the line
with "===...":

===================================================

What's wrong?

kai
-- 
~/.signature: No such file or directory

From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Newsgroups: gnus.ding
Subject: Strange coding bug.
Date: Tue, 26 Jun 2001 14:05:31 +0200
Organization: Gnus Information Center
Lines: 108
Approved: auto
Message-ID: <vaf8zifa1kk.fsf@lucy.cs.uni-dortmund.de>
NNTP-Posting-Host: quimby.gnus.org
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=-=-="
X-Trace: quimby.gnus.org 993594203 26964 195.204.10.139 (26 Jun 2001 22:23:23 GMT)
X-Complaints-To: usenet@quimby.gnus.org
NNTP-Posting-Date: 26 Jun 2001 22:23:23 GMT
To: Gnus Mailing List <ding@gnus.org>
Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1])
	by quimby.gnus.org (8.9.3/8.9.3) with ESMTP id AAA19136
	for <ding-moderator@quimby.gnus.org>; Wed, 27 Jun 2001 00:23:08 +0200 (CEST)
Original-Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.128.10])
	by karazm.math.uh.edu (8.9.3/8.9.3) with ESMTP id RAS16337;
	Tue, 26 Jun 2001 17:12:00 -0500 (CDT)
Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 26 Jun 2001 17:08:51 -0500 (CDT)
Original-Received: from sclp3.sclp.com (qmailr@sclp3.sclp.com [209.196.61.66])
	by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id RAA16548
	for <ding@hpc.uh.edu>; Tue, 26 Jun 2001 17:08:21 -0500 (CDT)
Original-Received: (qmail 11304 invoked by alias); 26 Jun 2001 22:08:44 -0000
Delivered-To: alias-ding@gnus.org
Original-Received: (qmail 4286 invoked from network); 26 Jun 2001 12:05:59 -0000
Original-Received: from waldorf.cs.uni-dortmund.de (129.217.4.42)
  by gnus.org with SMTP; 26 Jun 2001 12:05:59 -0000
Original-Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de  with ESMTP id OAA23338 for <ding@gnus.org>; Tue, 26 Jun 2001 14:05:32 +0200 (MES)
Original-Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160])
	by marcy.cs.uni-dortmund.de id OAA07721; Tue, 26 Jun 2001 14:05:31 +0200 (MET DST)
Original-Received: (from grossjoh@localhost)
	by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-21) id OAA15297;
	Tue, 26 Jun 2001 14:05:31 +0200
Original-Lines: 82
User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.104
Precedence: list
X-Majordomo: 1.94.jlt7
Xref: quimby.gnus.org gnus.ding:32933

--=-=-=

Note the word "oeuvre" in Rolf's posting.  It displays properly with
the ligature.  I used Gnus to create a followup to Rolf's posting, and
in the followup, the word "oeuvre" is b0rked.

What's wrong?

[rest skipped]

Re: what's wrong with viewing multipart messages in current gnus? (was: Strange coding bug.)

[Simon Josefsson]

Vladimir Volovich <vvv@vsu.ru> writes:

> current version of gnus (from cvs) is badly broken in displaying some
> multipart messages. in particular, the Kai Großjohann's article to
> gnus-ding to which i reply now (with message-id
> vaf8zifa1kk.fsf@lucy.cs.uni-dortmund.de and with subject "Strange
> coding bug.") is displayed without any headers!

This one also looked fine to me.  (Emacs 20.7) Are you sure some local
customization isn't causing the trouble?

> The text which i get in the beginning Article buffer is after the line
> with "===...":
> 
> ===================================================
> 
> What's wrong?

Maybe something MIME related is b0rked.  (I know, that statement kind
of nail it down to, say, only half the universe...)