Date: Mon, 28 Jun 1999 12:23:11 +0100 From: Nik Clayton <nclayton@lehman.com> To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG> Cc: motoyuki@snipe.rim.or.jp, nik@nothing-going-on.demon.co.uk, jkh@zippy.cdrom.com, kuriyama@sky.rim.or.jp, doc@FreeBSD.ORG, freebsd-translate@ngo.org.uk, jdp@FreeBSD.ORG, freebsd-tech-jp@jp.freebsd.org Subject: Re: Resolution: FDP reorganisation Message-ID: <19990628122311.I15628@lehman.com> In-Reply-To: <199906281058.DAA52295@silvia.hip.berkeley.edu>; from Satoshi - Ports Wraith - Asami on Mon, Jun 28, 1999 at 03:58:56AM -0700 References: <57461.930305624@zippy.cdrom.com> <199906251220.VAA22552@sakura.snipe.rim.or.jp> <19990625150942.K15628@lehman.com> <199906252311.QAA04505@silvia.hip.berkeley.edu> <19990626014203.B71532@catkin.nothing-going-on.org> <199906271240.VAA06437@rei.snipe.rim.or.jp> <19990628115003.C15628@lehman.com> <199906281058.DAA52295@silvia.hip.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 28, 1999 at 03:58:56AM -0700, Satoshi - Ports Wraith - Asami wrote:
> That's not what Konno-san meant. The "confusion" was about which one
> to use, not what each directory means. There is no need to have more
> than one Japanese directory. If both "ja.eucJP" and "ja.JIS" exists,
> Japanese people will still be confused. :)
Why? Fast forward to the future, 6 months from now.
# cd /usr/doc
# ls
en_US.ISO-8859-1/ ja_JP.eucJP/ zh_TW.Big5/
ja_JP.SJIS/ zh_CN.EUC/
[... and others ...]
Our SA wants to install the English documentation. What do they do?
# cd en*
# make install
and off it goes, installing the docs into /usr/share/doc/en_US.ISO-8859-1,
and making a symlink, /usr/share/doc/en/, that points to that directory.
Now they want to install both versions of the Chinese docs;
# cd ..
# cd zh_CN*
# make install
and as above, the docs get installed in /usr/share/doc/zh_CN.EUC, and a
compatability symlink is made from /usr/share/doc/zh.
Then they do
# cd ..
# cd zh_TW*
# make install
The docs now get installed in /usr/share/doc/zh_TW.Big5. However, because
the /usr/share/doc/zh symlink already exists, it is not changed to point
at the Big5 encoded docs. If the SA had installed these docs in a different
order then the Big5 encoding would become the default, simply because the
symlink for that one would have been made first.
Alternatively, they could do the steps above, but run something like
# make DEFAULT_ENCODING=yes install
and the existing /usr/share/doc/zh would be removed (regardless of whether
it was a symlink or a real directory), the docs would still be installed in
to /usr/share/doc/zh_TW.Big5, and the symlink would now point there
instead.
Japanese would function in exactly the same way. The only difference is
that whereas zh_TW.Big5 and zh_CN.EUC are different languages, and both
would exist in full in the tree, the ja_JP.SJIS files would be generated
automatically from the EUC encoded docs, using rules in the Makefile.
I accept that the Japanese team have decided that EUC is to be their
default encoding, and I have no problem with that. However, I don't want
to have to *force* this encoding on every Japanese FreeBSD user. Perhaps
some of them already have a mass of documentation in SJIS format, and
they would prefer to stick with SJIS format if at all possible -- or they
have a commercial application that can only handle SJIS format.
Whatever. I want to make it easy for them to choose. This is a side
effect of me wanting to make it easy for other users to choose.
N
--
--+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+--
--+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+--
--+==[ Year 2000 Testing: It's about time. . . ]==+--
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?19990628122311.I15628>