That's great news about the font licensing if it goes ahead: I've been suffering serious font envy ever since I started reading your blog.
As for the difference, I'm woefully ignorant of typography, but in the second example it looks as if the numerals are rendered as lower-case characters with acenders and descenders, and in the first example they're um, not.
Kevin Daly
· 4 years ago
Sorry, *ascenders (crap keyboard).
Adam T
· 4 years ago
I use Windows XP SP-2 where I've installed the Avalon Beta 1 and the corresponding WinFX SDK. I'm testing the XAML samples in XAMLPad but somehow cannot get most of my system-installed fonts to show up in the XAML. works fine but does not (the font is, of course, installed in Windows XP's system folder. The only way I actually got Bickham Script Pro to render *somehow* in Avalon is but of course this is not the idea.
Is there some additional magic I need to do so the XAMLPad output sees all the fonts installed on my system? Alternatively, is there a way to reference URIs in the FontFamily attribute?
Adam
Adam T
· 4 years ago
I figured it out. It worked when I specified "Bickham Script Pro Regular" instead of "Bickham Script Pro" as FontFamily. It looks that Avalon Beta 1 running in Windows XP SP-2 uses a different set of font names than Avalon running in Longhorn that you presumably use (name id 1 vs. 16). Might be worth looking at.
All Comments
As for the difference, I'm woefully ignorant of typography, but in the second example it looks as if the numerals are rendered as lower-case characters with acenders and descenders, and in the first example they're um, not.
Is there some additional magic I need to do so the XAMLPad output sees all the fonts installed on my system? Alternatively, is there a way to reference URIs in the FontFamily attribute?
Adam
Regards,
Adam