ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: font error with latest beta
Date: Sat, 16 Apr 2016 13:23:18 +0200	[thread overview]
Message-ID: <571220A6.1090807@wxs.nl> (raw)
In-Reply-To: <57111889.7050403@uni-bonn.de>

On 4/15/2016 6:36 PM, Thomas A. Schmitz wrote:
> Hi Hans,
>
> I run into my favorite error with the latest beta ("this can't happen").
> The document uses a SabonNext font, but I get similar results with other
> fonts. The error message is:
>
> tex error       > tex error on line 855 in file
> /home/tas/context/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv:
> ! This can't happen (fuzzy token cleanup in node)
>
>
> \page_shipouts_normal ...box \shipoutscratchbox }}
>                                                    \else
> \page_shipouts_ignor...
> \page_boxes_shipout ... {\box \shipoutscratchbox }
>                                                    \fi
> \setnextrealpageno \th...
> \page_otr_construct_and_shipout ...cted_page #1#2}
>
> \page_otr_flush_pending_co...
> \page_sides_output_routine_nop ...de_float_output
>                                                    \global
> \d_page_sides_vsiz...
> \page_sides_output_routine ..._output_routine_nop
>                                                    \fi
> \page_otr_triggered_output_routine ...and_routine
>                                                    \fi
> ...
> l.97 \getvalue{clf_processjob}
>                               % from cont-run.lua
>
>
>
>
> mtx-context     | fatal error: return code: 1%
>
> An older context version (2016.02.08 15:35) processes the same file
> without problems, so I suspect it may be the newer luatex binary. I
> can't produce a minimal example right now, the error is a bit
> unpredictable.

Do you have a minimal test (maybe some specific typographic feature 
triggers it)? It probably is some oversight .. i mess up a list ... we 
merged glue specs into glue nodes which is much cleaner (the last big 
thing before luatex 1.0). Probably not hard to solve.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | 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:[~2016-04-16 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15 16:36 Thomas A. Schmitz
2016-04-16 11:23 ` Hans Hagen [this message]

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=571220A6.1090807@wxs.nl \
    --to=pragma@wxs.nl \
    --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).