Re: [Bug: 21.5-b22] xft xemacs discards info about current dpi
Stephen J. Turnbull writes:
>>>>> "giacomo" == giacomo boffi
<giacomo.boffi(a)polimi.it> writes:
giacomo> XEmacs uses FcDefaultSubstitute [1] and that's a
giacomo> candidate for something consistent about that
No; FcDefaultSubstitute cannot handle *your* display *at all*; it
handles whatever Keith Packard thinks is the lowest common demoninator
(75dpi, in fact).
oh my, i was not suggesting that XEmacs should use
FcDefaultSubstitute! on the contyrary, i tried to point out that the
problem that XEmacs has with fonts *IS* FcDefaultSubstitute!
--- src/objects-x.c~ 2005-09-26 17:41:08.000000000 +0200
+++ src/objects-x.c 2005-09-28 09:13:56.393480744 +0200
＠＠ -1242,7 +1242,7 ＠＠
/* The order is correct according the fontconfig docs. */
FcConfigSubstitute (fcc, p, FcMatchPattern);
PRINT_XFT_PATTERN (2, "FcConfigSubstitute'ed name is %s\n", p);
- FcDefaultSubstitute (p);
+ /* FcDefaultSubstitute (p); */
PRINT_XFT_PATTERN (3, "FcDefaultSubstitute'ed name is %s\n", p);
/* #### check fcresult of following match? */
fontxft = FcFontMatch (fcc, p, &fcresult);
the above patch cured the wrong pixel sizes, AND the bold-italic
problem that i reported yesterday