Date: Sat, 15 May 1999 17:47:17 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Kazuo Horikawa <horikawa@jp.freebsd.org> Cc: nik@nothing-going-on.demon.co.uk, ru-freebsd-doc@freebsd.ru, doc@FreeBSD.ORG, freebsd-translate@ngo.org.uk, hanai@jp.freebsd.org Subject: Re: [RU-DOC] FDP Directory Reorganization Message-ID: <19990515174717.A656@nagual.pp.ru> In-Reply-To: <19990515222516E.k-horik@yk.rim.or.jp>; from horikawa@jp.freebsd.org on Sat, May 15, 1999 at 10:25:16PM %2B0900 References: <19990514204302.B43389@catkin.nothing-going-on.org> <19990515222516E.k-horik@yk.rim.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> The problem coming down the pipe with the full locale > specification is cases where there may be numerous locales for > any given language. Right now there are 4 de locales, 4 en > locales, 4 fr locales, 2 it locales, and 2 nl locales that differ > only in the country specification. While genuine > language/dialect differences do exist in some cases, how likely > is it that de_CH is going to produce a different set of > translations that de_DE? Thinking from locale autosearch perspective, all particular language variants could be linked to default langauge variant. If some language variant different with default appearse, it can be de-linked making real directory. But I don't think it really happens for documentation, so it seems that <lang>/<encoding> scheme is right. Maybe even <lang>.<encoding> if people choose only one encoding for documentation, but *not* simple <lang> (assuming some unknown default encoding) which means that program can't sense it. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990515174717.A656>