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: Patrick Gundlach <patrick@gundla.ch>
Subject: Re: post_linebreak_filter in context
Date: Fri, 25 Feb 2011 13:46:18 +0100	[thread overview]
Message-ID: <4D67A49A.7070803@wxs.nl> (raw)
In-Reply-To: <65243520-DA54-4978-A996-AA761054D3EB@gundla.ch>

On 25-2-2011 12:28, Patrick Gundlach wrote:
> Hi,
>
> how do I install a custom post_linebreak_filter in ConTeXt? I have this LaTeX file:
>
> ------------------------------------------------------------------------------------
> \documentclass[12pt,a4paper]{scrartcl}
> \usepackage[english]{babel}
> \usepackage{blindtext}
> \usepackage{fontspec}
> \directlua{
> show_hyph = function(head)
>    while head do
>      if head.id == 0 or head.id == 1 then % hlist, vlist
>        show_hyph(head.list) % should be head.head in a newer luatex than 0.64
>      elseif head.id == 7 then             % disc
>        local n = node.new("whatsit","pdf_literal")
>        n.mode = 0
>        n.data = "q 0.3 w 0 2 m 0 7 l S Q"
>        n.next = head.next
>        n.prev = head
>        head.next = n
>        head = n
>      end
>    head = head.next
>    end
>    return true
> end
> luatexbase.add_to_callback("post_linebreak_filter",show_hyph,"show_hyph")
>
> }
>
> \begin{document}
> \begin{minipage}{5cm}
> \blindtext
> \end{minipage}
> \end{document}
> ------------------------------------------------------------------------------------
>
> which registers a function "show_hyph" as the post_linebreak_filter (the rest is not really interesting). How would I do this in ConTeXt?

first put the function in some namespace, like:

moduledata.mystuff = { }
moduledata.mystuff.show_hyph = show_hyph

then register it in the finalizer group (which is the post_linebreak stuff)

nodes.tasks.appendaction("finalizers","after","moduledata.mystuff.show_hyph")

(before and after are subgroups that can be used by users if needed; of 
course one never know to what extent it will influence other processes, 
so "shipouts","after" might be a better choice)

-----------------------------------------------------------------
                                           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:[~2011-02-25 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 11:28 Patrick Gundlach
2011-02-25 12:46 ` Hans Hagen [this message]
2011-02-25 15:14   ` Patrick Gundlach

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=4D67A49A.7070803@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=patrick@gundla.ch \
    /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).