[comp.windows.x] dificulty with R3 man page names: *.3X11 and *.3Xt -- ULTRIX 2.3

kek@DINORAH.WUSTL.EDU (Ken Krippner) (12/01/88)

It seems that the   make install   does a fine job of putting things
in their expected places.

It seems however that it was decided to change the style of man page
filenames between R2 and R3.   R2, files were named, for instance,
XDrArc.3X  while for R3 the name XDrArc.3X11 is used.  Also, the
Xt man pages are named  XtAddCbk.3Xt 

At least on ULTRIX 2.3, these man pages are not found.  My experience
is that they must have only two character extensions beyond the dot.

Of course we were running R2 previously so that both the *.3X and
the *.3X11 files were present, and man has an easy time of giving us
a page (albeit out-of-date) unless it is a new function.  The cat3/...
added even more fun to the game of which man pages worked and which
didn't.

Anyway, has anyone else seen this?
  and	did you simply rename all of them as 3X?
  or	is their a sweeter solution?

TIA,
ken.

becker@CS.ROCHESTER.EDU (Tim Becker) (12/01/88)

   It seems however that it was decided to change the style of man page
   filenames between R2 and R3.   R2, files were named, for instance,
   XDrArc.3X  while for R3 the name XDrArc.3X11 is used.  Also, the
   Xt man pages are named  XtAddCbk.3Xt 

   At least on ULTRIX 2.3, these man pages are not found.  My experience
   is that they must have only two character extensions beyond the dot.

   Anyway, has anyone else seen this?
     and	did you simply rename all of them as 3X?
     or	is their a sweeter solution?

I had the same problem on my SunOS3.4 machine.  I renamed them to *.3.

Tim Becker.
becker@cs.rochester.edu

tom@ICASE.EDU (Tom Crockett) (12/02/88)

>  It seems however that it was decided to change the style of man page
>  filenames between R2 and R3.   R2, files were named, for instance,
>  XDrArc.3X  while for R3 the name XDrArc.3X11 is used.  Also, the
>  Xt man pages are named  XtAddCbk.3Xt
>  
>  At least on ULTRIX 2.3, these man pages are not found.  My experience
>  is that they must have only two character extensions beyond the dot.

I ran into the same problem on our Suns running SunOS 3.5.  After some
experimentation, I discovered that "man" is very picky about what suffixes it
will find, and the permissible possiblilities vary from section to section of
the manual.  For example, in sections "local" and "public" (manl and manp),
the only suffixes man seems to find are ".l" and ".p", respectively.  Suffixes
like ".3" or ".pX" or ".3X11" just plain don't work in manl and manp. In our
case, we wanted to keep all of the X man pages in "manp" to segregate them
from everything else.  It makes maintenance easier, and reduces confusion and
potential name conflicts.  I also tried creating a /usr/man/manX, but "man"
refused to look in there either.  

So it would appear that the "install.man" entries in the doc/Xlib/Xman and
doc/Xt/Xtman Imakefiles should be using "LibManSuffix" as the suffix for the
installed man pages.  The "expand.names" files would need to be modified
accordingly, preferably by some automated procedure.

VERY minor gripe:  The "expand.names" scripts should be run automatically
if "ExpandManNames" is set in the appropriate *.macros or site.def files.  It
looks like the hooks are all there, but just didn't get carried all the way
through.

Tom Crockett

--------------------------------------------------------------------------------
Institute for Computer Applications in Science and Engineering
M.S. 132C, NASA Langley Research Center
Hampton, VA  23665

e-mail:  tom@icase.edu		phone:   (804) 865-4097
--------------------------------------------------------------------------------