On 2015-03-09 11:25 (+0100), jazzynico wrote:
> Note that generic fonts are a fallback mechanism, and that Inkscape
> maps the font to a real font.
AFAIU that mapping is actually done by fontconfig (0.91 uses that
instead of the win32 backend for pango on Windows).
> Weirdly, the font preview (in the Text and font dialog) shows an
> Arial font when the invalid Sans font is selected...
Similar mismatches are also observed on OS X (if using GTK+/Quartz and
pango's coretext backend) - the font preview in the 'Text and Font'
dialog in 0.91 seems to no longer use the same internal rendering as
on-canvas as before the merge of the cairo-rendering branch, and
apparently is not based on the same init or configration information as
the fontconfig-based pango backend (used on-canvas).
On 2015-03-09 11:25 (+0100), jazzynico wrote:
> Note that generic fonts are a fallback mechanism, and that Inkscape
> maps the font to a real font.
AFAIU that mapping is actually done by fontconfig (0.91 uses that
instead of the win32 backend for pango on Windows).
> Weirdly, the font preview (in the Text and font dialog) shows an
> Arial font when the invalid Sans font is selected...
Similar mismatches are also observed on OS X (if using GTK+/Quartz and
pango's coretext backend) - the font preview in the 'Text and Font'
dialog in 0.91 seems to no longer use the same internal rendering as
on-canvas as before the merge of the cairo-rendering branch, and
apparently is not based on the same init or configration information as
the fontconfig-based pango backend (used on-canvas).