From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: latest beta (again)
Date: Thu, 09 Oct 2008 11:22:06 +0200 [thread overview]
Message-ID: <48EDCD3E.9010604@wxs.nl> (raw)
In-Reply-To: <9E22F5A7-7456-4D42-9704-078DCB22D92E@uni-bonn.de>
Thomas A. Schmitz wrote:
> 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):
hard to test without test files and fonts -)
you can try
\ctxlua{fonts.trace=true}
and see what is handled
% test file
%
% \starttypescript[serif][mine-1]
% \definefontsynonym[Serif] [TeXGyrePagella-Regular]
%
\definefontsynonym[TeXGyrePagella-Regular][file:texgyrepagella-regular]
% \stoptypescript
%
% \starttypescript[serif][mine-2]
% \definefontsynonym[Serif] [TeXGyrePagella-Regular]
[features=default]
%
\definefontsynonym[TeXGyrePagella-Regular][file:texgyrepagella-regular]
[features=oldstyle]
% \stoptypescript
%
% \starttypescript[serif][mine-3]
% \definefontsynonym[Serif] [TeXGyrePagella-Regular]
[features=oldstyle]
%
\definefontsynonym[TeXGyrePagella-Regular][file:texgyrepagella-regular]
[features=default]
% \stoptypescript
%
% \starttypescript[serif][mine-4]
% \definefontsynonym[Serif] [TeXGyrePagella-Regular]
[features=default]
%
\definefontsynonym[TeXGyrePagella-Regular][file:texgyrepagella-regular]
[features=default]
% \stoptypescript
%
% \starttypescript[serif][mine-5]
% \definefontsynonym[Serif] [TeXGyrePagella-Regular]
[features=oldstyle]
%
\definefontsynonym[TeXGyrePagella-Regular][file:texgyrepagella-regular]
[features=oldstyle]
% \stoptypescript
%
% \starttext
% \dorecurse {5} {
%
\expanded{\definetypeface[mine-\recurselevel][rm][serif][mine-\recurselevel][default]}
% \expanded{\setupbodyfont [mine-\recurselevel]
mine-\recurselevel: text 1234567890 done}
% \par
% }
% \blank
% \dorecurse {5} {
%
\expanded{\definetypeface[more-\recurselevel][rm][serif][mine-\recurselevel][default][features=oldstyle]}
% \expanded{\setupbodyfont [more-\recurselevel]
mine-\recurselevel: text 1234567890 done}
% \par
% }
% \stoptext
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-09 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 8:55 Thomas A. Schmitz
2008-10-09 9:22 ` Hans Hagen [this message]
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=48EDCD3E.9010604@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).