> Don't you see the cosole code ? There is TODO that say , "hey , I need > UNICODE support..." And what has happened over time is that we've learned - that real unicode is hard - that some languages need very complex character handling, and this happens to be most of the major non western european languages in the world today and someone put all the needed logic into pango, and people wrote fbterm and friends. The world has moved on > Simply drawing characters won't need any hw acceleration. It doesn't > matter if it is slow. KMS and Wayland will make more people work under > console, trust me. No I don't trust you, sorry. You need compositing acceleration to do some of the character composing efficiently and to do anti-aliasing which for small symbols in many non western fonts is rather essential. > > Your other problem is mode setting, VESA is on its way out, a lot of > No, VESA will still be here for another decades. Some fb driver conflict VESA is X86 specific, PC class hardware specific and subject to various assumptions, when it works. No VESA on Intel MID platforms, no VESA on PPC, no VESA on Android phones > printk console , if redirect to a ttyS? , then the outer Linux world > terminal will do UNICODE handling. In a window in a debug/development environment under X11 with Pango.. -- 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
