ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Tim Li <timli2013@outlook.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Mismatched font size when switching fonts in the chapter title
Date: Wed, 17 Apr 2013 09:47:14 +0000	[thread overview]
Message-ID: <BLU152-W5F292588E46F03993C60EA9CE0@phx.gbl> (raw)
In-Reply-To: <CAF=dkzzm-8=5TsaaEEvOLwKdnss=5jxx9i2-OKK_ZNDeW4OCJA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2174 bytes --]

Sietse,  Thanks for your detailed explanation. With your help, I have known the reason. Also, I am reading the new chapter on fonts.
 Best regards,Tim> From: sbbrouwer@gmail.com
> Date: Wed, 17 Apr 2013 10:11:19 +0200
> To: ntg-context@ntg.nl
> Subject: Re: [NTG-context] Mismatched font size when switching fonts in the chapter title
> 
> Hi Tim,
> 
> [PalatinoRoman sa 1]
> This means "PalatinoRoman scaled at 1 x bodyfontsize. The document's
> body font size is 12 pt, but chapter headers usually are ... like,
> about 2.4 * body font size? Hence the size mismatch.
> 
> [PalatinoRoman sa *]
> This means "AnotherFont is PalatinoRoman scaled to 1 x the font size
> at time of calling.
> 
> Compare these two MWE's (I've changed the font name to
> texgyrepagellaregular so that the example will work for any ConTeXt
> user.)
> 
> \setupbodyfont[12pt]
> \definefontsynonym[PalatinoRoman][texgyrepagellaregular][features=default]
> \definefont[AnotherFontSaOne][PalatinoRoman sa 1]
> \definefont[AnotherFontSaStar][PalatinoRoman sa *]
> 
> \starttext
> \chapter{Fonts and \AnotherFontSaOne Fonts}
> Generalized \AnotherFontSaOne Generals. (Constant size)
> 
> \chapter{Fonts and \AnotherFontSaStar Fonts}
> Generalized \AnotherFontSaStar Generals. (Adapt to current size)
> \stoptext
> 
> I got this information from page 5 of the Fonts chapter of the
> long-coming manual. (Not the same as the document detailing what you
> can do with OTF and Lua, although I think that one, too, is called a
> fonts manual.)
> http://context.aanhet.net/svn/contextman/context-reference/en/co-fonts.pdf
> 
> Cheers,
> Sietse
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 2743 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 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
___________________________________________________________________________________

      reply	other threads:[~2013-04-17  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  7:00 Tim Li
2013-04-17  8:11 ` Sietse Brouwer
2013-04-17  9:47   ` Tim Li [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=BLU152-W5F292588E46F03993C60EA9CE0@phx.gbl \
    --to=timli2013@outlook.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).