Charles Philip Chan <cpchan@sympatico.ca> さんは書きました:
On February 5, 2003 10:20 am, Mike FABIAN wrote:
Sorry about the last message... hit the wrong button ;-(.
How does the XLFD of this font look like?
Here is the full version:
% postscript="AllegroBT-Regular" family="Allegro BT" style="Regular" % xlfd="-Bitstream-Allegro-medium-r-condensed--0-0-0-0-p-0-iso8859-9" /AllegroBT-Regular (/usr/X11R6/lib/X11/fonts/truetype/allegron.ttf) ; /Allegro /AllegroBT-Regular ;
This doesn't work with the /AllegroBT-Regular font? Why not? Why does Qt think it is /AllegroBt if the XLFD doesn't have "Allegro BT" in the family name?
The BT is not in the XLFD, but is is in the postscript name.
Hmm. Qt really uses the PostScript name in that case? I could generate aliases form the part of the PostScript name before the '-' as well of course. But that would probably increase the number of duplicate aliases quite a lot. If you have many fonts installed you probably already have some duplicate aliases in Fontmap.X11-auto. I've marked the duplicates in the generated Fontmap.X11-auto by uncommenting the last one and adding "% warning: duplicate!", like that: %---------------------------------------------------------------------- % postscript="ClarendonLHHeavy" family="ClarendonLH" style="Heavy" % xlfd="-misc-ClarendonLH-black-r-normal--0-0-0-0-p-0-iso8859-1" /ClarendonLHHeavy (/usr/X11R6/lib/X11/fonts/test/clarlh__.ttf) ; /ClarendonLH /ClarendonLHHeavy ; /Clarendonlh /ClarendonLHHeavy ; %---------------------------------------------------------------------- % postscript="ClarendonLHLight" family="ClarendonLH" style="Light" % xlfd="-misc-ClarendonLH-light-r-normal--0-0-0-0-p-0-iso8859-1" /ClarendonLHLight (/usr/X11R6/lib/X11/fonts/test/clarll__.ttf) ; % /ClarendonLH /ClarendonLHLight ; % warning: duplicate! % /Clarendonlh /ClarendonLHLight ; % warning: duplicate! %---------------------------------------------------------------------- In that case, Qt probably needs the alias /Clarendonlh in both cases, it looks like it can't distinguish between these two. By the way, because of the possibility of generating aliases which are identical to PostScript names or aliases used in Fontmap.GS, Fontmap.X11-auto should be included at the top of /usr/share/ghostscript/7.05/lib/Fontmap like this %! % See Fontmap.GS for the syntax of real Fontmap files. (Fontmap.X11-auto) .runlibfile (Fontmap.GS) .runlibfile (Fontmap.kanji) .runlibfile (Fontmap.rus) .runlibfile (Fontmap.CID) .runlibfile (Fontmap.greek) .runlibfile because if there are duplicate aliases/PostScript names, the last one wins. And Fontmap.GS, and the other Fontmap.* below may contain handedited stuff, which should always win against the autogenerated stuff in Fontmap.X11-auto. -- Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。