In article <[EMAIL PROTECTED]>, Stefan Monnier <[EMAIL PROTECTED]> writes:
>>> Hmm... indeed the translation-table-for-input is not used for X11 keys. >>> Now that I look at it a bit more, I think the patch below would make sense. >>> What do other people think? >> That doesn't work in some case. The value of >> translation-table-for-input can be different in each buffer >> (depending of buffer-file-coding-system of a buffer). > Of course, that's why we can't do directly it in the > xkeysym-> char conversion. But it seems like doing it in read-char > should work. I don't know the diffence between them because even read-char doesn't know how a caller will treat the returned character. > Can you show me an existing piece of code where it wouldn't > work right? No, I can't. But shouldn't we avoid such an incompatible change at this stage? > Hypothetical examples aren't too interesting since we can also > concoct such examples where the current "translate in > self-insert-command" can be made to fail. I didn't know that self-insert-cmmand also uses translation-table-for-input. I have thought that the variable is for an input method as in this docstring: Char table for translating self-inserting characters. This is applied to the result of input methods, not their input. See also `keyboard-translate-table'. Anyway, could you show me such an example? --- Ken'ichi HANDA [EMAIL PROTECTED] _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel