ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Saunders <odradek5@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: LuaTeX error ... object in use
Date: Sun, 30 May 2010 06:24:02 -0500	[thread overview]
Message-ID: <AANLkTinv-gsWnFPsqWwzFoLzuPIrT-IK1XnM9kUKqQcT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikcRYx4GAl6P2OY4hOWUj824V5hzZyt0Yt8SPXC@mail.gmail.com>

>How is the [body] feature defined?

\definefontfeature[body][default][onum=yes,pnum=yes,calt=yes,protrusion=quality,expansion=quality]

\definefontfeature[in][body][sinf=yes]%inferior
\definefontfeature[su][body][sups=yes,ordn=yes]%superior
\definefontfeature[nu][body][numr=yes]%numerator
\definefontfeature[de][body][dnom=yes]%denominator
in{\addff{in}123}
su{\addff{su}123abc}
nu{\addff{nu}123}
de{\addff{de}123}

The numerals all come out as proportional oldstyle, but the letters work.  So,
sinf, sups, numr, and dnom are failing but ordn works.

I was thinking---besides updating to 0.60 yesterday, I was also trying
to test Stix fonts, so I ran:
mtxrun --script fonts --reload
luatools --generate
Maybe a change in mtxrun or luatools broke these features?


About my other problem---the strange one that's hard to isolate, and
which appeared this way in 0.50:

! LuaTeX error ...imal/tex/texmf-context/tex/context/base/lpdf-ini.lua:345:
pdf.immediateobj() object in use

and this way in 0.60:

" ! Undefined control sequence.
<argument> \@@bklocation
\processaction ...-> \expandaction \!!stringa{#1
             } \ifx \!!stringa \empty \l..."

I'm still having a very hard time isolating a short example---e.g., I
spent the evening discovering this:  near the end of about seven pages
of typeset text, I have the following string in my input file:

"become more obvious as we examine the phenomena"

This works:
become more obvious as %we examine the phenomena
and this fails:
become more obvious as we %examine the phenomena

I know the word "we" isn't the problem.  Maybe it has something to do
with the length of the text, but that doesn't seem quite right either.
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2010-05-30 11:24 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 [this message]
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
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=AANLkTinv-gsWnFPsqWwzFoLzuPIrT-IK1XnM9kUKqQcT@mail.gmail.com \
    --to=odradek5@gmail.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).