From Bugzilla Helper: User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-3 i586) Description of problem: The buildfontlist function uses ttmkfdir if there are any ttf fonts to build a fonts.scale, from which fonts.dir is constructed. But if there are .pfb fonts in the same directory, they are ignored. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Put both .ttf and .pfb files in a directory 2. Add the directory to the catalogue for xfs 3. restart xfs Actual Results: The fonts.{scale,dir} files generated will not record the .pfb files. The existing *correct* fonts.scale and fonts.dir files have been overwritten. Grrrr. Expected Results: Both ttf and pfb files should be listed in fonts.{scale,dir} Additional info: Putting ttf and pfb files into separate directories is not an option for /usr/share/AbiSuite/fonts.
This is not supported. Put ttf files in one directory, and type1 in another directory. We do not support putting mixed types of fonts in one directory at this time.
The following procedure seems to work for Abiword. Clear out everything from /usr/share/AbiSuite/fonts, putting all the fonts one wants to use in Abiword in appropriate other directories, and link to them (and the corresponding .afms) from /usr/share/AbiSuite/fonts. Construct suitable fonts.scale and fonts.dir and use ttfadmin as described in the abiword documentation. The crucial point now is to add the other font directories to the font path but *not* /usr/share/AbiSuite/fonts which may contain both .pfb and .ttf links and which the Red Hat xfs init script would mess up. As long as all the fonts are available, Abiword is happy.