From: Francisco Gracia <fgragu023@gmail.com>
To: ntg-context@ntg.nl
Subject: Chapter endings
Date: Mon, 4 Nov 2013 23:48:19 +0100 [thread overview]
Message-ID: <CACiybx6pnhboGa4Onv3sN63HzMLG9To+eoukef4se=V1RANrvQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2370 bytes --]
Many thanks, Wolfgang, for your quick and complete solution to my riddle.
As Hans has commented, it is really brilliant.
I must confess that I do not understand yet the substance of it, i.e. the
definition itself of *Fleuron*, but I will keep studying it and will end
for getting it, I hope.
For the moment I have analyzed and elaborated a bit on your example, first
and mostly by commenting it, but also by slightly modifying it so that it
shows more clearly the characteristics of your solution. I attach it here
just in case it could be as helpful for someone else as it has been for me.
Many thanks again and good luck!
Francisco
% Fleuron.tex
% Example script of the creation and use of a documental ornament
% We first define the documental ornament
% under the traditional name of *Fleuron*
% in the way brilliantly formulated by Herr Schuster
\def\Fleuron
{\par
\leaders\vbox to \lineheight{I am the \em Fleuron\em}\vfil}
% and create a page 10 lines high for testing its behaviour
\setuplayout[lines=10]
% We put *Context* to work
\starttext
% Method 1 (really?)
% Typesetting the ornament as the first element of the page
% results disappointing: it just does not show up
\Fleuron
% but other texts that follow it get their normal treatment;
% for instance, this sentence
I am not really the start:\par
\ \ \ the \em Fleuron\em\ went before me\par
% or this automatically generated text
\dorecurse{4}{Line \recurselevel\par}
% Even the *Fleuron* is treated the same,
% if it is the last element of this page
\Fleuron
% so we create a new page and repeat the same
% instructions
\page
I am not really the start:\par
\ \ \ the \em Fleuron\em\ went before me\par
\dorecurse{4}{Line \recurselevel\par}
\Fleuron
I am after the \em Fleuron\em\
% surprisingly, although there is room available,
% the ornament disappears
% if there is more text coming after it
% so we go to another page, the third one,
% for our last and definitive test
\page
% This time the space of the page is full
\dorecurse{10}{Line \recurselevel\par}
% when the turn of the *Fleuron* arrives
\Fleuron
% The result is that not only the *Fleuron* does not show up
% in this page, which was to be expected because it is full,
% but even the implied next page, the fourth,
% does not get generated by *Context*. PERFECT!
\stoptext
[-- Attachment #1.2: Type: text/html, Size: 5094 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 reply other threads:[~2013-11-04 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 22:48 Francisco Gracia [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-11-10 15:07 Francisco Gracia
2013-11-10 21:21 ` Wolfgang Schuster
2013-11-02 20:54 Francisco Gracia
2013-11-04 0:37 ` Wolfgang Schuster
2013-11-04 14:55 ` 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='CACiybx6pnhboGa4Onv3sN63HzMLG9To+eoukef4se=V1RANrvQ@mail.gmail.com' \
--to=fgragu023@gmail.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).