From: Rick Hohensee <humbubba@smarty.smart.net>
To: linux-kernel@vger.kernel.org
Subject: Re: linux localization
Date: Mon, 12 Mar 2001 00:39:51 -0500 (EST) [thread overview]
Message-ID: <200103120539.AAA04151@smarty.smart.net> (raw)
>> My work will concern with the internationalization of Linux
>> So, could anybody tell me what kinds of features should be in the
>> consideration when linux be localized from english to Japanese or
chinese,
>> say using 2 bytes character set.
>
>Most of the Linux userspace libraries are set up for handling UTF8 and
>other internationalisations. Fonts are more of an issue and lack of
application>translations. Filenames are defined to be UTF8.
For the features that don't exist in Linux yet, you want to look closely
at Plan 9 From Bell Labs, whence UTF-8 originates. Plan 9 for example has
font cacheing in the kernel for huge glyph sets, if I read it right. The
Plan 9 C compiler, written by Ken Thompson, author of UNIX and ed,
specifically for writing Plan 9, is fully UTF-8 also. Everything else in
Plan 9 is also UTF-8, from ed to libc to the GUI.
Per-process namespaces are a Plan 9 idea also. That is the ultimate in
localization. Plan 9 was released relatively recently under a license
clearly patterned after the GPL. Congratulations once again to Richard
Stallman. Thompson, Ritchie, Pike and so on have embraced his most
important ideas.
Plan 9 has a narrow platform base compared to Linux or NetBSD. I myself
haven't been able to install it on my oldish hardware. You probably need
to see it running, I suspect.
My own Dotted Standard File Hierarchy mechanism in cLIeNUX
(Linux/GNU/unix) may also be of interest. See my "/" below. That could
easily be Japanese, Mandarin, Hindi, etc.
ftp://linux01.gwdg.de/pub/cLIeNUX/descriptive/DSFH.html
Rick Hohensee
www.clienux.com
:; cLIeNUX /dev/tty3 00:12:08 /
:;d -d */
Linux// dev// help// mounts// suite//
boot// device// incoming// owner// temp//
command// floppy// log// source//
configure// guest// lost+found// subroutines//
:; cLIeNUX /dev/tty3 00:42:44 /
:;
next reply other threads:[~2001-03-12 5:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 5:39 Rick Hohensee [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-12 1:39 linux localization XingFei
2001-03-12 2:21 ` Alan Cox
2001-03-12 6:46 ` Martin Dalecki
2001-03-12 12:47 ` Rik van Riel
2001-03-12 20:35 ` Andreas Dilger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200103120539.AAA04151@smarty.smart.net \
--to=humbubba@smarty.smart.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.