I am having some issues with LuaLaTex and/or fontenc and bold small caps while using the Adobe Garamond Pro font. Here are my files:

enter image description here

When I compile with XeLaTeX and these options:

\setmainfont{Adobe Garamond Pro}

Everything works fine (except for the italic small caps, but I have no use for it):

enter image description here

But when I try to compile with LuaLaTeX and these options:

    Path           = /home/.../Fonts/Adobe Garamond Pro/,
    Extension      = .otf,
    Ligatures      = TeX,
    BoldFont       = AGaramondPro-Bold,
    ItalicFont     = AGaramondPro-Italic,
    BoldItalicFont = AGaramondPro-BoldItalic,

Bold small caps don't work:

enter image description here

Here is the log:

LaTeX Font Warning: Font shape `EU2/AGaramondPro-Regular(0)/bx/sc' undefined
(Font)        using `EU2/AGaramondPro-Regular(0)/bx/n' instead on input 
line 31.

[1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./smallcaps.aux)

LaTeX Font Warning: Some font shapes were not available, defaults

I looked into the fontspec manual and did not find anything that solved this issue. Clearly it's not font-related because XeLaTeX manage to produce bold small caps but not LuaLaTeX. Thanks for your help.

closed as off-topic by cfr, Masroor, Joseph Wright Jul 5 '14 at 22:56

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • If you check the files with otfinfo -f you will see that the neither the bold nor the italic variant provide small caps. The Xetex output might due to some fake bold trickery. – Philipp Gesang Jun 23 '13 at 19:37
  • Related to @phg's comment, check this question on how to produce fake small caps. – Xavier Jun 23 '13 at 20:10
  • 1
    @phg: Neither XeTeX nor fontspec do fake fonts by default (fontspec manual even discourages using them). – Khaled Hosny Jun 23 '13 at 22:36
  • @Khaled Hosny then OP has a different version of the font. I personally have only limited access to those fonts so I can’t really test them. – Philipp Gesang Jun 24 '13 at 9:30
  • 2
    This question appears to be off-topic because the OP has adopted a work-around which does not answer the original question but the original problem probably depends on some oddity in a commercial font not generally accessible. (Or it is a duplicate of one of the linked questions but we can't tell which without the font and the OP is no longer interested in the answer.) – cfr Jul 5 '14 at 22:11

Browse other questions tagged or ask your own question.