From: Rory Molinari <context@quokka70.fastmail.fm>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problems with Palatino sans serif
Date: Mon, 20 Oct 2008 14:03:49 -0700 [thread overview]
Message-ID: <48FCF235.5030208@quokka70.fastmail.fm> (raw)
In-Reply-To: <48FC51D0.8050809@elvenkind.com>
Taco Hoekwater wrote:
> Hi Rory,
Hi Taco,
Thanks for responding.
>
> Because there is no fallback font defined either, you get 'nothing'
> when you switch to \ss in the older contexts. You could attempt
> to update your context installation, but this could introduce
> new problems, so it may be easiest to add a \definetypeface line
I've already updated my installation, which cleared up the problem. Is
it risky in general to use 'ctxtool --updatecontext'?
> for palatino ss in your document someplace before the \setupbodyfont.
>
> \definetypeface [palatino] [ss] [sans] [modern]
> [default] [encoding=ec,rscale=1.075]
Oh, I see. This uses the Computer Modern sans.
So if I understand things correctly, the various arguments are:
[palatino]: the typeface being defined (or modified in this case)
[ss]: the part of the typeface being defined (the \ss name)
[sans]: refers to a part of the "modern" typeface
[modern]: pick the "sans" part of the this typeface
[default]: what's this bit?
[encoding]: the encoding to use
[rscale]: a scaling adjustment to make up for CM's smaller x-size.
Is that the general idea?
Cheers,
Rory
>
> Best wishes,
> Taco
> ___________________________________________________________________________________
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-20 21:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 23:13 Rory Molinari
2008-10-18 23:34 ` Rory Molinari
2008-10-18 23:59 ` Aditya Mahajan
2008-10-19 1:26 ` Rory Molinari
2008-10-19 2:10 ` Aditya Mahajan
2008-10-19 7:35 ` Taco Hoekwater
2008-10-19 14:37 ` Idris Samawi Hamid ادريس سماوي حامد
2008-10-19 19:24 ` Rory Molinari
2008-10-20 9:39 ` Taco Hoekwater
2008-10-20 21:03 ` Rory Molinari [this message]
2008-10-20 22:14 ` Taco Hoekwater
2008-10-19 1:47 ` Idris Samawi Hamid ادريس سماوي حامد
2008-10-19 12:56 ` Mojca Miklavec
2008-10-20 9:54 ` Taco Hoekwater
2008-10-20 11:33 ` Mojca Miklavec
2008-10-20 11:36 ` Mojca Miklavec
2008-10-20 12:45 ` Taco Hoekwater
2008-10-20 14:40 ` Mojca Miklavec
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=48FCF235.5030208@quokka70.fastmail.fm \
--to=context@quokka70.fastmail.fm \
--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).