From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: redefining paragraph breaks
Date: Fri, 06 Jan 2012 17:17:48 +0100 [thread overview]
Message-ID: <4F071EAC.5000302@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.1201061436470.8727@calypso.view.net.au>
On 6-1-2012 05:09, Michael Talbot-Wilson wrote:
> On Tue, 3 Jan 2012, Chris Lott wrote:
>
>> I know I could do it manually, but that makes the source ugly, so is
>> there a way to redefine paragraph breaks so that instead of actual
>> breaks in the output they are kept as running text separate by a
>> paragraph symbol, e.g.:
>>
>> This is paragraph 1.
>>
>> This is paragraph 2.
>>
>> Becomes in the typeset document:
>>
>> This is paragraph 1. ¶ This is paragraph 2.
>>
>> ?
>>
>> c
>
> Can't you use plain's \everypar?
don't touch that one if you don't want to loose functionality (some day
it will be more heavily protected)
\EveryPar is a user hook
but even then, it comes to late for this purpose as the new paragraoh
has already been started
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
___________________________________________________________________________________
prev parent reply other threads:[~2012-01-06 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:31 Chris Lott
2012-01-03 20:14 ` Wolfgang Schuster
2012-01-04 10:04 ` Hans Hagen
2012-01-06 4:09 ` Michael Talbot-Wilson
2012-01-06 12:54 ` Michael Talbot-Wilson
2012-01-06 16:17 ` 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=4F071EAC.5000302@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).