From: Hans Hagen <pragma@wxs.nl>
To: Achim Jander <achim@jander.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: export and pagebreak
Date: Mon, 03 Jan 2011 16:19:17 +0100 [thread overview]
Message-ID: <4D21E8F5.3010408@wxs.nl> (raw)
In-Reply-To: <4D21E706.6000707@jander.de>
On 3-1-2011 4:11, Achim Jander wrote:
> So it would be more convenient to have
> filter, lump, <pagebreak/>skip,
> but that could be also done in the postprocessing.
indeed this belongs to postprocessing (if only because there is no space
at a pagebreak) .. similar would be: abc<linebreak/>def where is no
linebreak is needed it can become a space)
> yes, i see. In my case it is of interest to have the same breaking in
> that run, so i wonder if disabling the hz feature
> doesn't change the line-breaking ?
it does
Hans
-----------------------------------------------------------------
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:[~2011-01-03 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-31 18:22 Achim Jander
2011-01-02 14:57 ` Hans Hagen
2011-01-03 11:54 ` Achim Jander
2011-01-03 14:43 ` Hans Hagen
2011-01-03 15:11 ` Achim Jander
2011-01-03 15:19 ` Hans Hagen [this message]
2011-01-03 15:32 ` Achim Jander
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=4D21E8F5.3010408@wxs.nl \
--to=pragma@wxs.nl \
--cc=achim@jander.de \
--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).