Comments on: Font terms survey results http://www.thomasphinney.com/2009/04/font-terms-survey-results/ the Phinney-us Blog on Typography & Text Wed, 11 Aug 2010 21:30:01 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: A font by any other name? | Phinney on Fonts http://www.thomasphinney.com/2009/04/font-terms-survey-results/comment-page-1/#comment-215 A font by any other name? | Phinney on Fonts Sat, 18 Apr 2009 00:42:03 +0000 http://www.thomasphinney.com/?p=236#comment-215 [...] Font terms survey results [...] [...] Font terms survey results [...]

]]> By: rm http://www.thomasphinney.com/2009/04/font-terms-survey-results/comment-page-1/#comment-208 rm Wed, 08 Apr 2009 16:00:57 +0000 http://www.thomasphinney.com/?p=236#comment-208 I'm a little inebriated, but, all this info exists in texts that have been published. People just don't know where to look for it. Refer to Robert Bringhurst for a complete and thorough system of classification. I’m a little inebriated, but, all this info exists in texts that have been published.
People just don’t know where to look for it.
Refer to Robert Bringhurst for a complete and thorough system of classification.

]]> By: Font terms survey results, Thomas Phinney | FontSite, an OpenType Font Resource http://www.thomasphinney.com/2009/04/font-terms-survey-results/comment-page-1/#comment-205 Font terms survey results, Thomas Phinney | FontSite, an OpenType Font Resource Tue, 07 Apr 2009 16:23:41 +0000 http://www.thomasphinney.com/?p=236#comment-205 [...] The results-are-in! the inestimable Thomas [my other car is a sans serif] Phinney with the findings from his own Font terms survey. [...] [...] The results-are-in! the inestimable Thomas [my other car is a sans serif] Phinney with the findings from his own Font terms survey. [...]

]]> By: johno http://www.thomasphinney.com/2009/04/font-terms-survey-results/comment-page-1/#comment-189 johno Mon, 06 Apr 2009 09:07:40 +0000 http://www.thomasphinney.com/?p=236#comment-189 Many thanks for putting this together. A little surprised by some of the results. Perhaps I'll return when I've finished digesting it all. The jaw surgery sounds incredibly painful. Hoping that you make a speedy recovery. Many thanks for putting this together. A little surprised by some of the results. Perhaps I’ll return when I’ve finished digesting it all.

The jaw surgery sounds incredibly painful. Hoping that you make a speedy recovery.

]]> By: Adam Twardoch http://www.thomasphinney.com/2009/04/font-terms-survey-results/comment-page-1/#comment-182 Adam Twardoch Sat, 04 Apr 2009 10:16:09 +0000 http://www.thomasphinney.com/?p=236#comment-182 Thank you, Thomas, for your wonderful work. Below is an excerpt of some documentation I've been working on for future versions of FontLab products. We will stick to "styling group" simply because it is shorter than "style-linked group", fits better with UI requirements. I realize it's a new, not yet established term, so people are obviously not familiar with it. But I hope through the dissemination of our future products, the terms will become more familiar. So, below is the relevant part of my write-up. A complete version will be included in the manuals of our products, and perhaps also in a separate whitepaper. == Traditionally, the Mac OS platform has always allowed typographic family grouping of fonts: an arbitrary number of fonts can appear in the font menu under one family name, with every font having a distinctive style name. This allows typographically authentic representation of font families. Many font families consist of a number of styles with different weights (light, regular, semibold, bold, black etc.), sometimes different widths (condensed, normal, extended) and often with accompanying italic styles. Some of the fonts within one family are linked together through styling links, also known under the name “style-linking associations”. A typical styling link is “this font acts as the bold style of another font” and “this font acts as the italic style of another font”. Through styling links, the application knows which font should be used when the user applies italic or bold formatting — typically through clicking on an “I” or “B” icon in the application’s toolbar. Some fonts within the typographic family are associated with each other through styling links that have two properties: “is bold” and “is italic”. All fonts that are associated with each other through styling links form a styling group. The styling group name is the name that appears in Windows GDI applications as the family name. It is sometimes called “Windows family name” or “Microsoft menu name”. The typographic family must be divided into styling groups, each having no more than four members which all must be connected by styling links with each other. Each styling group within a typographic family must have a unique name. The styling link name is the name that appears in Windows GDI applications as the style name. It is sometimes called “Windows style name”. Thank you, Thomas, for your wonderful work.

Below is an excerpt of some documentation I’ve been working on for future versions of FontLab products. We will stick to “styling group” simply because it is shorter than “style-linked group”, fits better with UI requirements.

I realize it’s a new, not yet established term, so people are obviously not familiar with it. But I hope through the dissemination of our future products, the terms will become more familiar.

So, below is the relevant part of my write-up. A complete version will be included in the manuals of our products, and perhaps also in a separate whitepaper.

==

Traditionally, the Mac OS platform has always allowed typographic family grouping of fonts: an arbitrary number of fonts can appear in the font menu under one family name, with every font having a distinctive style name. This allows typographically authentic representation of font families. Many font families consist of a number of styles with different weights (light, regular, semibold, bold, black etc.), sometimes different widths (condensed, normal, extended) and often with accompanying italic styles.

Some of the fonts within one family are linked together through styling links, also known under the name “style-linking associations”. A typical styling link is “this font acts as the bold style of another font” and “this font acts as the italic style of another font”. Through styling links, the application knows which font should be used when the user applies italic or bold formatting — typically through clicking on an “I” or “B” icon in the application’s toolbar.

Some fonts within the typographic family are associated with each other through styling links that have two properties: “is bold” and “is italic”.

All fonts that are associated with each other through styling links form a styling group. The styling group name is the name that appears in Windows GDI applications as the family name. It is sometimes called “Windows family name” or “Microsoft menu name”.

The typographic family must be divided into styling groups, each having no more than four members which all must be connected by styling links with each other. Each styling group within a typographic family must have a unique name.

The styling link name is the name that appears in Windows GDI applications as the style name. It is sometimes called “Windows style name”.

]]>