Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Using iso-8859-15 with Emacs21 & Gnus
Date: Thu, 01 Nov 2001 18:30:35 -0500	[thread overview]
Message-ID: <2n7ktaul0k.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <87u1wexktw.fsf@deneb.enyo.de> (Florian Weimer's message of "Thu, 01 Nov 2001 22:06:19 +0100")

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

Florian Weimer <fw@deneb.enyo.de> writes:

> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>
>>> Anyway, the current behavior of CVS Gnus + Emacs 21 is not acceptable.
>>> How shall we fix it?  Unify latin-iso8859-1 and latin-iso8859-15
>>> character sets?  Extend the iso-latin-1 and iso-latin-9 coding systems
>>> so that they can encode part of the other charset?  Extend the UTF-8
>>> charset, to make it encode latin-iso8859-15 as well?
>>
>> I've put some code into the Gnus CVS to handle this issue.  Please
>> try. 
>
> It doesn't work, I'm afraid.  For example, ISO-8859-1 '¼' is changed

[-- Attachment #2: Type: text/plain, Size: 69 bytes --]

> to ISO-8859-15 'Œ', which is clearly wrong.

Fixed.

ShengHuo

  reply	other threads:[~2001-11-01 23:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27 21:50 Raymond Scholz
2001-10-27 22:51 ` Florian Weimer
2001-10-28 13:12   ` Raymond Scholz
2001-11-01 11:26     ` Florian Weimer
2001-11-01 14:37       ` ShengHuo ZHU
2001-11-01 21:06         ` Florian Weimer
2001-11-01 23:30           ` ShengHuo ZHU [this message]
2001-11-02 19:36             ` Florian Weimer
2001-11-02 22:36               ` ShengHuo ZHU
2001-11-03 10:37                 ` Florian Weimer
2001-11-03 14:53                   ` ShengHuo ZHU
2001-11-03 16:36                     ` Kai Großjohann
2001-11-03 18:29                       ` Graham Murray
2001-11-03 20:28                         ` Florian Weimer
2001-11-03 20:28                           ` Per Abrahamsen
2001-11-03 20:38                             ` Russ Allbery
2001-11-03 21:11                               ` USEFOR (was: Re: Using iso-8859-15 with Emacs21 & Gnus) Per Abrahamsen
2001-11-03 21:34                                 ` Russ Allbery
2001-11-03 22:01                                 ` USEFOR Florian Weimer
2001-11-05 10:46                                   ` USEFOR Per Abrahamsen
2001-11-03 21:57                             ` Using iso-8859-15 with Emacs21 & Gnus Florian Weimer
2001-11-03 22:09                               ` Russ Allbery
2001-11-04  0:56                                 ` Florian Weimer
2001-11-04 10:31                                   ` Russ Allbery
2001-11-04 18:29                           ` Kai Großjohann
2001-11-04 23:27                             ` Florian Weimer
2001-11-04 18:24                         ` Kai Großjohann
2001-11-03 19:57                     ` Karl Eichwalder
2001-11-03 12:54                 ` Per Abrahamsen
2001-11-03 23:31                   ` Paul Jarc
2001-11-01 21:14         ` Raymond Scholz
2001-11-01 22:26           ` Florian Weimer
2001-11-01 17:51       ` news
2001-11-01 21:06         ` Florian Weimer

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=2n7ktaul0k.fsf@zsh.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).