From: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: decode-coding-string gone awry?
Date: Mon, 14 Feb 2005 22:57:19 +0100 [thread overview]
Message-ID: <x5hdke24ao.fsf@lola.goethe.zz> (raw)
In-Reply-To: <jwvvf8ug7f0.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 14 Feb 2005 16:29:44 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Now I am venturing into the realm of pure luxury: is there a way to
>> have the eight-bit-* chars display as octal escapes always even when
>> real latin1 characters (inserted by a process with process-coding
>> latin1) get displayed transparently? I seem to remember that in those
>> "crazy" utf-8 buffers I had, those that were created by decoding
>> raw-text, there appeared latin-1 characters like the infamous Ã
>> character. But maybe I am mistaken about that. I'll just experiment
>> with the stuff a bit and probably use C-x = a lot.
>
> The eight-bit-* chars are different characters than the latin1 ones, so they
> can indeed be displayed differently. The eight-bit-* chars have internal
> codes 128-255, so you can use slots 128-255 of char tables to control how
> they're displayed. If the display-table says "nil" for one of them it'll be
> displayed as \NNN. IIRC in many normal startup situations, those slots are
> set so as to display latin-1 chars.
That explains that I remembered seeing Latin-1 (which is my normal
setup). That I was right now seeing the _expected_ \xxx sequences is
quite likely entirely the fault of my X11 environment which for some
completely unfathomable reason has LC_CTYPE=C set. I suspect a recent
change to fluxbox, but have yet to find the culprit.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-02-14 21:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 3:50 decode-coding-string gone awry? David Kastrup
2005-02-14 1:50 ` Kenichi Handa
2005-02-14 2:28 ` David Kastrup
2005-02-15 6:15 ` Richard Stallman
2005-02-15 9:31 ` David Kastrup
2005-02-15 16:17 ` Stefan Monnier
2005-02-17 10:35 ` Richard Stallman
2005-02-17 12:08 ` Kenichi Handa
2005-02-17 13:20 ` Stefan Monnier
2005-02-18 8:30 ` Kenichi Handa
2005-02-18 12:56 ` Stefan Monnier
2005-02-19 9:44 ` Richard Stallman
2005-02-18 14:12 ` Richard Stallman
2005-02-19 20:55 ` Richard Stallman
2005-02-21 1:19 ` Kenichi Handa
2005-02-22 8:41 ` Richard Stallman
2005-02-18 14:12 ` Richard Stallman
2005-02-14 13:37 ` Stefan Monnier
2005-02-14 13:50 ` David Kastrup
2005-02-14 16:57 ` Stefan Monnier
2005-02-14 17:24 ` David Kastrup
2005-02-14 18:12 ` Stefan Monnier
2005-02-14 18:41 ` David Kastrup
2005-02-14 19:30 ` Stefan Monnier
2005-02-14 20:09 ` David Kastrup
2005-02-14 20:56 ` Stefan Monnier
2005-02-14 21:07 ` David Kastrup
2005-02-14 21:29 ` Stefan Monnier
2005-02-14 21:57 ` David Kastrup [this message]
2005-02-14 21:26 ` David Kastrup
2005-02-15 17:28 ` Richard Stallman
2005-02-15 21:42 ` David Kastrup
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5hdke24ao.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).