Gnus development mailing list
 help / color / mirror / Atom feed
From: Jorgen Schaefer <forcer@forcix.cx>
Subject: Re: locale ISO-8859-15, UTF-8 and mail...
Date: 18 Jul 2002 22:56:06 +0200	[thread overview]
Message-ID: <hhadoo7o2h.fsf@forcix.burse.uni-hamburg.de> (raw)
In-Reply-To: <87bs94vk9w.fsf@tzone.org>

fabien@tzone.org (Fabien Niñoles) writes:

>>> Something like "élève" will go out has "?l?ve", and, if I "C-u
>>> W M c latin-9", it will be "\201él\201ève".  Just watching it
>>> with "W M c", only add \201 before all `?'.  I'm looking for
>>> adding a command that simple (gnus-article-decode-charset nil
>>> 'latin-9) and remove all \201, but I will frankly prefer 
>>> make it works correctly.

I don't know wether this helps, but I have a default setup of
latin-1, and have the same problem viewing latin-9 messages.

In Message-ID: <0acc5b761e7260decdcdbcb5869bcce6@fitug.de>, both
W M c and C-u W M c latin-1 convert "n?herungsweise" to
"n\216äherungsweise".

> 2- I isolate the other bug (the \201 or \216 character add
> before every high-bit set character in multibyte environment) to
> a bug in the coding-system. To test it just evaluate this:
> 
> (decode-coding-string "élève" 'iso-8859-1) => "\216él\216ève" in latin-1 environment.

This gives "\201él\201ève" here, on an emacs 21.2.1 right from
Debian unstable.

HTH,
        -- Jorgen

-- 
((email . "forcer@forcix.cx") (www . "http://www.forcix.cx/")
 (gpg   . "1024D/028AF63C")   (irc . "nick forcer on IRCnet"))



  reply	other threads:[~2002-07-18 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 18:01 Fabien Niñoles
2002-07-18 11:41 ` Kai Großjohann
2002-07-18 16:12   ` Fabien Niñoles
     [not found]   ` <878z49dnk3.fsf@tzone.org>
     [not found]     ` <vaf4rew25r4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
2002-07-18 20:44       ` Fabien Niñoles
2002-07-18 20:56         ` Jorgen Schaefer [this message]
2002-07-19  7:19         ` Kai Großjohann

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=hhadoo7o2h.fsf@forcix.burse.uni-hamburg.de \
    --to=forcer@forcix.cx \
    /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).