Alan Coopersmith wrote:
> Richard Lowe wrote:
> > Roland Mainz wrote:
[snip]
> The bug in question is currently assigned to the solaris/shell/bourne
> category, which I would have thought would be an open category.
> 
> It's even had a comment added to it by one of the i18n engineers, but
> unfortunately, he put it in the "Comments" field so you won't see it
> on bugs.opensolaris.org:
> 
>   This does not need to be done.  The man command appropriately handle
>   the locale setting.  For example, if ja_JP.UTF-8 locale is set and
>   /usr/share/man is set in MANPATH, the man command will search
>   /usr/share/man/ja_JP.UTF-8 directory first.  If it failed to find
>   a corresponding manpage, the man command will fall back to
>   /usr/share/man directory.

This does not AFAIK help in all cases. /usr/bin/man may do the
locale-specific lookup but all other tools do not do that (for example
/usr/openwin/bin/xman etc.). Either all tools, including external manual
page viewers/help viewers are modified to do the same "trick" of
appending ${LC_MESSAGES} (or ${LANG}) to each manual path element first
or we tweak ${MANPATH} to include the locale-specific subdirs.

Is there any "standard" (POSIX/Unix98/etc.) which defines the behaviour
for /usr/bin/man in the presence of localised manual pages ? If there is
such a standard which says that /usr/bin/man should look at the
${LC_MESSAGES}-specific subdirs for each element in ${MANPATH} then I'll
drop that part of the RFE (but the remaining part of setting ${MANPATH}
based on ${PATH} would still be very nice... :-) ).

----

Bye,
Roland

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz at nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 7950090
 (;O/ \/ \O;)

Reply via email to