Please Help Correct This By Submitting a Bug Report to Apple

Things not necessarily Nisus. Chat about the latest Apple release, your adorable three-toed sloth, or whatever else you fancy.
Post Reply
wwgreaves
Posts: 49
Joined: 2013-01-27 17:47:43

Please Help Correct This By Submitting a Bug Report to Apple

Post by wwgreaves »

I recently discovered that an inability to toggle between old-style and lining figures in certain fonts originates from the development of Mavericks. I have submitted a bug report through Apple.com, and I would appreciate other members of this forum submitting bug reports as well. You could just copy the first three paragraphs below and submit them as your text:

When the engineers reworked the Cocoa OpenType menu (the “typography” panel) in Mavericks, they assumed that every font’s default figures are lining. Because they’re making this erroneous assumption, they only look for the “Old-Style Figures” OpenType feature, and they completely ignore the standard “Lining Figures” OpenType feature.

This bug directly effects the preparation of financial and scientific documents. For example, if I want to use the fonts Harriet or Alright Sans, which have old-style figures as the default, I cannot toggle to lining figures for tables, graphs, or addresses. In fact, in Harriet and Alright Sans, the lining figures aren’t accessible at all because of this bug.

I’ve tested a number of OpenType fonts, including the OpenType benchmark Microsoft ClearType fonts, and I am 100% certain this is an Apple bug. The problem manifests itself in Nisus Writer Pro, Pages ’09, and TextEdit.

Below is a more technical description of the bug, which a local font developer provided. I hope you can help quickly resolve this bug with the engineers.


BUG REPORT:

LNUM unavailable in Mavericks via CTFontCopyFeatures

Product: OS X Product Version: 10.9.1
Classification: Serious Reproducible: Yes

Summary:

Under prior versions of OSX, calling CTFontCopyFeatures for a CTFontRef containing the LNUM opentype feature would show three options for kNumberCaseType:

0: oldstyle figures
1: lining figures
2: no change

in Mavericks, only 0 and 2 are available, with the same font.

The problem also manifests itself under advanced typography options in Textedit and Pages ‘09.

Steps to Reproduce:

With any font using the LNUM opentype feature, compile the following:

CTFontRef ctf = CTFontCreateWithName(CFSTR("NadyezhdaSLOne-Reg"), 16.0, nil);
CFArrayRef feats = CTFontCopyFeatures(ctf);
for (NSDictionary* d in (__bridge NSArray *) feats) {
if ([d objectForKey:@"CTFeatureTypeIdentifier"] == [NSNumber numberWithInt:21])
NSLog(@"%@", d);
}


Expected Results:
{
CTFeatureTypeExclusive = 1;
CTFeatureTypeIdentifier = 21;
CTFeatureTypeName = "Number Case";
CTFeatureTypeSelectors = (
{
CTFeatureSelectorIdentifier = 0;
CTFeatureSelectorName = "Old-Style Figures";
},
{
CTFeatureSelectorIdentifier = 1;
CTFeatureSelectorName = "Lining Figures";
},
{
CTFeatureSelectorDefault = 1;
CTFeatureSelectorIdentifier = 2;
CTFeatureSelectorName = "No Change";
}
);
}

Actual Results:
{
CTFeatureTypeExclusive = 1;
CTFeatureTypeIdentifier = 21;
CTFeatureTypeName = "Number Case";
CTFeatureTypeNameID = "-2200";
CTFeatureTypeSelectors = (
{
CTFeatureSelectorIdentifier = 0;
CTFeatureSelectorName = "Old-Style Figures";
CTFeatureSelectorNameID = "-2201";
},
{
CTFeatureSelectorDefault = 1;
CTFeatureSelectorIdentifier = 2;
CTFeatureSelectorName = "No Change";
CTFeatureSelectorNameID = "-2203";
}
);
}

Version:

OSX 10.9.1 -- incorrect behavior

OSX 10.6.8 -- correct behavior

Notes:

Did not have any other versions of OSX handy to test

Configuration:

The correct behavior was observed in 10.6, the incorrect behavior showing only two states for NumberCase showed up in 10.9
Post Reply