New to Typophile? Accounts are free, and easy to set up.
No idea where we stand in the implementation of descriptive names for Stylistic Sets in applications.
But here's a question anyway:
As far as I know there are no specs on where in the naming tables to put them. Any name table ID can be chosen.
Here I also see a major reason why no one bothers to implement them because they don't know where to look.
Are there any conventions yet on ID ranges?
22 Jan 2013 — 4:43am
No conventions are needed because a Feature Table can point, via its FeatureParams field, at a specific name ID. See the feature tag registry which also mentions which name IDs may be used.
22 Jan 2013 — 5:45am
Okay, so given an FDK code snippet like below, will the FeatureParams field that you mentioned automatically point to the right name ID, given that in this code I don’t even point out name IDs?
In other words: Is this all code that is necessary?
feature ss04 {
# Stylistic Set 4
featureNames {
name 1 "Alternate german lowercase sz";
name 3 "Alternate german lowercase sz";
};
}ss04;
22 Jan 2013 — 6:40am
It is as simple as that.
24 Jan 2013 — 7:33am
Does anyone have any info on what applications display these name records in the UI?
27 Jan 2013 — 8:55pm
I don't know of any that do, yet. Certainly not InDesign or the like. Anybody else know of one that does?
28 Jan 2013 — 4:20am
Maybe in the [near] future; there is one Adobe font with human readable names: Source Sans Pro
28 Jan 2013 — 8:52pm
I would not assume any correlation between the data being in Adobe fonts and support in Adobe applications. Adobe has had optical size data in OpenType fonts for over a decade now, and it is still unsupported by any Adobe application.