Hi, On Thu, 12 Apr 2007, Egmont Koblinger wrote:
> On Thu, Apr 12, 2007 at 05:52:49PM +0200, Roman Zippel wrote: > > > Well, it often doesn't end there, other users may report these as bugs and > > want to get them fixed, so we have to look ahead a little for possible > > problems. > > They may even report that the current behavior of not knowing anything about > double-width characters is wrong. If Unicode is updated and someone reports > the kernel code is outdated, it's going to be fairly easy to update that one > as well. As far as Unicode is concerned we could go really wild here, e.g. how do we handle decomposed characters, there are also halfwidth characters... So the primary question is still: is this a kernel problem? The kernel only implements a simple fixed char width output device. Does it really make sense to pretend being able to handle characters, we can't display in first place? > > It has everything to do with this. It describes the terminal capabilities, > > so why should variable width support not one part of it? > > Nice idea. Terminfo database should tell whether a particular terminal > supports double-width characters. Applications should expect the cursor to > move one or two cells depending on this. So both terminfo databases as well > as plenty of libraries and applications would need update. If everyone reimplements this kind of stuff, something is seriously wrong... bye, Roman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
