Date: Sun, 16 May 1999 18:16:07 +0900 From: horikawa@jp.freebsd.org To: ache@nagual.pp.ru Cc: horikawa@jp.freebsd.org, nik@nothing-going-on.demon.co.uk, ru-freebsd-doc@freebsd.ru, doc@FreeBSD.ORG, freebsd-translate@ngo.org.uk, asami@freebsd.org Subject: Re: [RU-DOC] FDP Directory Reorganization Message-ID: <19990516181607K.k-horik@yk.rim.or.jp> In-Reply-To: Your message of "Sat, 15 May 1999 18:09:10 %2B0400" <19990515180910.A1012@nagual.pp.ru> References: <19990515180910.A1012@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
I cc'd ports master, Satoshi Asami, because changes in manpage
destination should have some influences on ports.
From: "Andrey A. Chernov" <ache@nagual.pp.ru>
Subject: Re: [RU-DOC] FDP Directory Reorganization
Date: Sat, 15 May 1999 18:09:10 +0400
> ... continue ...
>
> Imagine bad things happens, if user set LANG to ja_JP.SJIS while mans are
> in EUC stored in /usr/share/man/ja
>
> It must be renamed to /usr/share/man/ja.EUC to resolve this collision.
Now, ja-man-1.1g (jman) can support both ja_JP.EUC and ja_JP.SJIS,
using only man/ja subdirectory which contains ja_JP.EUC roff sources,
because:
o ja-groff-0.99 accepts only ja_JP.EUC roff sources (regardless of
LC_* or LANG) and outputs formated manuals in ja_JP.EUC (Yes, I
think that this ja-groff-0.99 behavior is *hard-coded*).
o ja-less-233 (jless) can handle LC_* or LANG. jless can accept both
ja_JP.EUC and ja_JP.SJIS (it has auto-detection mechanism) and
outputs text as specified by LC_* or LANG.
So, if we type `LANG=ja_JP.SJIS jman ls' (*1):
(1) ja-man-1.1g (jman) finds /usr/share/man/ja/ls.1.gz, and invokes
ja-groff-0.99 (jgroff) and ja-less-233 (jless) like:
gzcat /usr/share/man/ja/ls.1.gz | jgroff -man -Tnippon | jless
(2) ja-groff-0.99 (jgroff) accepts `gzcat /usr/share/man/ja/ls.1.gz`
which is in ja_JP.EUC and outputs in ja_JP.EUC.
(3) ja-less-233 (jless) accepts ja_JP.EUC and outputs in ja_JP.SJIS,
as specified by LANG.
If we type `LANG=ja_JP.EUC jman ls':
(1) ja-man-1.1g (jman) finds /usr/share/man/ja/ls.1.gz, and invokes
ja-groff-0.99 (jgroff) and ja-less-233 (jless) like:
gzcat /usr/share/man/ja/ls.1.gz | jgroff -man -Tnippon | jless
(2) ja-groff-0.99 (jgroff) accepts `gzcat /usr/share/man/ja/ls.1.gz`
which is in ja_JP.EUC and outputs in ja_JP.EUC.
(3) ja-less-233 (jless) accepts ja_JP.EUC and outputs in ja_JP.EUC, as
specified by LANG.
%%
If we must have Japanese manpages in both man/ja_JP.EUC and
man/ja_JP.SJIS instead of single directory man/ja, we will have both
man/ja_JP.EUC/ls.1.gz and man/ja_JP.SJIS/ls.1.gz. It doubles disk
usage to support both locales. I know that some commercial OS have
both ja_JP.EUC manuals and ja_JP.SJIS manuals, but I (personally)
think that it is not good idea to install both manuals which represent
same text, which are only encoded differently (supporting both locales
is needed on large systems to support both users who prefer ja_JP.EUC
and users who prefer ja_JP.SJIS).
When user-front-ended programs can handle locales (in this case, jman
searches only man/ja if LANG is ja_JP.EUC or ja_JP.SJIS, and jless can
convert ja_JP.EUC to ja_JP.SJIS losslessly if LANG is ja_JP.SJIS), I
think that we need not have as many text sources (in this case,
man/ja_JP.EUC/ls.1.gz and man/ja_JP.SJIS/ls.1.gz) as the numbers of
locales to support.
%%
When we have only ja_JP.EUC manuals in man/ja_JP.EUC, I think that we
can support ja_JP.SJIS by modifying ja-man-1.1g to search in
man/ja_JP.EUC (instead of man/ja) even if LANG is ja_JP.SJIS.
BTW, when we think about man page destination, we should also consider
about *ports* which install locale specific man pages. On March 1998,
/usr/local/man/ja_JP.EUC was renamed to /usr/local/man/ja, and many
ports maintainers had to rewrite Japanese man page destination. I
think that more discussion is needed to decide man page destination.
I think that we can discuss FDP Directory Reorganization and man page
destination separately. Can we discuss man page destination topic
after FDP Directory Reorganization is finished?
--
Kazuo Horikawa
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?19990516181607K.k-horik>