Re: Getting started on Fedora9

On Mon, 2008-10-27 at 13:50 +0000, Dan Hatton wrote:
> On Mon, 27 Oct 2008, Enrique Perez-Terron wrote:
> 
> > (HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-bold-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-bold-o-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-medium-o-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> > (HyperDoc) Cannot load font -adobe-courier-bold-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
> 
> This is a bit of a stab in the dark, but...
> 
> Does your system contain a file
> 
> /etc/X11/fs/config.rpmnew
> 
> ?

Hey, I did not even have xfs installed at all. I did not know that I did
not have it. So I thought you had a very good point. Thanks!

But after installing, the only change was that now the number of error
messages was reduced:

(HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
(HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.
(HyperDoc) Cannot load font -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso8859-1 ; using default.

Then I checked if xfs was listening on a tcp port, and it was not. (Of
course.) But just to make sure, I enabled the tcp port and restarted the
xfs daemon. This time, all seven error messages were present.  No joy.

Next I came to think of the old program xlsfonts.

Ha! I have the unicode version:

  -adobe-courier-medium-r-normal--18-*-*-*-m-*-iso10646-1

but not iso8859.

Some old memories came trickling back... xfs is quite obsolete these
days. I stopped xfs, and ran xlsfonts again. All the same fonts as
before are present.

So thanks again, I may well be on the track now. I just have to find out
how to have my system offer some iso8859 fonts.

Ugh, I already have that also, only not in size 18:

  $ xlsfonts | grep adobe-courier.\*8859
  -adobe-courier-bold-o-normal--11-80-100-100-m-60-iso8859-1
  -adobe-courier-bold-o-normal--14-100-100-100-m-90-iso8859-1
  -adobe-courier-bold-o-normal--17-120-100-100-m-100-iso8859-1
  -adobe-courier-bold-o-normal--20-140-100-100-m-110-iso8859-1
  -adobe-courier-bold-o-normal--25-180-100-100-m-150-iso8859-1
  -adobe-courier-bold-o-normal--34-240-100-100-m-200-iso8859-1
  -adobe-courier-bold-r-normal--11-80-100-100-m-60-iso8859-1
  -adobe-courier-bold-r-normal--14-100-100-100-m-90-iso8859-1
  -adobe-courier-bold-r-normal--17-120-100-100-m-100-iso8859-1
  -adobe-courier-bold-r-normal--20-140-100-100-m-110-iso8859-1
  -adobe-courier-bold-r-normal--25-180-100-100-m-150-iso8859-1
  -adobe-courier-bold-r-normal--34-240-100-100-m-200-iso8859-1
  -adobe-courier-medium-o-normal--11-80-100-100-m-60-iso8859-1
  -adobe-courier-medium-o-normal--14-100-100-100-m-90-iso8859-1
  -adobe-courier-medium-o-normal--17-120-100-100-m-100-iso8859-1
  -adobe-courier-medium-o-normal--20-140-100-100-m-110-iso8859-1
  -adobe-courier-medium-o-normal--25-180-100-100-m-150-iso8859-1
  -adobe-courier-medium-o-normal--34-240-100-100-m-200-iso8859-1
  -adobe-courier-medium-r-normal--11-80-100-100-m-60-iso8859-1
  -adobe-courier-medium-r-normal--14-100-100-100-m-90-iso8859-1
  -adobe-courier-medium-r-normal--17-120-100-100-m-100-iso8859-1
  -adobe-courier-medium-r-normal--20-140-100-100-m-110-iso8859-1
  -adobe-courier-medium-r-normal--25-180-100-100-m-150-iso8859-1
  -adobe-courier-medium-r-normal--34-240-100-100-m-200-iso8859-1

OK, now I have looked in the source, and found that hyperdoc accepts
font settings in .Xdefaults, and I have set all the font variables to 17
pixels instead of 18.

This time there are no error messages, but still no window!!

I have now tried to make a new axiom from the source corresponding to
the binary tar file, but it does not build. I appears to have a couple
of problems, which seem to originate in the "configure" script in the
common lisp source tree. The makefile writes a shell script that tries
to "exec" a directory.  There should have been a program name after that
directory, but the Make variable has not been set. The configure script
has code to set this variable....

Perhaps the source tarball was not correctly cleaned. There also appears
to be some leftovers from a debian customization.  It is not likely that
debian files and patches should be present in a tarball prepared for
Fedora.

I guess I will return to this next week or so. 

Thanks anyway.

-Enrique