On 9/23/06, Peter Dyballa <[EMAIL PROTECTED]> wrote:
The improvement is that I can find via an Unicode value an ISO Latin encoded character – is this an improvement?
It's what you asked for -- that input codes use some well-known encoding rather than the unfamiliar emacs codes.
The file code is A4 in any ISO Latin case, and the character is U+20AC in Unicode when in ISO Latin-10/ISO Latin-0 or ISO Latin-9. This looks like a Do What I Mean. Really not bad! But the real way should be C-s C-q 2 4 4 RET or C-s C-q A 4 RET or C-s C-q 1 6 4 RET (decimal), because it searches for the codes one expects in the encoded file, and which does not work.
I think that sounds awful -- I do not think users want to learn the codepoints in all encodings they use, they simply want to be able to enter _characters_ that they don't know how to enter via the keyboard. UCS codepoints are good because they allow _all_ emacs characters to be entered in a consistent way. Having C-q use the buffer's file encoding on the other hand seems quite annoying, because it requires users to use different numbers depending on what the file they're editing was saved in (and I suspect a large portion of the time, users don't even _know_ what encoding their file uses). Nonetheless, if you feel that is the right method, feel free to implement it and allow us to try it out (I offered the patch above because it is very simple and offers useful functionality, but I do not know offhand how to implement what you want). -Miles -- Do not taunt Happy Fun Ball. _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
