<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>John,</div><div><br></div><div>I see name ID 2 as simply the user-facing string associated with the face in a 4-face style-linked grouping.</div><div><br></div><div>I don't see a problem with this user-facing string indicating the "true" weight of that face, e.g. "Semibold", if that’s what the foundry wants. The font engine shouldn't have any use for this string except as a UI label; the underlying style bits (or weight class and friends) should be what matter, and should be set appropriately. Also, the usual name table localizations should apply.</div><div><br></div><div>That said, its wording is definitely stale, and I'd welcome a proposal to tighten it, though what you suggest goes excessively far, IMO.</div><div><br></div><div>Also, I should say that an app UI that does have 4-face style groupings could express the styles as name ID 2 (whatever its contents), as a hard-coded string corresponding to the style bits ("Regular", "Bold", etc), as two buttons or checkboxes, or other means – an app isn't *required* to use name ID 2.</div><div><br></div><div>Sairus</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> John Hudson <<a href="mailto:john@tiro.ca">john@tiro.ca</a>><br><span style="font-weight:bold">Organization: </span> Tiro Typeworks<br><span style="font-weight:bold">Date: </span> Monday, June 24, 2013 12:24 PM<br><span style="font-weight:bold">Cc: </span> "<a href="mailto:mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>" <<a href="mailto:mpeg-OTspec@yahoogroups.com">mpeg-OTspec@yahoogroups.com</a>><br><span style="font-weight:bold">Subject: </span> [mpeg-OTspec] Tighten name ID 2 spec?<br></div><div><br></div><div><div style="background-color: #fff;"><span style="display:none"> </span>
<div id="ygrp-text">
<p>OpenType name table ID 1 (Font Family name) and ID 2 (Font Subfamily <br>
name) together provide for style-linking in simple four-style families. <br>
This is explicit in the spec for ID 1:<br><br>
Font Family name. Up to four fonts can share the<br>
Font Family name, forming a font style linking group<br>
(regular, italic, bold, bold italic - as defined by<br>
OS/2.fsSelection bit settings).<br><br>
However, the spec for ID 2 refers also to weight differences other than <br>
regular and bold:<br><br>
Font Subfamily name. The Font Subfamily name<br>
distiguishes[sic] the font in a group with the same<br>
Font Family name (name ID 1). This is assumed to<br>
address style (italic, oblique) and weight (*light*,<br>
bold, *black*, etc.). A font with no particular<br>
differences in weight or style (e.g. medium weight,<br>
not italic and fsSelection bit 6 set) should have<br>
the string “Regular” stored in this position.<br><br>
I believe this is a mistake, and that name ID 2 should be more strictly <br>
defined as being one of the four basic styles Regular, Italic, Bold or <br>
Bold Italic, in accordance with the corresponding OS/2.fsSelection setting.<br><br>
JH<br><br>
-- <br><br>
Tiro Typeworks www.tiro.com<br>
Gulf Islands, BC <a href="mailto:tiro%40tiro.com">tiro@tiro.com</a><br><br>
The criminologist's definition of 'public order<br>
crimes' comes perilously close to the historian's<br>
description of 'working-class leisure-time activity.'<br>
- Sidney Harring, _Policing a Class Society_<br></p>
</div>
</div></div><!-- end group email --></span></body></html>