2009/11/25 Hans Hagen
<pragma@wxs.nl>
Mika Ritola wrote:
Hello again,
I seem to be running into all sorts of font problems. Now my document has suddenly turned bold. For example, running the following code results in "Test." being rendered in bold characters.
\usemodule[simplefonts]
\setmainfont[Adobe Garamond Pro]
\starttext
Test.
\stoptext
Running "mtxrun --script font --list --pattern="*Garamond*" --all" reveals that there's something fishy about the font mapping:
adobegaramondpro => agaramondprosemibold => AGaramondPro-Semibold.otf
adobegaramondprobold => agaramondprosemibold => AGaramondPro-Semibold.otf
adobegaramondprobolditalic => agaramondprosemibolditalic => AGaramondPro-SemiboldItalic.otf
adobegaramondproitalic => agaramondprobolditalic => AGaramondPro-BoldItalic.otf
adobegaramondpronormal => agaramondproregular => AGaramondPro-Regular.otf
adobegaramondproregular => agaramondprobold => AGaramondPro-Bold.otf
adobegaramondprosemibold => agaramondprosemibold => AGaramondPro-Semibold.otf
agaramondprobold => agaramondprobold => AGaramondPro-Bold.otf
agaramondprobolditalic => agaramondprobolditalic => AGaramondPro-BoldItalic.otf
agaramondproitalic => agaramondproitalic => AGaramondPro-Italic.otf
agaramondproregular => agaramondproregular => AGaramondPro-Regular.otf
agaramondprosemibold => agaramondprosemibold => AGaramondPro-Semibold.otf
agaramondprosemibolditalic => agaramondprosemibolditalic => AGaramondPro-SemiboldItalic.otf
As you can see, agaramond... are mapped properly while adobegaramond... are mapped wrong.
it all depends in what info is in the font ... familyname, weight etc and sometimes it's contradicting
I downgraded to the "current" (2009.10.27 16:35) version of ConTeXt to see if the mappings are different, and this is the result:
adobegaramondpro => Adobe Garamond Pro Bold => AGaramondPro-Bold.otf
adobegaramondprobold => Adobe Garamond Pro Bold => AGaramondPro-Bold.otf
adobegaramondprobolditalic => Adobe Garamond Pro Bold Italic => AGaramondPro-BoldItalic.otf
adobegaramondproitalic => Adobe Garamond Pro Italic => AGaramondPro-Italic.otf
adobegaramondproregular => Adobe Garamond Pro Regular => AGaramondPro-Regular.otf
adobegaramondprosemibold => Adobe Garamond Pro Semibold => AGaramondPro-Semibold.otf
adobegaramondprosemibolditalic => Adobe Garamond Pro Semibold Italic => AGaramondPro-SemiboldItalic.otf
agaramondprobold => AGaramondPro-Bold => AGaramondPro-Bold.otf
agaramondprobolditalic => AGaramondPro-BoldItalic => AGaramondPro-BoldItalic.otf
agaramondproitalic => AGaramondPro-Italic => AGaramondPro-Italic.otf
agaramondproregular => AGaramondPro-Regular => AGaramondPro-Regular.otf
agaramondprosemibold => AGaramondPro-Semibold => AGaramondPro-Semibold.otf
agaramondprosemibolditalic => AGaramondPro-SemiboldItalic => AGaramondPro-SemiboldItalic.otf
In other words, the mappings seem to be fine here (though I'm not sure about the first one). Thus, it seems that some change in ConTeXt has "broken" the font.
Changing \setmainfont[Adobe Garamond Pro] to \setmainfont[agaramondpro] fixes the issue but, still, I'd prefer to use the former (as I've done until now) since it's clearer.
how recent is your version of mtxrun / mtx-font / font database? it has been a bit in flux last weeks