All fonts from Type1 subdirectory ("ult1mo" registry) of this package when selected in a font selector (stand-alone gfontsel or from gnome-terminal) result only in an error message "This font is not available" or something of that sort (from memory). The same fonts when used with gfontsel from RH 6.2 distribution are simply crashing that application. There are no such such troubles with "ult1mo" fonts when they are replaced by XFree86-ISO8859-2-Type1-fonts-1.0-12.noarch.rpm package from RH7 distribution. As an aside my old #27072 report about fonts (look at pictures attached to it) does not seem to be resolved at all even if a final release seems to be very close. Michal michal
The XFree86-ISO8859-2 was obsoleted in the development cycle post Guinness. I've changed the package component to reflect this, as this is the first time I've seen this bug report. The functionality was incorporated into XFree86, however it seems it is not done completely correctly. I will look into this issue deeper when I have time to delve into the complexities of XFree86 font generation, etc..
The XFree86 package itself,and all subpackages produced contain only fonts that come from XFre86.org sources now. All other fonts are in their own external packages and no packages have XFree86 in their name unless they are part of XFree86. All font packages external to X are now named fonts-* or ttfonts-* (or should be). The new package for these fonts is fonts-ISO8859-2 in rawhide. Please let me know if this package is broken, as I believe it to be ok now.
See #60641 for a solution.
> The new package for these fonts is fonts-ISO8859-2 in rawhide. These all are bitmaps fonts in a pcf.gz format. Although their presence is nice we are talking here about scalable fonts and problems with the later seem to be "solved" by removing them from subsequent distributions. Web browsers, for example, have a hard time with bitmap fonts.