From: Steinar Bang <sb@dod.no>
Subject: The displaying of ISO-8859-15
Date: Thu, 14 Dec 2006 11:32:40 +0100 [thread overview]
Message-ID: <87vekekbsn.fsf@bang.priv.no> (raw)
Platform: Intel Pentium M, Ubuntu Dapper,
emacs21 21.4a-3ubuntu2,
No Gnus v0.6 (CVS update from May 1 2006)
The good people at Opera has at one point in time made the bad
decision of promoting ISO-8859-15 as the default charset in email and
news messages sent from the Opera browser (at least when running in a
Western European locale).
One annoying thing is that if this setting is changed to
eg. ISO-8859-1, the setting isn't preserved when Opera is upgraded.
And experience has shown that admonishing Opera users to change their
charset setting, can be tiring on both the admonisher and the
admonished...
So I figured out how to make Gnus cast replies and followups to
8859-15 messages into 8859-1 when responding, and was satisfied with
that.
The main reason (apart from the purely aestethical dislike of
iso-8859-15 as a concept) for being annoyed with ISO-8859-15, is that
Gnus on my platform (see above) picked a bug-ugly font for those
characters. I've filed that under "probably caused by the fonts
installed on my platform, and not something I'd spend time on".
But today I did `C-u g' in the summary buffer to see the headers of an
ISO-8859-15 message. And down in the message body, the ISO-8859-15
characters were shown in the same font as the surrounding US-ASCII.
Ie. the same font ISO-8859-1 characters would have been shown in.
It then dawned on me that configuring the display of ISO-8859-15 in
messages is possibly something that Gnus can do. Eg. decide to
display it like ISO-8859-1 or something (who needs that silly Euro
char anyways...?).
Does anyone know?
Thanx!
- Steinar
next reply other threads:[~2006-12-14 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 10:32 Steinar Bang [this message]
2006-12-14 12:06 ` Reiner Steib
2006-12-28 7:50 ` Steinar Bang
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=87vekekbsn.fsf@bang.priv.no \
--to=sb@dod.no \
/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).