Hi, Pavel Vávra, le Tue 26 Dec 2006 01:01:40 +0100, a écrit : > thank you for your explanation. How short is the term you are talking about?
Someone has to write a patch, have it accepted upstream, published in a new kernel, then the interface may be considered accepted, and the kbd package be fixed for using it. > Is any chance that it will be fixed in stable etch? I don't think so. > I cannot believe that I am the first one who find this bug/feature. I'm not surprised. Not many people use the linux console nowadays (this bug only affects the linux console, not X!). Even less people use the linux console _and_ need non-latin1 chars. > Does it men that etch will not be ready to UTF-8 for non-Latin1 countries? It _is_ ready for UTF-8 for non-Latin1 countries concerning gnome/kde/etc. desktops. But Linux kernel's console is not. Actually, the linux console sucks for a lot of such utf-8-related things, and not many people are really brave enough to tackle the issue, considering how many people really use it nowadays. Another approach would be to use a framebuffer xterm like bogl or jfbterm. Samuel
