From: Hans Hagen <pragma@wxs.nl>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
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 13:11:48 +0200 [thread overview]
Message-ID: <4C233D74.3050902@wxs.nl> (raw)
In-Reply-To: <AANLkTilclZmrJb7qxL170exhbZPhnzSeXYKSNEuF-O3t@mail.gmail.com>
On 24-6-2010 9:54, Mojca Miklavec wrote:
> On Thu, Jun 24, 2010 at 09:48, Hans Hagen wrote:
>>
>> also runs ok
>
> Yes, in minimals it works fine. Also if I copy the XeTeX binary from
> TL, it still works OK, it's only TL that is failing. Is it possible
> that some settings in kpathsea/xetex font searching settings are
> different?
>
> Is it possible to avoid searching for
> lmmi7:+liga;+kern;mapping=tlig;
> from within ConTeXt?
Makes me wonder where it comes from ... as xetex has this latex friendly
but context unfriendly [] system and favors names over files, we need
some tricks to check what we're dealing with so we do some tests .. what
does
\settrue\tracexetexfonts
return? did they change the error recovery code, that is, this
\suppressfontnotfounderror
thing.
Anyhow, I stripped some code from font-ini.mkii, move some to
font-xtx.mkii and removed de feature default so now you need to
explicitly add [features=default] to typescript definitions (I did that
in font-otf.mkii from which i also stripped a bunch of lucida type 1
defs which should not be in there anyway).
I'll upload a beta to the ftp server for you. As texlive is frozen it
won't help much for tl2010 but here are the files that matter:
font-ini.mkii
font-xtx.mkii
type-ini.mkii
type-otf.mkii (also fixed some antikwa defs)
I really hope that this is the last time i have to look into it.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-06-24 11:11 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
2010-06-24 7:48 ` Hans Hagen
2010-06-24 7:54 ` Mojca Miklavec
2010-06-24 11:11 ` Hans Hagen [this message]
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=4C233D74.3050902@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.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).