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>
Cc: Michael Saunders <odradek5@gmail.com>
Subject: Re: LuaTeX error ... object in use
Date: Sun, 30 May 2010 23:05:14 +0200	[thread overview]
Message-ID: <4C02D30A.2090105@wxs.nl> (raw)
In-Reply-To: <AANLkTimGNa9QWkXdqPZ3xSHbl_NJ-h0UAw0deQSvbWuf@mail.gmail.com>

On 30-5-2010 10:36, Michael Saunders wrote:
>> There is no test file, and I still do not know which font you are
>> using. Attempting to find the problem is closer to tea-gazing
>> than to debugging at the moment. Font features cannot be debugged
>> independent of the actual font.
>
> Thanks, I understand.  I had been using GaramondPremrPro (which has
> all four features and worked with 0.50).  You gave me the idea to try
> GillSansMTPro, which also has the four features.  I got a very
> interesting result---for it, numr and dnom work, but sinf and sups do
> not.  I don't know how I could prepare a test file for you short of
> sending you my fonts and typescripts (which I'd be willing to do).

you can try

mtxrun --script font --list --info garamondpremrpr

or

context --trackers=otf.features yourfile

to see what happens with features


-----------------------------------------------------------------
                                           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
___________________________________________________________________________________


  reply	other threads:[~2010-05-30 21:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  2:35 Michael Saunders
2010-05-29  5:39 ` Taco Hoekwater
2010-05-29  7:53 ` Michael Saunders
2010-05-29 12:56   ` Taco Hoekwater
2010-05-29 15:58   ` Michael Saunders
2010-05-30  9:54     ` Taco Hoekwater
2010-05-30 11:24     ` Michael Saunders
2010-05-30 11:35       ` Hans Hagen
2010-05-30 16:52         ` Michael Saunders
2010-05-30 19:08           ` Michael Saunders
2010-05-30 19:29             ` taco
2010-05-30 20:36             ` Michael Saunders
2010-05-30 21:05               ` Hans Hagen [this message]
2010-05-30 21:24                 ` Michael Saunders
2010-05-30 21:33                   ` Hans Hagen
2010-05-30 22:08                     ` Michael Saunders
2010-05-31  6:44                       ` Hans Hagen
2010-05-31 11:32                   ` Hans Hagen
2010-05-30 18:29       ` taco

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=4C02D30A.2090105@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=odradek5@gmail.com \
    /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).