Date: Mon, 13 Jun 2005 09:51:43 -0400 From: Mikhail Teterin <mi+kde@aldan.algebra.com> To: Dejan Lesjak <dejan.lesjak@ijs.si>, freebsd-x11@freebsd.org Subject: Re: bug in mkfontdir? Message-ID: <200506130951.44130@aldan> In-Reply-To: <200506131430.30430.dejan.lesjak@ijs.si> References: <200506111506.j5BF6obi014607@aldan.algebra.com> <200506131430.30430.dejan.lesjak@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 13 June 2005 08:30 am, you wrote: = > For example, the x11-fonts/gemini-fonts port creates PCF files from = > BDF sources and then runs mkfontdir to create fonts.dir. = > = > With XFree86's mkfontdir the file will begin with the number 68 and = > list the PCFs only -- as per the mkfontdir(1). = > = > With Xorg's, the file begins with 136 and each font ends up listed twice: = > = > [...] = > gem1c.bdf -gemini-courier-medium-r-normal--8-80-75-75-m-50-koi8-u = > gem1c.pcf.gz -gemini-courier-medium-r-normal--8-80-75-75-m-50-koi8-u = > gem1cb.bdf -gemini-courier-bold-r-normal--8-80-75-75-m-50-koi8-u = > gem1cb.pcf.gz -gemini-courier-bold-r-normal--8-80-75-75-m-50-koi8-u = > [...] = > = > Is this something, I should only talk about with the Xorg people? = = Hm, does this cause any trouble with using fonts or does it only = generate larger file? It is a problem. When the BDF is present it results in the inefficiency of using it instead of the binary-tailored PCF. The worst is, however, when the BDF is not installed at all -- font name will be listed (as in xlsfonts), but the server will refuse to use it... I had gemini-fonts in front of my fontpath (for koi8-u enoding). After switching to Xorg, most of the fonts stopped working in xterm :-( -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506130951.44130>