From: Michael Below <mbelow@antithese.de>
Subject: Re: Automatically detecting the charset
Date: Fri, 24 Jan 2003 11:16:21 +0100 [thread overview]
Message-ID: <87el727szu.fsf@antithese.de> (raw)
In-Reply-To: <87y95cm9ec.fsf@antithese.de>
Hi,
a followup to Kai's message
<84bs277szf.fsf@lucy.is.informatik.uni-duisburg.de>:
> For keyboard input, it might help to say C-x RET k iso-8859-15 RET.
> Then enter umlauts. Do they show up in the proper encoding?
No, that doesn't help. I am being offered iso-latin-9 as a default
when I do that, but C-u C-x = still gives me "eight-bit-graphic".
> Try
>
> LANG=de_DE@euro emacs -q -no-site-file
>
> in bash. Then open a file with umlauts into that Emacs. Is that
> okay?
Hey, that works! Now characters are recognized as something like:
character: ö (07566, 3958, 0xf76)
charset: latin-iso8859-15
(Right-Hand Part of Latin Alphabet 9 (ISO/IEC 8859-15): ISO-IR-203)
code point: 118
syntax: word
category: l:Latin
buffer code: 0x8E 0xF6
file code: F6 (encoded by coding system iso-latin-9-unix)
font:
-monotype-courier new-medium-r-normal--17-128-95-95-m-100-iso8859-15
That sounds much better!
It also works if I leave out the -q.
So it looks like the system init files are buggy somehow.
I know these init files:
~ $ls /etc/emacs/site-start.d
00debian-vars.el 50dpkg-dev.el 50gettext.el 50mew.el
50bbdb.el 50erc.el 50mailcrypt.el 50user-de.el
~ $ls /etc/emacs21/site-start.d
00debian-vars.elc 49url.el 50psgml-init.el 50w3.el
Should I try removing them and putting them back in one by one, or
is there a more intelligent approach?
Ciao
Michael
--
_Agricultural activity_ is the management by an enterprise of the
biological transformation of biological assets for sale, into
agricultural produce, or into additional biological assets. IAS 41,5
next prev parent reply other threads:[~2003-01-24 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 10:29 Michael Below
2003-01-21 11:02 ` Kai Großjohann
[not found] ` <87wukxtrhe.fsf@antithese.de>
[not found] ` <85el75cvl5.fsf@bretagne.rail.eu.org>
[not found] ` <87u1g1ti38.fsf@antithese.de>
[not found] ` <87y95cm9ec.fsf@antithese.de>
2003-01-23 16:04 ` Kai Großjohann
2003-01-24 10:16 ` Michael Below [this message]
2003-01-24 12:34 ` Kai Großjohann
[not found] ` <87u1fwud4w.fsf@antithese.de>
2003-01-26 20:25 ` Michael Below
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=87el727szu.fsf@antithese.de \
--to=mbelow@antithese.de \
/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).