microcai, le Mon 29 Nov 2010 09:42:30 +0800, a écrit : > >> Well, if you have that time, please find out those softwares that need > >> to rewrite, and, send patches to them. I'm sure they will just reply : > >> why not handle UNICODE in kernel ?! > > > > Which has been answered, if you want to run multiple graphical apps on a > > framebuffer use a windowing system like everyone else does, and I would > > imagine "use X" is what most of the software people would tell you. > > think of w3m. which runs on framebuffer, so ,fbterm is useless here. > But w3m uses framebuffer to draw pictures, not characters. > So, if you want nice output, enable UNICODE font in kernel will be the > best way rather than hacking into the w3m code. Well, fbterm shouldn't prevent applications from being able to draw on the console. That's where the fix could go too (and it makes a lot of sense). > if you hack one w3m ,there will be another one that need this kinds of hack .... > implement it in kernel was/is/will be the best choice. The kernel will never accept good enough support for all kind of unicode script. Think of arabic ligatures, tibetan combinations, etc. You don't want to put a rendering engine for these in the kernel. fbterm is there for that. 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
