From: Lars Balker Rasmussen <lbr@image.dk>
Subject: Re: pgnus and ntemacs 20.3.1
Date: Sun, 06 Sep 1998 17:59:00 GMT [thread overview]
Message-ID: <wkogstktkg.fsf@image.dk> (raw)
In-Reply-To: <m37lzh433r.fsf@sparky.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Lars Balker Rasmussen <lbr@image.dk> writes:
> > (standard-display-european t)
> > (require 'latin-1)
>
> Remove these, and use
>
> (set-language-environment "Latin-1")
>
> instead.
Yes, I tried that first, which is even worse. Then I went through
ntemacs' mailinglist archive from the last month, and found the "old"
approach used above recommended for fixing inputting accented letters.
For the record, set-language-environment causes
From: svar_til@usa.net (=?ISO-8859-1?Q?Martin_Herl=F8w?=)
Subject: =?ISO-8859-1?Q?Priser_m.m_1049_Officiel_respons_=F8nskes?=
to show as
R [ 15: Martin Herlxw ] Priser m.m 1049 Officiel respons xnskes
in the Summary buffer, and the same in the Article buffer.
Articles with unencoded iso-latin-1 characters will show as
[...] Re: Priser m.m 1049 Officiel respons \370nskes
in both buffers.
Articles with
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
shows as
1) G\346lder der s\370ndagstakst p\345 helligdage?
and articles without any Content-* headers are the same.
This message-buffer still has -\ as "buffer-type", and I can't see the
accented characters I input (no highbit):
æøå (ae oe aa keys), naîve (hat accent key, `i'), façade (`C-x 8 , c')
Frustrated,
--
Lars Balker Rasmussen "Woo hoo!?"
.
prev parent reply other threads:[~1998-09-06 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-06 15:20 Lars Balker Rasmussen
1998-09-06 15:35 ` Lars Balker Rasmussen
1998-09-06 16:55 ` Alan Shutko
1998-09-06 16:28 ` Lars Magne Ingebrigtsen
1998-09-06 17:59 ` Lars Balker Rasmussen [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=wkogstktkg.fsf@image.dk \
--to=lbr@image.dk \
/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).