From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: redefining paragraph breaks
Date: Tue, 3 Jan 2012 21:14:22 +0100 [thread overview]
Message-ID: <9F11A96B-5ACD-49E6-BDEF-82A749DE113D@googlemail.com> (raw)
In-Reply-To: <CAHJRaA7Rkq5OHwd4PJgJxcDra_fVikUkJ-YRRHPgzrUGuHe8Ug@mail.gmail.com>
Am 03.01.2012 um 20:31 schrieb Chris Lott:
> 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.
You can save the text in a buffer and replace the empty lines with the paragraph symbol.
\startluacode
userdata = userdata or { }
function userdata.specialparagraph()
local text = buffers.getcontent("specialparagraph")
text = string.gsub(text,"\n\n"," ¶ ")
context(text)
end
\stopluacode
\def\startspecialparagraph
{\dostartbuffer[specialparagraph][startspecialparagraph][stopspecialparagraph]}
\def\stopspecialparagraph
{\ctxlua{userdata.specialparagraph()}}
\starttext
This is paragraph 1.
\startspecialparagraph
This is paragraph 2.
This is paragraph 3.
\stopspecialparagraph
This is paragraph 4.
\stoptext
Wolfgang
___________________________________________________________________________________
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:[~2012-01-03 20:14 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 [this message]
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
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=9F11A96B-5ACD-49E6-BDEF-82A749DE113D@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).