Yes, that is a good additional amendment, IMO.<div><br></div><div>T<br><br><div class="gmail_quote">On Fri, Mar 26, 2010 at 2:01 PM, Levantovsky, Vladimir <span dir="ltr"><<a href="mailto:Vladimir.Levantovsky@monotypeimaging.com">Vladimir.Levantovsky@monotypeimaging.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="white" lang="EN-US" link="#1E66AE" vlink="#1E66AE">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thank you, Thomas.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">All, I would like to ask you to review this proposal and see if
this is something we can reach a consensus on. We do have few more days for
ballot comments to be submitted (until March 30), and we can make this proposal
a part of the ballot comments to be included in the current draft corrigendum.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">On the subject of the proposed amended text – I also
noticed that the UI suggestion section for ‘lnum’ feature
recommends that “</span>This feature should be inactive by default.<span style="font-size:11.0pt;color:#1F497D">”
while the UI suggestion for ‘onum’ is silent about feature default
state. Should we also include the recommendation that the ‘onum’
feature should be inactive by default? This question about unidentified default
state was also asked on the W3C CSS mailing list.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Thank you,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D">Vladimir</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#1F497D"> </span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt">
<a href="mailto:mpeg-OTspec@yahoogroups.com" target="_blank">mpeg-OTspec@yahoogroups.com</a> [mailto:<a href="mailto:mpeg-OTspec@yahoogroups.com" target="_blank">mpeg-OTspec@yahoogroups.com</a>] <b>On Behalf
Of </b>Thomas Phinney<br>
<b>Sent:</b> Friday, March 26, 2010 4:50 PM<br>
<b>To:</b> <a href="mailto:mpeg-OTspec@yahoogroups.com" target="_blank">mpeg-OTspec@yahoogroups.com</a><br>
<b>Subject:</b> [mpeg-OTspec] Suggestion for minor correction on figure styles</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<div>
<div><div><div></div><div class="h5">
<div>
<p>From a conversation between me and John Daggett of Mozilla, on a CSS<br>
mailing list. He wrote:<br>
<br>
> OpenType spec just says "Users can switch between the lining and<br>
> oldstyle sets by turning this feature on or off."<br>
><br>
> I think that may be a bug in the spec, if a designer uses old-style<br>
> figures as the default glyphs for numerals then the statement above<br>
> will be incorrect.<br>
<br>
He is of course correct. Further, the default figures in a typeface<br>
may be neither lining nor oldstyle, but in between or something else!<br>
To allow for default figures that are non-lining, or even neither<br>
lining nor oldstyle, I have made a more formal proposal out of my<br>
response.<br>
<br>
Currently the 'lnum' and 'onum' feature tags in 6.4.3.2 "Feature<br>
descriptions and implementations," include the following language<br>
(assuming they are the same as the current OT spec).<br>
<br>
LNUM<br>
<br>
Function: This feature changes selected figures from oldstyle to the<br>
default lining form.<br>
Example: The user invokes this feature in order to get lining figures,<br>
which fit better with all-capital text. Various characters designed to<br>
be used with figures may also be covered by this feature. In cases<br>
where lining figures are the default form, this feature would undo<br>
previous substitutions.<br>
Recommended implementation: The lnum table maps each oldstyle figure,<br>
and any associated characters to the corresponding lining form (GSUB<br>
lookup type 1).<br>
Application interface: For GIDs found in the lnum coverage table, the<br>
application passes a GID to the onum table and gets back a new GID.<br>
Even if the current figures resulted from an earlier substitution, it<br>
may not be correct to simply revert to the original GIDs, because of<br>
interaction with the figure width features, so it's best to use this<br>
table.<br>
UI suggestion: This feature should be inactive by default. Users can<br>
switch between the lining and oldstyle sets by turning this feature on<br>
or off. Note that this feature is distinct from the figure width<br>
features (pnum and tnum). When the user invokes this feature, the<br>
application may wish to inquire whether a change in width is also<br>
desired.<br>
<br>
ONUM<br>
<br>
Function: This feature changes selected figures from the default<br>
lining style to oldstyle form.<br>
Example: The user invokes this feature to get oldstyle figures, which<br>
fit better into the flow of normal upper- and lowercase text. Various<br>
characters designed to be used with figures may also have oldstyle<br>
versions.<br>
Recommended implementation: The onum table maps each lining figure,<br>
and any associated characters, to the corresponding oldstyle form<br>
(GSUB lookup type 1).<br>
Application interface: For GIDs found in the onum coverage table, the<br>
application passes a GID to the onum table and gets back a new GID.<br>
UI suggestion: Users can switch between the lining and oldstyle sets<br>
by turning this feature on or off. Note: This feature is separate from<br>
the figure-width features pnum and tnum. When the user changes figure<br>
style, the application may want to query whether a change in width is<br>
also desired.<br>
Script/language sensitivity: None.<br>
Feature interaction: This feature overrides the results of the Lining<br>
Figures feature (lnum).<br>
<br>
I hereby propose those sections of these two feature descriptions be<br>
replaced as follows. (Note that this also corrects a typo in the<br>
"lnum" application interface description, where onum was incorrectly<br>
referenced. Note also that there are parts both before and after the<br>
blocks I am amending, which can remain untouched.)<br>
<br>
LNUM<br>
<br>
Function: This feature changes selected non-lining figures to lining figures.<br>
Example: The user invokes this feature in order to get lining figures,<br>
which fit better with all-capital text. Various characters designed to<br>
be used with figures may also be covered by this feature. In cases<br>
where lining figures are the default form, this feature would undo<br>
previous substitutions.<br>
Recommended implementation: The lnum table maps each oldstyle figure,<br>
and any associated characters to the corresponding lining form (GSUB<br>
lookup type 1). If the default figures are non-lining, they too are<br>
mapped to the corresponding lining form.<br>
Application interface: For GIDs found in the lnum coverage table, the<br>
application passes a GID to the lnum table and gets back a new GID.<br>
Even if the current figures resulted from an earlier substitution, it<br>
may not be correct to simply revert to the original GIDs, because of<br>
interaction with the figure width features, so it's best to use this<br>
table.<br>
UI suggestion: This feature should be inactive by default. Users can<br>
switch between the default and lining figure sets by turning this<br>
feature on or off. Note that this feature is distinct from the figure<br>
width features (pnum and tnum). When the user invokes this feature,<br>
the application may wish to inquire whether a change in width is also<br>
desired.<br>
<br>
ONUM<br>
<br>
Function: This feature changes selected figures from the default or<br>
lining style to oldstyle form.<br>
Example: The user invokes this feature to get oldstyle figures, which<br>
fit better into the flow of normal upper- and lowercase text. Various<br>
characters designed to be used with figures may also have oldstyle<br>
versions.<br>
Recommended implementation: The onum table maps each lining figure,<br>
and any associated characters, to the corresponding oldstyle form<br>
(GSUB lookup type 1). If the default figures are non-lining, they too<br>
are mapped to the corresponding oldstyle form.<br>
Application interface: For GIDs found in the onum coverage table, the<br>
application passes a GID to the onum table and gets back a new GID.<br>
UI suggestion: Users can switch between the default and oldstyle<br>
figure sets by turning this feature on or off. Note: This feature is<br>
separate from the figure-width features pnum and tnum. When the user<br>
changes figure style, the application may want to query whether a<br>
change in width is also desired.</p>
</div>
</div></div><div>
<p class="MsoNormal"><span style="color:white"></span></p>
</div>
</div>
</div>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>"The rat's perturbed; it must sense nanobots! Code grey! We have a Helvetica scenario!" — <a href="http://xkcd.com/683/">http://xkcd.com/683/</a><br>
</div>