Full Unicode Support for FreeBSD

[Edwin Groothuis]

On Tue, Mar 16, 2010 at 11:10:04AM +0100, Gergely CZUCZY wrote:
> On Fri, 12 Mar 2010 20:49:16 +0100
> Dominic Fandrey <kamikaze at bsdforen.de> wrote:
> 
> > On 12/03/2010 19:23, ????????? Jiawei Ye wrote:
> > > On Sat, Mar 13, 2010 at 1:43 AM, Elmar Stellnberger
> > > <elmstel at 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.
> > 
> 
> I think he is referring to the syscons. Syscons lacks UTF supports,
> though some work is being done:
> http://wiki.freebsd.org/SysconsUnicodeProject

I use sysutils/jfbterm on my laptop which doesn't work with X
(hardware issue) anymore to overcome this problem.

Edwin
-- 
Edwin Groothuis		Website: http://www.mavetju.org/
edwin at mavetju.org	Weblog:  http://www.mavetju.org/weblog/