From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Trouble displaying 8bit postings properly
Date: Tue, 18 Mar 2003 03:26:27 +0100 [thread overview]
Message-ID: <m3u1e14dgs.fsf@defun.localdomain> (raw)
In-Reply-To: <v9smtmjf0r.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Sun, Mar 16 2003, Jesper Harder wrote:
>
>> The real solution to 2. is to have Emacs know about Windows-1252, which
>> it doesn't. I think it's supported in the Unicode branch, though.
>
> Windows-1252 is supported in CVS-HEAD of Emacs.
> Just say (require 'code-pages).
Thanks, I hadn't noticed that there's both the old 'codepages.el' and
the new 'code-pages.el'.
This will work, but you have to add Windows-1252 to the coding system
priorities explicitly -- otherwise Emacs won't detect it.
But be sure _not_ to add it to the front, else Gnus will send out
windows-1252 crap just like Outlook Express. Hmm, maybe we should put
in a check for this to avoid that embarrasment.
prev parent reply other threads:[~2003-03-18 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 13:04 Karl Eichwalder
2003-03-16 21:20 ` Jesper Harder
2003-03-17 13:31 ` Reiner Steib
2003-03-18 2:26 ` Jesper Harder [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=m3u1e14dgs.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).