[mpeg-OTspec] Proposal to modify wording for name table ID 6

Sairus Patel sppatel at adobe.com
Fri Jun 13 19:27:00 CEST 2014


Note that there is a correlation between name IDs 6 and 20 in the spec. The bulk of the descriptions could go into the Recommendations section but they shouldn't just be deleted. We'd need more time to figure out how best to refactor/change these spec descriptions.

Sairus

From: "mpeg-OTspec at yahoogroups.com<mailto:mpeg-OTspec at yahoogroups.com>" <mpeg-OTspec at yahoogroups.com<mailto:mpeg-OTspec at yahoogroups.com>>
Reply-To: Joshua Hadley <Joshua.Hadley at monotypeimaging.com<mailto:Joshua.Hadley at monotypeimaging.com>>
Date: Tuesday, June 10, 2014 at 11:23 AM
To: "mpeg-OTspec at yahoogroups.com<mailto:mpeg-OTspec at yahoogroups.com>" <mpeg-OTspec at yahoogroups.com<mailto:mpeg-OTspec at yahoogroups.com>>
Subject: [mpeg-OTspec] Proposal to modify wording for name table ID 6



The wording for the name table, name ID 6, currently reads (in part):
"OpenType fonts which include a name with name ID of 6 shall include these two names with name ID 6, and characteristics as follows:" (goes on to list Mac/Roman and Windows/Unicode entries)

While this may have been true for some implementations in the past (or even today), it is certainly not a requirement for validity of an OpenType font in general. Much of the remaining wording is also very implementation-specific (FOND resources?!?). I'd like to propose a vast simplification of the wording for name ID 6, replacing the entire current entry with:

"Postscript name for the font; Name ID 6 specifies a string which is used to invoke a PostScript language font that corresponds to this OpenType font.

When translated to ASCII, the name string must be no longer than 63 characters and restricted to the printable ASCII subset, codes 33-126, except for the 10 characters '[', ']', '(', ')', '{', '}', '<', '>', '/', '%'.
"

And that's all. If deemed important by stakeholders, the remaining text could be moved to the recommendations section as non-normative, implementation-specific advice.

Thanks,

Joshua Hadley
Monotype


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20140613/2dfee50a/attachment.html>


More information about the mpeg-otspec mailing list