Date: Fri, 12 Mar 2010 20:49:16 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: freebsd-ports@freebsd.org Subject: Re: Full Unicode Support for FreeBSD Message-ID: <4B9A9ABC.90801@bsdforen.de> In-Reply-To: <c21e92e21003121023m65708c92p50d237d99d84dc8d@mail.gmail.com> References: <4B9A7D2D.9070903@gmail.com> <c21e92e21003121023m65708c92p50d237d99d84dc8d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/03/2010 19:23, 葉佳威 Jiawei Ye wrote: > On Sat, Mar 13, 2010 at 1:43 AM, Elmar Stellnberger <elmstel@gmail.com> wrote: >> Isn`t it time for FreeBSD to fully support Unicode/UTF-8 by now? >> It is considered to be standard charset by now. XML uses it by default. >> If you are working with texts in different languages there is no >> alternative to UTF-8. >> If you chat with a Linux machine you can easily run into charset >> troubles if you are >> still using the old iso-8859-1. >> >> By now it is no problem to activate UTF-8 for your console. >> However a comprehensive Unicode support would require much more: >> i.e. configuring all user packages like KDE for Unicode support and >> asserting that also file names (f.i. from ext2 partitions) are interpreted >> correctly. > Do you have a concrete example of how FreeBSD fails to support UTF-8? > I have been setting my LANG to zh_TW.UTF-8 for years without problem > with modern software. As this is the ports list, I guess you have some > issues with the software in the ports collection? I second this. I've been using en_GB.UTF-8 since 5.3. Even the file system can deal with UTF-8 encoded file names. I tried to create files with Arabian, Chinese, Russian and other characters. It all worked. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B9A9ABC.90801>