Re: Parsing of fontconfig font names and other font related stuff.

[Kenichi Handa]

In article <address@hidden>, =?ISO-8859-1?Q?Jan_Dj=E4rv?= <address@hidden> 
writes:

> Actually it is too late to add DPI in xftfont.c, because it must be added 
> long 
> before that.  Font.c does DPI calculations all over the place, and assumes 
> that either dpi=... is given in the font spec, or that the DPI for the 
> monitor 
> can be used.  In fact, it is either 75 (fontconfig default) or 96 (GNOME 
> default) that is used, so font.c is wrong (wrong == different from other 
> applications) when a plain font name like monospace-8 is given.

Ah, sure.

> It would be nice to be able to use XftDefaultSubstitute to pick up the GConf 
> settings from the X database (GConf puts them there).  But by the time the 
> Xft 
> driver has been choosen, the pixel size for the font has already been 
> calculated, using another dpi-value.

> How can we fix this?  Can we choose driver without calculating a pixel size?

I think it's not that difficult of modify the current code
to do that, but...

> The fast but kind of ugly way would be to add the defaults from 
> XftDefaultSubstitute to the name if it is an fcname and Xft is present.

shouldn't the DPI value from GConf be reflected to (struct
x_display_info).resy or (struct frame).resy?

---
Kenichi Handa
address@hidden