ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing ConTeXt users list for <ntg-context@ntg.nl>
Subject: latest beta (again)
Date: Thu, 9 Oct 2008 10:55:28 +0200	[thread overview]
Message-ID: <9E22F5A7-7456-4D42-9704-078DCB22D92E@uni-bonn.de> (raw)

Hans,

I still have some problems with my fonts in the latest beta. Maybe it  
has to do with the latest optimizations. I'm just wondering: in my  
Greek typescripts, I define several fontfeatures and connect them with  
featurefiles, like so (just an example, the list is longer):

\installfontfeature[otf][gent]
\installfontfeature[otf][kori]

\definefontfeature
   [korinthia]
    
[mode 
= 
node 
,language 
= 
dflt 
,script 
=latn,kern=yes,tlig=no,trep=no,kori=yes,featurefile=korinthia.fea]

\definefontfeature
   [gentiumgreek]
    [mode=node,language=dflt,script=latn,kern=yes,tlig=no,trep=no,
     gent=yes,featurefile=gentium.fea]

\starttypescript [serif] [GreekGentiumAlt] [name]
   \definefontsynonym [Serif]           [name:GenAR102]  
[features=gentiumgreek]
   \definefontsynonym [SerifItalic]     [name:GenAI102]  
[features=gentiumgreek]
   \definefontsynonym [SerifBold]       [Serif]
   \definefontsynonym [SerifBoldItalic] [SerifItalic]
\stoptypescript

\starttypescript [serif] [GreekKorinthia] [name]
   \definefontsynonym [Serif]           [name:Korinthia]   
[features=korinthia]
   \definefontsynonym [SerifItalic]     [Serif]
   \definefontsynonym [SerifBold]       [Serif]
   \definefontsynonym [SerifBoldItalic] [Serif]
\stoptypescript

The main font definition is of this form:

\starttypescript[greek]
\definetypeface[greek][rm][serif][\currentmoduleparameter{font}] 
[default][rscale=\currentmoduleparameter{scale}]
\stoptypescript
\usetypescript[greek]

So I'm just wondering: must the "features=" be included into the  
\definetypeface as well? I have the impression that the different  
features I define are not used at all...

Thomas

___________________________________________________________________________________
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-10-09  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09  8:55 Thomas A. Schmitz [this message]
2008-10-09  9:22 ` Hans Hagen
2008-10-09  9:47   ` Thomas A. Schmitz
2008-10-09 10:26 ` 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=9E22F5A7-7456-4D42-9704-078DCB22D92E@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.de \
    --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).