From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Two errors in test file.
Date: Tue, 9 Sep 2014 21:37:41 +0200 [thread overview]
Message-ID: <1F3002C0-C638-4445-9749-CA7AEA99AD1B@gmail.com> (raw)
In-Reply-To: <20140909151803.780f433a@localb.wexfordpress.net>
Am 09.09.2014 um 21:18 schrieb john Culleton <John@wexfordpress.com>:
> Here is the test file:
> --------------------------------------
> \definefontfamily [myfamily][serif][MinionPro Serif]
> \definefontfamily [myfamily][sans][MyriadPro Sans]
> \definefontfamily [myfamily][italic][MinionPro Italic]
> \setupbodyfont[myfamily]
> \starttext
> \rm
> foo
> \startitemize[a]
> \item {\bf Inkscape}
> \item Scribus
> \item Gimp
> \stopitemize
> \stoptext
> ---------------------------------------
> First, nothing prints.
> Second, if I say
> \startitemize[1]
> I get an error on the first \item line.
> I suspect that the default font doesn't have the
> big dot character.
>
> The system variable OSFONTDIR points
> to /usr/share/fonts
>
> Obviously there is something that I am missing
> in the font definitions.
All of your three font definitions are wrong because
1. There is only a font with the name “Minion Pro” but no “Minion Pro Serif”.
2. There is only a “Myriad Pro” font but no “Minion Pro Sans” font.
3. The “italic” in the style of the third definition is wrong because italic is a font alternative. When an unknown value is used for the style the command uses serif as fallback and therefore overwrites the first line which sets the serif style as well.
The following example uses the right names (which I used also in the answers of your previous questions) for both fonts.
\definefontfamily [myfamily] [serif] [Minion Pro]
\definefontfamily [myfamily] [sans] [Myriad Pro]
\setupbodyfont[myfamily]
\starttext
\startitemize[a]
\item {\bf Inkscape}
\item Scribus
\item Gimp
\stopitemize
\stoptext
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2014-09-09 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 19:18 john Culleton
2014-09-09 19:37 ` Wolfgang Schuster [this message]
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=1F3002C0-C638-4445-9749-CA7AEA99AD1B@gmail.com \
--to=schuster.wolfgang@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).