Printing a list of all my fonts

[Frizzylee]

Is it possible to print a list of all my existing fonts (for quick reference)
in the style of each particular font? In other words, Arial looks like
Arial, Helvetica looks like Helvetica, etc.

Thanks in advance for help with this.

 

[Jay Freedman]

Is it possible to print a list of all my existing fonts (for quick
reference) in the style of each particular font? In other words,
Arial looks like Arial, Helvetica looks like Helvetica, etc.

Thanks in advance for help with this.

See http://www.word.mvps.org/FAQs/Formatting/FontSampleGenerator.htm.

--
Regards,
Jay Freedman
Microsoft Word MVP
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

 

[Reitanos]

Here's a simple macro:

Sub WriteFontList()
For Each fname In FontNames
With Selection
.Font.Name = "Tahoma"
.Font.Size = 12
.ParagraphFormat.SpaceBefore = 6
.TypeText fname
.TypeText ": "
.Font.Size = 12
.Font.Name = fname
.TypeText "The Quick Brown Fox"
.TypeText Text:=Chr(13)
End With
Next fname
End Sub

 

[JoAnn Paules]

I use something else but will that tell you what's similar to another font?

--

JoAnn Paules
MVP Microsoft [Publisher]
Tech Editor for "Microsoft Publisher 2007 For Dummies"

 

[Jay Freedman]

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". ;-)

I use something else but will that tell you what's similar to another font?

--

JoAnn Paules
MVP Microsoft [Publisher]
Tech Editor for "Microsoft Publisher 2007 For Dummies"

See http://www.word.mvps.org/FAQs/Formatting/FontSampleGenerator.htm.

--
Regards,
Jay Freedman
Microsoft Word MVP
Email cannot be acknowledged; please post all follow-ups to the newsgroup
so all may benefit.

 

[Bob Buckland ?:-\)]

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=-O...LC2cfm7&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>.

============
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". ;-) <<
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Jay Freedman]

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.

 

[Bob Buckland ?:-\)]

Hi Jay,

When you see all of the things that go on and all the different combinations of devices and outside factors that can be involved
(including the ability to type the name of a non-existant font into Word and have it 'use it' <g>) it's fairly amazing that
everything works as well as it does

The link to W3 would have worked if I could type <g> onto computer 'a', what I'm reading on the screen from computer 'b'
Try this one
http://www.w3.org/Printing/stevahn.html

==============
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 >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*