ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: taco <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LuaTeX error ... object in use
Date: Sun, 30 May 2010 21:29:29 +0200	[thread overview]
Message-ID: <4C02BC99.7020107@elvenkind.com> (raw)
In-Reply-To: <AANLkTimYBfIlnQxKd_7JI1zCS2YuH56TVM-R9tY-cSfS@mail.gmail.com>

Michael Saunders wrote:
>> Please add script=latn, that works for Palatino Nova, and I think
>> there possibly was in change in that a while back (some months).
> 
> Thanks, I have added script=latn to \definefontfeature[body], but
> those Open Type features still aren't back to normal.  I should have
> mentioned that I had:
> \definefontfeature[default][mode=node,language=dflt,script=latn,kern=yes,liga=yes,tlig=yes,trep=yes]
> \definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]

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. All I can say is that your original
example, after addition of 'script=latn', works with Palatino Nova
(which is the only font I have that supports those features)

> 
> must be related to the missing line from str-flt.mkiv.  I have added
> it, though, and I _think_ I remade the formats, but I get no change in
> behavior.

The
   context --make en
should have taken care of that, but you can check: the third or fourth
line in the log file is something like this:

ConTeXt  ver: 2010.05.30 17:08 MKIV  fmt: 2010.5.30  int: english/english

The date after fmt: is the date on which the format was generated.

Best wishes,
Taco
___________________________________________________________________________________
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 19:29 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 [this message]
2010-05-30 20:36             ` Michael Saunders
2010-05-30 21:05               ` Hans Hagen
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=4C02BC99.7020107@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).