From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: parbuilder in lua
Date: Thu, 25 Sep 2014 12:35:59 +0200 [thread overview]
Message-ID: <5423F00F.7090409@wxs.nl> (raw)
In-Reply-To: <71935EF1-4E97-4DB6-9F85-34CF2FA11225@elvenkind.com>
On 9/25/2014 9:57 AM, Taco Hoekwater wrote:
> Hi Hans,
>
> Can you please try the code below? I found three issues with it:
>
> 1. node-ltp.lua is not completely ready for nuts mode, e.g. line 3148:
>
> elseif order == 0 and hlist.list and last_badness > tex.hbadness then
>
> where ‘hlist.list' should be 'getfield(hlist, "list”)’
getlist(hlist)
> 2. with tracing on, I always get:
>
> Lua linebreak_filter failed, reverting to default on line 1
I've seen that before so I need to check the luatex code too.
> which makes me nervous. Does that mean it works ok without tracing, or does it
> just not report that it does not work?
cur_p -> current
local save_link = getnext(current)
setfield(current,"next",nil)
write_nl("log","")
par.font_in_short_display =
short_display("log",getnext(printed_node),par.font_in_short_display)
setfield(current,"next",save_link)
> 3. with tracing on, there is a double-free of a glyph node (this could be specific to tufte)
some day i'll make an overload of the tracing for context (this code is
somewhat evolving and i want to add some plugins as well ... maybe even
make it kind generic so that we can play in plain tex but as this is all
playground it has a bit low priority)
> TIA,
> Taco
>
> Code:
>
> \tracingparagraphs=1
> \tracingonline=1
> \starttext
> \startparbuilder[basic]
> \input tufte
> \stopparbuilder
> \stoptext
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
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:[~2014-09-25 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 7:57 Taco Hoekwater
2014-09-25 10:35 ` Hans Hagen [this message]
2014-09-25 10:36 ` 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=5423F00F.7090409@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).