Gnus development mailing list
 help / color / mirror / Atom feed
From: "Toby Speight" <streapadair@gmx.net>
Subject: Re: UTF-8 reading broken?
Date: 27 Mar 2001 19:43:24 +0100	[thread overview]
Message-ID: <s84rwf833n.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: jakub@martynski.pl's message of "26 Mar 2001 19:08:20 +0200"

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

0> In <URL:news:m3d7b47917.fsf@wazabi.tpi.pl>,
0> Jakub Marty <URL:mailto:jakub@martynski.pl> ("Jakub") wrote:

Jakub> I have another question: i want make "iso-8859-2" default
Jakub> coding for my posts and mails, but when i reply to "utf-8" i
Jakub> got charset "utf-8" in my headers (like in that post). How set
Jakub> recoding all "utf-8" posts to iso-8859-2 in Gnus?

I think this is a side-effect of how MULE works - it doesn't really
understand that a "á" character (for example) is in Latin-2 as well as
Latin-1, so when it reads "á", it puts a Latin-1 "á" in the message,
rather than a Latin-2 "á"[*].  If you quote this, and add some text of
your own with a Latin-2 "á" (or if the quote contains a character like
"ń" which isn't in Latin-1), then Mule thinks you've mixed two different
encodings.  That's why it uses UTF-8.

The fix isn't easy - though it may be possible to patch mule-ucs to
prefer Latin-2 encoding when reading.  I wouldn't know how to do this,
unfortunately.

[*] I've distinguished the two characters during composition, but this
    will be sent as UTF-8, so you won't be able tell them apart.
    Perhaps if I divide the message by hand, they'll get coded
    seperately:



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

> I think this is a side-effect of how MULE works - it doesn't really
> understand that a "á" character (for example) is in Latin-2 as well as
> Latin-1, so when it reads "á", it puts a Latin-1 "á" in the message,

[-- Attachment #3: Type: text/plain, Size: 265 bytes --]

> rather than a Latin-2 "á"[*].  If you quote this, and add some text of
> your own with a Latin-2 "á" (or if the quote contains a character like
> "ń" which isn't in Latin-1), then Mule thinks you've mixed two different
> encodings.  That's why it uses UTF-8.

      parent reply	other threads:[~2001-03-27 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vgp26plr.fsf@cachemir.echo-net.net>
     [not found] ` <wkbsqpa6bu.fsf@try.harder.Invalid>
     [not found]   ` <uu8zltnlza.fsf@nbsp.nsk.su>
2001-03-26 17:08     ` Jakub Martyński
2001-03-26 17:09       ` Jakub Martyński
2001-03-27 18:43       ` Toby Speight [this message]

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=s84rwf833n.fsf@lanber.cam.eu.citrix.com \
    --to=streapadair@gmx.net \
    /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).