|
↑ ↑ ↑ ✔ This
I suspect what's happened is that MS wanted to get rid of "Substitute Fonts". But rather than ditching them holus-bolus it has left enough in place to maintain backwards compatibility for older applications, but discouraged ongoing use of the 'feature' in recently developed/updated applications.
MS tries to maintain backwards compatibility, which allows people like me to run 25 year old software on the current version of Windows. Some platforms wont even run software developed 10 years ago let alone last century.
@Lauraq - have a look at MS Reference Sans Serif, to my not very good eyes it seems a bit 'sharper' than my MS Shell Dlg2 (Tahoma).
BR
|