Microcai, le Mon 29 Nov 2010 18:11:16 +0800, a Ãcrit : > å 2010-11-29äç 10:58 +0100ïSamuel Thibaultåéï > > 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 > > YES, my patch just include BMP(mostly CJK), not full UNICODE. IF it can > be included, then I can do more work to make sure it doesn't break old > stuff. And it's configurable. users don't have to be forced to use. It seems you didn't get my point: what is the use of including CJK into kernel when that won't solve the issue for e.g. arabic, while fixing fbterm will solve the issue for both arabic and CJK? 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
