On Sat, Feb 23, 2002 at 07:37:41PM +0000, Markus Kuhn wrote: > You have two files > > Müller > Müllerin > > in a directory, the first in NFD, the second in NFC. If you press M+TAB > in a yet to be written UTF-8 aware version of bash, it will fail to > expand to Müller, as the two strings differ after the first letter. > Typing Mu+TAB will expand one, and typing Mü+TAB will expand the other, > so there is a solution for experienced users. A user interface > inprovement would be to provide two control keys that allows to scroll > through the list of files that are available in the current state of the > TAB selection. I could also imagine bash doing a normalization, such > that entering a prefix in one normalization will include the file name > in the other one as well. There are lots of ways to implement this in a
But nothing with tab completion can fix the fact that I can't enter this by typing "Müller", and I don't see a good fix at all for that. This isn't quite the same as the homoglyph problem. (Someone pointed out that the c in "cat" could actually be a few different characters--but I can tell from the context that it *should* be a regular Roman "c". If it's not, it's probably someone playing games deliberately.) Either should still be copy-and-pastable already, but it'd be nice if that fallback could be avoided. I suspect that, like homoglyphs, there is no good fix, but I think this should be considered independently. (Since it's still copy-and-pastable, it's not as much of an issue to me as unprinting characters and other things that aren't.) > convenient way, and the only real problem is to get the bash maintainers > interested in UTF-8 at all ... *Is* there any bash maintainance? -- Glenn Maynard -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
