Date: 06 May 2000 02:10:10 -0700 From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: Martin Cracauer <cracauer@cons.org> Cc: committers@FreeBSD.ORG, i18n@FreeBSD.ORG Subject: Re: vision Message-ID: <vqc4s8cxcwd.fsf@silvia.hip.berkeley.edu> In-Reply-To: Martin Cracauer's message of "Fri, 5 May 2000 20:15:05 %2B0200" References: <20000504102932.8227C37B726@hub.freebsd.org> <vqcn1m53u2s.fsf@silvia.hip.berkeley.edu> <20000505114226.V1642@argon.blackdawn.com> <20000505180526.A6360@jedi.wbnet> <20000505121044.Y1642@argon.blackdawn.com> <20000505182053.A6440@jedi.wbnet> <vqc66ss51ws.fsf@silvia.hip.berkeley.edu> <20000505201505.A38121@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
(Yanked over to i18n@FreeBSD.org) * From: Martin Cracauer <cracauer@cons.org> * As a result, I don't think that FreeBSD should do serious moves into a * multilingual direction. To use any Unix-based system effectivly, you * need to know English, no way around it. I think that localized * systems make things harder in the long term (for users how initially * prefer the localized version, but want to make full use of the system * later). I'm not talking about error messages. The Japanese people don't care much about that either. However, treating multibyte characters as data is a must. Whether commands like sed and grep correctly handle multibyte characters, whether applications compiled and linked just like other OSes can handle multibyte characters (right now there are a whole bunch that require a patch to add "-lxpg4"), those kinds of stuff. I believe the newly imported tcsh already has native multibyte support. This is a good thing. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqc4s8cxcwd.fsf>