From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: TL 2010 and gentium typescript: weird errors with XeTeX
Date: Thu, 24 Jun 2010 09:05:09 +0200 [thread overview]
Message-ID: <AANLkTimaTceoejpHeLgeYcqSEoNOjFTqbXaLGVhj4Tx5@mail.gmail.com> (raw)
In-Reply-To: <4C2236EB.3010102@wxs.nl>
On Wed, Jun 23, 2010 at 18:31, Hans Hagen wrote:
> On 23-6-2010 5:58, Mojca Miklavec wrote:
>
>> True. But lmmi7 *is* an old tfm font.
>
> i don't think that i changed anything at the mkii end so there are two
> possibilities then
>
> (1) the math font definition has changed and refers to features
> (2) xetex has changed
I can test if taking XeTeX from TeX Live into minimals changes anything.
> how does your tex file looks like (not that i'm too keen into diving into a
> xetex related font proble right now)
This is a minimals file (already sent in the first mail):
\usetypescriptfile[type-gentium]
\usetypescript[gentium]
\setupbodyfont[gentium]
\starttext
something
\stoptext
But if you want a more independent one (any font would generate the
same error; without the need to have Gentium installed; just replace
file:GenR102 with any other font specification):
\starttypescript [serif] [gentium]
\definefontsynonym [Gentium-Roman] [file:GenR102] [features=default]
\stoptypescript
\starttypescript [serif] [gentium] [name]
\definefontsynonym [Serif] [Gentium-Roman]
\definefontsynonym [SerifItalic] [Serif]
\definefontsynonym [SerifBold] [Serif]
\definefontsynonym [SerifBoldItalic] [Serif]
\definefontsynonym [SerifSlanted] [Serif]
\definefontsynonym [SerifBoldSlanted] [Serif]
\definefontsynonym [SerifCaps] [Serif]
\definefontsynonym [OldStyle] [Serif]
\stoptypescript
\starttypescript [gentium]
\definetypeface [gentium] [rm] [serif] [gentium] [default] [features=default]
\stoptypescript
\usetypescript[gentium]
\setupbodyfont[gentium]
\starttext
test
\stoptext
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-24 7:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 11:39 Mojca Miklavec
2010-06-23 13:24 ` Hans Hagen
2010-06-23 15:11 ` Khaled Hosny
2010-06-23 15:58 ` Mojca Miklavec
2010-06-23 16:31 ` Hans Hagen
2010-06-23 16:45 ` Khaled Hosny
2010-06-24 7:05 ` Mojca Miklavec [this message]
2010-06-24 7:48 ` Hans Hagen
2010-06-24 7:54 ` Mojca Miklavec
2010-06-24 11:11 ` Hans Hagen
2010-06-24 12:30 ` Mojca Miklavec
2010-06-24 13:08 ` Hans Hagen
2010-06-24 7:50 ` 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=AANLkTimaTceoejpHeLgeYcqSEoNOjFTqbXaLGVhj4Tx5@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).