From: John Goerzen <jgoerzen@complete.org>
Subject: Re: Latin-1 characters in Gnus
Date: Fri, 03 Jan 2003 14:28:32 -0600 [thread overview]
Message-ID: <87of6yvuz3.fsf@christoph.complete.org> (raw)
In-Reply-To: <863coacbxl.fsf@kronstadt.homeunix.net>
Ian Zimmerman <itz@speakeasy.org> writes:
> I just had some problems with this myself (see "european headers"
> thread yesterday).
Interesting discussion (those following along at home may find it at
http://groups.google.com/groups?dq=&hl=en&lr=&ie=UTF-8&threadm=m3bs2yg0wt.fsf%40quimbies.gnus.org&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26group%3Dgnu.emacs.gnus
Unfortunately, it wasn't directly helpful to this question -- I don't
want to install half a gig of fonts to get a single character :-)
However, later experimentation showed that installing:
xfonts-base-transcoded xfonts-75dpi-transcoded xfonts-100dpi-transcoded
solved this particular problem -- for X. Still is a problem in an
xterm, though.
> John> In a text console, gnus always renders this as a question mark.
>
> For terminals, you need to know your terminal type (ie. the TERM
> environment variable). Then, stick something like this in
> ${EMACS}/site-lisp/term/${TERM}.el:
>
> ;; this from my linux.el
> ;; The Linux console handles Latin-1 by default.
>
> (unless (terminal-coding-system)
> (set-terminal-coding-system 'iso-latin-1))
I tried setting this manually (M-x set-terminal-coding-system RET
iso-latin-1 RET) before starting gnus. It had no effect. I also
tried setting it to latin-1 (any idea what the difference is?), which
also had no effect.
> See the thread yesterday. You need both *-iso8859-1 and *-iso8859-15
> versions of your emacs font. I bet the reason it "sometimes" works is
> you have the -1 font and don't have the -15 one.
Really weird, as it's an 8859-1 character. I don't even know what the
8859-15 charset is for...
-- John
next parent reply other threads:[~2003-01-03 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <873coa6slo.fsf@christoph.complete.org>
[not found] ` <863coacbxl.fsf@kronstadt.homeunix.net>
2003-01-03 20:28 ` John Goerzen [this message]
[not found] ` <86fzs9onra.fsf@kronstadt.homeunix.net>
[not found] ` <87adihk98i.fsf@christoph.complete.org>
2003-01-04 14:28 ` 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=87of6yvuz3.fsf@christoph.complete.org \
--to=jgoerzen@complete.org \
/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).