From: Mika Ritola <the.thin.air@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Problem with font mapping
Date: Wed, 25 Nov 2009 17:27:51 +0200 [thread overview]
Message-ID: <86d68cc30911250727xcbb007elc822b887a3d54c30@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1723 bytes --]
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.
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.
I'm running ConTeXt version 2009.11.24 10:13.
Mika
[-- Attachment #1.2: Type: text/html, Size: 1969 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2009-11-25 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 15:27 Mika Ritola [this message]
2009-11-25 16:47 ` Hans Hagen
2009-11-25 18:52 ` Mika Ritola
2009-11-26 10:39 ` Hans Hagen
2009-11-27 9:31 ` Metapost and mkiv Alan BRASLAU
2009-11-27 9:53 ` Hans Hagen
2009-11-27 13:54 ` Willi Egger
2009-11-28 18:28 ` Alan BRASLAU
2009-11-29 8:03 ` Taco Hoekwater
2009-11-26 12:27 ` Problem with font mapping Wolfgang Schuster
2009-11-26 15:01 ` Hans Hagen
2009-11-26 15:43 ` Wolfgang Schuster
2009-11-26 15:49 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86d68cc30911250727xcbb007elc822b887a3d54c30@mail.gmail.com \
--to=the.thin.air@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).