Date: Wed, 15 Jul 2009 11:07:32 +0400 From: Kamigishi Rei <spambox@haruhiism.net> To: Dan Nelson <dnelson@allantgroup.com> Cc: Vladimir Grebenschikov <vova@fbsd.ru>, Ed Schouten <ed@80386.nl>, freebsd-current@freebsd.org, Franck Royer <royerfranck@free.fr> Subject: Re: UTF-8 on 8.0-CURRENT: Yes We Can! Message-ID: <4A5D8034.4090101@haruhiism.net> In-Reply-To: <20090715062041.GH63413@dan.emsphone.com> References: <4A5C9CE2.6060801@free.fr> <20090714155513.GO48776@hoeg.nl> <1247599592.2232.27.camel@localhost> <20090714194726.GP48776@hoeg.nl> <1247603171.2105.38.camel@localhost> <20090714204028.GT48776@hoeg.nl> <20090715062041.GH63413@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote: > Another option would be to dynamically remap the 256 text-mode characters as > needed, similar to how the mouse cursor is displayed. The average > single-language console will have much less than 256 unique characters > onscreen at once at any one time, so the average console will rarely have a > phyical character remapped once a glyph has been assigned to it. Any more > than 256 onscreen at once could be replaced with a special symbol or > remapped to a similar character if possible. You could even preferentially > replace symbol/line-drawing characters first, and try and preserve > characters in the area around the cursor This is probably true for European countries, however I can easily imagine a situation where I have much more than 256 different characters on my screen - f.ex. reading a website in Links; it will have latin characters (numbers, symbols, punctuation marks) in URLs and kana & kanji as the text itself. So a completely Unicode-compatible solution would be much more preferred. -- Kamigishi Rei KREI-RIPE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A5D8034.4090101>