[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: coding systems and input methods are non-intuitive stuff
From: |
Kenichi Handa |
Subject: |
Re: coding systems and input methods are non-intuitive stuff |
Date: |
Tue, 30 Jan 2007 21:46:08 +0900 |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.93 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) |
Very sorry for the late response.
In article <address@hidden>, "Juanma Barranquero" <address@hidden> writes:
> 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 reason why the second quail-show-key fails is that the
input method is going to insert latin-2 character but as the
buffer-file-coding-system is changed to utf-8, the character
is translated by translation-table-for-input into
mule-unicode-0100-24ff character. Unfortunately as the data
structure of the input method still contains only latin-2
character, the current code of quail-show-key thinks the
translated character is not in the data structure.
I'm now trying to find a good way to solve this problem.
---
Kenichi Handa
address@hidden