Kaixo! On Thu, Feb 21, 2002 at 06:50:27AM -0500, Glenn Maynard wrote: > On Thu, Feb 21, 2002 at 11:59:14AM +0100, Pablo Saratxaga wrote: > > It isn't that much of a problem. > > I think it's not a completely trivial loss, compared to an ASCII environment > where filenames were completely unambiguous
I don't know; I have never used an ascii environment; I need at the very least iso-8859-1 :) > > that the system will tell him "no such filename" and he will be puzzled > > as he sees there is; as there is no visual difference betwen a precomposed > > character like "aacute" and two characters "a" and "composing acute accent". > > Should control characters ever end up in filenames? I'd be surprised if > many terminal emulators handled copy and paste with control characters > well, if at all. Well, it sometimes happen to me that I hit Ctrl-V by accident then another key and end up with a filanem with escape and other ctrl sequences. > > The normalization should be done at the input method layer; that way it will > > be transparent and hopefully, if all OS do the same, the potential problem > > of duplicates will never happen. > > See my other response: characters are often entered in other ways than a > nice modularized input method; terminal emulators will need to behave in > the same way as IMs for this to work, as well as GUIs at some layer. I consider as an input method too the whatever code that allows to type dead keys and have accents, and the compose key etc. A terminal emulator doesn't needs to do anything, they don't handle input themselves (real terminal does; but terminal emulators are just another window on the screen, like any other program, from the input perspective) So, what should be addressed is an agreement on what should input methods, keyboards, compose etc produce. IMHO it should be normalized in a known and predictable way, and if possible using the same normalization across systems and different operating systems, so a same keystroke will produce the same result. -- Ki �a vos v�ye b�n, Pablo Saratxaga http://www.srtxg.easynet.be/ PGP Key available, key ID: 0x8F0E4975 -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
