XFree86 4.3.0 anti-alias font problem

From: Doug Poland (doug_at_polands.org)
Date: 05/31/03

  • Next message: Steven Lake: "My scroll wheel on my mouse won't work!!" 
    Date: Sat, 31 May 2003 07:33:51 -0500
To: questions@freebsd.org

    Hi,

    I'm on a 4.8-STABLE box with XFree86 4.3.0. I'm going through the handbook
    (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-fonts.html)
    and adding anti-aliased fonts to my system.

    The problem I'm having is adding TrueType and the bitstream-vera fonts
    to my fontpath via xset.

    Following the handbook, I've...

    * Created the directory: /usr/X11R6/lib/X11/fonts/TrueType
    * Copied .ttf fonts from my windows partition to above directory
    * run the following command: ttmkfdir > fonts.dir

    I do get a message from ttmkfdir which states:
            "unknown font foundry code SYRC"

    A look at the files in the directory reveals nothing remotely similar
    to SYRC. The fonts.dir file appears valid but admittedly I'm not sure
    what I'm looking at.

    To continue, when I run:

    * xset fp+ /usr/X11R6/lib/X11/fonts/TrueType

    I see:

            xset: bad font path element (#64), possible causes are:
                    Directory does not exist or has wrong permissions
                    Directory missing fonts.dir
                    Incorrect font server address or syntax

    In my case, the directory does exist and has the same permissions as
    the other font directories. The fonts.dir file does exist. And I'm
    not sure what the 3rd possible cause is.

    Curiously, I get the exact same error when I try to add the
    bitstream-vera fonts (added via x11-fonts/bitstream-vera port) to the
    fontpath.

    * xset fp+ /usr/X11R6/lib/X11/fonts/bitstream-vera/
      xset: bad font path element (#64), possible causes are:
      Directory does not exist or has wrong permissions
      Directory missing fonts.dir
      Incorrect font server address or syntax

    I must be missing something here. Does anyone have any suggestions? 

    -- 
Regards,
Doug
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Steven Lake: "My scroll wheel on my mouse won't work!!"

    Relevant Pages

    • Re: [SLE] Installing bitmap fonts (Second Post) on Suse 8.0
      ... "man xset" explains the "fp rehash" - it fits your situation. ... > installed .ttf fonts with help received from this ... Now I want to install fonts in .fon file. ...
      (SuSE)
    • Re: Installing new fonts on SunOS 5.9
      ... contains different subdirectories with fonts. ... but I still have the same problem with xset. ... Fatal Error: No listening sockets established. ... Why sometimes this command goes ...
      (comp.unix.solaris)
    • x3270 fonts not loading
      ... install I can't get the default fonts to get picked ... The iso fonts are getting picked up fine. ... run through the xset commands ... Discover Yahoo! ...
      (SunManagers)
    • Re: unicode not appearing correctly
      ... > both systems and compare outputs. ... "xset q" does look useful. ... The problem is not what's different with the fonts between the two ... So the difference is between my login/setup and my ...
      (comp.lang.tcl)
    • xset: bad font path element (#305)
      ... I recently installed fluxbox on my account at my university ... special set of fonts. ... I downloaded the fonts and I've done exactly as it ... $ xset fp+ $HOME/.fonts ...
      (comp.unix.questions)