<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
The current spec says, in the post table format 2.0, that:<br>
<br>
<span style="color: rgb(0, 0, 0); font-family: Georgia, 'Times
New Roman', Times, serif; font-size: 13px; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing: normal;
line-height: normal; orphans: 2; text-align: start; text-indent:
0px; text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-size-adjust: auto;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); display: inline !important; float: none;">Index numbers
32768 through 65535 are reserved for future use.<span
class="Apple-converted-space"> <br>
<br>
<br>
</span></span>This effectively limits fonts to 32K glyphs unless
we want to abandon any hope of extracting usable texts from glyph
streams. In any case, having to ensure no more than 32K glyphs have
postscript names makes font development more difficult.<br>
<br>
You might ask: why don't I just put the postscript names in there
anyway? The reason is that products like Firefox are being more
stringent about what fonts are acceptable, especially for web fonts,
and fonts that have glyph name IDs greater than 32767 are being
rejected because they violate this clause of the standard.<br>
<br>
Is there any reason to continue to reserve IDs 32768 through 65535?
Or is the future here and we should start permitting those IDs?<br>
<br>
Bob Hallissy<br>
<br>
</body>
</html>