Jay
Tue Jul 15 18:56:33 PDT 2008
Thanks, Bob. FYI, the link to w3.org doesn't work any more (the page might have
been moved to their archive). The MSDN link was very informative, though
(fortunately I'm not freaked by complicated structures in C++).
From some of the results I've seen, I'll guess that many amateur fonts and even
a fair number of commercial ones contain either erroneous Panose data or none at
all. That experience was the basis for my original comment.
--
Jay
On Tue, 15 Jul 2008 18:04:04 -0700, "Bob Buckland ?:-\)" <75214.226(At
Beautiful Downtown)compuserve.com> wrote:
>Hi Jay,
>
>Welll, since you 'asked' ;)
>it's actually Windows Graphic Device Interface (GDI) rather than Office that determines(?) 'similarity' using Panose mapping :)
>
>
http://support.microsoft.com/kb/918791 (search on Panose)
>
>
http://www.w3.org/Pringint/steveahn.html (Thumbnail overview)
>
>
http://msdn.microsoft.com/en-us/library/ms533998(VS.85).aspx (coding)
>
>Example of how the Similarity lookup works:
>
>
http://books.google.com/books?id=-O92IIF1Bj4C&pg=RA9-PA909&lpg=RA9-PA909&ots=SwWLC2cfm7&sig=hEJLl5waOW65cmNh_F5Sg9zGQ74&hl=en
>
>The TextMetric structure used to figure out how to match what you see on screen, on differing devices, to the printing devices,
>after determining which font each actually has or can 'look like' it has so that the view and print more or more or less match is
>pretty involved <g>.
>
>============
> <<"Jay Freedman" <jay.freedman@verizon.net> wrote in message news:6acq74l4h651nidou4tt69ovvpt90ondoi@4ax.com...
>No, it's similar to the macro posted by Reitanos -- it just prints a sample of
>each font.
>
>Anyway, I defy anyone to explain the rule Word uses to decide what fonts are
>"similar". ;-) <<