Microcai, le Mon 29 Nov 2010 17:32:37 +0800, a Ãcrit : > å 2010-11-29äç 09:58 +0100ïSamuel Thibaultåéï > > Microcai, le Mon 29 Nov 2010 09:14:04 +0800, a Ãcrit : > > > Hey, my old patch already did it , and do not break any old stuff. > > > > To your knowledge. IIRC while reading your patch I found a couple of > > things that would most probably break some corner cases, which could > > go unnoticed, that's why I proposed to first extend the internal vc > > content matrix into unicode values, so as to clearly have to upgrade all > > drivers. > > I doesn't matter *how to do* . Concerning breaking existing stuff, yes, it does. > I have many different kinds of patchs that did it in different ways. > > What realy matters is that, do we agree that add unicode font support is > acceptable ? Simple unicode font (i.e. just go beyond the arbitrary historical-vga 512 glyphs limit for fbcon) might go in. Double-width is questionable, but it can probably simple enough to be able to get in (there is already some code for it anyway). But complete unicode support (with arabic ligatures, tibetan combinations, etc.) won't ever be accepted in the kernel as that's far too involved in terms of font rendering. So the userland way needs to be fixed for these anyway, and then things like chinese will go along... Samuel -- To unsubscribe from this list: send the line "unsubscribe linux-console" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
