If Word 2010 does not access the font's OpenType small caps feature, then the answer is no, you won't be able to get the true small cap glyphs.
Arno Pro and other more recent Adobe font releases do not use PUA encodings. We currently believe that assigning PUA codepoints to small cap (and other alternate) glyphs is not a good practice.
Thanks for the response, Miguel.
Just out of curiosity, what is the thinking behind no longer assigning PUA
codepoints to small caps?
Also, do you know offhand which Adobe fonts, other than Arno and Adobe
Caslon, do not have PUA codeponts for small caps?
Thanks very much.
Using PUA-encoded glyphs breaks the semantics of the text; the words can no longer be spell-checked, and they might turn to gibberish or notdefs (rectangular boxes with a cross) if you switch to another font.
Thanks very much for the explanation, Miguel.
It is surprising that MS did not include small caps in the OpenType features
they added to Word 2010. I'd think small caps would. be wanted at least as
much as automatic ligature substitution. For the time being, I'll use fake
small caps if needed in Arno, or use a font that uses PUA for the small
I just got a copy of Word 2011 (Mac). For some reason they support stylistic variants but not small caps. However if you have a font editor that can edit Opentype, it's pretty easy to copy the small caps feature and rename the copy to stylistic variant N, where N is either not used by the font one a feature you don't care about.
It seems pretty odd for them to support stylistic variants, but omit small caps, as I'm pretty sure sure caps are used more often.
Thanks for the info and suggestion, Charles. Word 2010 (for PC) supports
OpenType as you say Word 2011 (Mac) does.
Thomas Phinney posted a likely explanation somewhere to the effect that
substituting small caps could lead to anomalous results if the font does not
have a small cap for a particular glyph, e.g., many non-English accented
letters. He posited that the Office team's thinking might have been that
while users of InDesign, Quark, and MS Publisher would be sophisticated
enough to deal with the problem, large numbers of Word users might not be.
Your suggestion as to how to modify fonts by putting small caps in as
sylistic variant N is helpful, but unfortunately, I don't have or know how
to use a font editor.
It is too bad that there is no repository of fonts modified as you suggest.
I guess the problem, though, is that there would be no way to restrict
access to those owning a licensed copy of the font in question, and
providing copies to all would violate copyright laws.
Hopefully, MS will include true small caps in the next versions of Word.
I'll look into doing a converter. I have an existing program that will take an opentype font and change the character table to move the small caps into the position of the normal letters. But this produces a second small caps font. It should be a lot easier to make this change.
Finney's theory is interesting, but I doubt it's that well-considered.