From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: coding systems and input methods are non-intuitive stuff
Date: Tue, 30 Jan 2007 01:17:48 -0700 [thread overview]
Message-ID: <epmuv3$56p$1@sea.gmane.org> (raw)
In-Reply-To: <f7ccd24b0701260911k6209e858y54c948d52ba1d2d0@mail.gmail.com>
Juanma Barranquero wrote:
> C-x b *scratch* RET
> C-x RET f latin-1 RET ; buffer coding system = latin-1
> C-u C-\ romanian-prefix RET ; input method: romanian-prefix
> ,s ; character: ş (2362, #o4472, #x93a,
> ; U+015F)
> <left> M-x quail-show-key RET ; To input `ş', type ",s"
> <right>
> C-x RET f utf-8 RET ; buffer coding system = utf-8
> ; input method: the same as before
> ,s ; character: ş (331903, #o1210177,
> ; #x5107f, U+015F)
> <left> M-x quail-show-key RET ; ş can't be input by the current
> ; input method
>
> Now, I understand that the buffer code for these characters is not the
> same... but it is quite weird nonetheless to input a character with
> the current input method, and afterwards be told that it "can't be
> input by the current input method".
The thing that confuses me is that the ISO 8859-1 character set (which
is what the latin-1 coding system encodes, right?) only contains U+0000
- U+00FF. So how does U+015F get inserted into a latin-1 buffer?
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2007-01-30 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 17:11 coding systems and input methods are non-intuitive stuff Juanma Barranquero
2007-01-30 8:17 ` Kevin Rodgers [this message]
2007-01-30 8:35 ` David Kastrup
2007-01-30 8:38 ` Juanma Barranquero
2007-01-30 12:46 ` Kenichi Handa
2007-01-30 12:58 ` Juanma Barranquero
2007-01-31 0:46 ` Kenichi Handa
2007-01-31 2:12 ` Juanma Barranquero
2007-02-01 1:48 ` Kenichi Handa
2007-02-01 1:54 ` Juanma Barranquero
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='epmuv3$56p$1@sea.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.