ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XeTeX and precise font sizes
Date: Thu, 10 Jul 2008 23:35:39 +0200	[thread overview]
Message-ID: <487680AB.4030108@wxs.nl> (raw)
In-Reply-To: <78C327A4-A72D-45CB-9D59-F6ED5CBC6E8E@getalime.ru>

Neiaglov Dmitry wrote:
>>
>> \starttypescript[serif][gentium-basic]
>> \definefontsynonym[Serif]          [GentiumBasic]
>> \definefontsynonym[SerifItalic]    [GentiumBasicItalic]
>> \definefontsynonym[SerifBold]      [GentiumBasicBold]
>> \definefontsynonym[SerifBoldItalic][GentiumBasicBoldItalic]
>> \stoptypescript
> 
> 
> Cool, that clarifies a lot for me, thanks :) So \startypescript uses  
> xetex after all!

it's more the reverse ... typescripts are the interface and deep down it 
is translated to the right commands for pdftex, zetex or luatex

> Unfortunately, ConTeXt tends to compile this document three times  
> before giving me the PDF. (Makes you wonder!)

normally there ar etwo runs (depends on how many changes in the 
documents); any macro package that uses multi pass data will do several 
runs to be sure that the cross refs and lists are ok (also, some pdf 
constructs use forward references that need to be resolved)

> And anyway, what is the difference between typescripts and typefaces  
> in ConTeXt terms? The only thing I found in docs was that \definefont  
> works in the context of the current construction.

typescripts are just definitions and invoking a one of them (which 
itself may invoke another) will define a typeface which itself 
eventually results in a bunch of font definitions

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2008-07-10 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 22:13 Neiaglov Dmitry
2008-07-09 23:02 ` Diego Depaoli
2008-07-10  5:48   ` Wolfgang Schuster
2008-07-10  6:50   ` Neiaglov Dmitry
2008-07-10  8:19     ` Hans Hagen
2008-07-10 11:52     ` Diego Depaoli
2008-07-10 14:10     ` Mojca Miklavec
2008-07-10 16:09       ` Neiaglov Dmitry
2008-07-10 21:35         ` Hans Hagen [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=487680AB.4030108@wxs.nl \
    --to=pragma@wxs.nl \
    --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).