Replacement feature problem
The problem is that when I replace lower case with small caps the brackets also reduce in size (shown in pink). There is a similar problem when replacing caps with small caps. As you can see with the illustration the feature code is pretty simple - just replacing one class with another. Could this be something that needs specifying as an exception to the context rule? The FontLab manual has no illustrations which demonstrate the meaning of the text, so consequently means nothing to me. That’s the trouble with the manual; sometimes it has illustrations for obvious things, but none for not-so obvious things.
Any ideas? Thanks.
23.Jul.2008 2.56am
Nick,
I think it is a question of feature appliance: Should they blindly be applied throughout the whole text string?
But if you like it to work even in these cases, I guess you’ll have to add some contextual stuff.
23.Jul.2008 4.25am
Hi Nick,
I haven’t worked with c2sc and such before, but I think it would work if you take your punctuation out of the classes altogether for caps and small caps. That way your resized marks can replace the standard contextually as Christoph says.
Stephen
23.Jul.2008 4.31am
I think that you can define a different class for small brackets and everything is not a letter, in that way in smcp you can replace only the letters and in c2sc you replace letters and other glyphs
23.Jul.2008 5.39am
You seem to deal with smallcap punctuation in smcp. It’d be better to cover alternate smallcap punctuation only in c2sc (caps to small caps), but not in smcp (lowercase to small caps).
Then, smallcap punctuation are applied only if a user selects “All Small Caps” in the application which activates both c2sc and smcp (so to test this behavior in FLS, you need to apply both too).
If a user selects “Small Caps”, only smcp would be activated (without smallcap punctuation).
In so far I don’t think that it makes sense to take smallcap punctuation out of smallcap features entirely. No contextuality needed either, that may mess things up even more.
Karsten
23.Jul.2008 1.40pm
Right Karsten.
“smcp” should be only for letters, so that it works as “(Caps with) Small Caps” in mixed case settings with upper and lower case, such as acronyms and names in text.
“c2sc” should have all the bells and whistles, for when applications combine it with “smcp” to produce “All Small Caps”—for use in settings such as running heads, folios and title pages, where the idea is to produce an effect akin to optical scaling.