From: Francisco Gracia <fgragu023@gmail.com>
To: ntg-context@ntg.nl
Subject: Chapter endings
Date: Sun, 10 Nov 2013 16:07:13 +0100 [thread overview]
Message-ID: <CACiybx5csP-yzKY5UjLAS53NaAbLSL+W9hMfYf44u6Zu2AnKHQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2160 bytes --]
This is a disclaimer to my former message about this subject.
I continued considering the solution to the problem of using *fleurons* in
a document via the suggested *\leaders* command and it turned out to be a
dead end for the following reasons:
1) it acts wrongly if the page in which the *fleuron* is to appear has
a lot of blank space availabe, as the following test code demonstrates:
\setuplayout[lines=30]
\def\Fleuron
{\par
\leaders\vbox to \lineheight{\midaligned{Finis\\coronat\\opus}}\vfil}
\starttext
\dorecurse{32}{Line \recurselevel\par}
\Fleuron
\stoptext
where the intended *fleuron* appears superposed several times instead of
the only one desired;
2) the use of such an instruction is touchy and not dependable. As I
have experienced, things work satisfactorily or not according to the degree
of nesting of the command *\fleuron* in the whole launching command and
possibly according to many other unnoticed factors;
3) the suggested formulation does not allow enough control for the
placement of the *fleuron* in the final document.
In the end all this seems reasonable: the straigth use of the *\leaders*
command is almost the contrary of the one demanded for the present
functionality. The effect of the (obscure in more than one sense) *Tex*
command *\leaders* is to fill a (rather implicitly defined) surface with
repeated copies of a certain motive. The visibility or not of the result
according to the surrounding text or space in the page has to be considered
therefore as a purely accidental (and noxious) side effect. The content
typesett via *\leaders* is not supposed in any way to disappear when
following lines are added.
I conclude that the only lawful use of *\leaders* in the true context of
*fleurons* would be for the generation of certain repetitive motives (for
instance a kind of small checkered board), but this is only a hint; I have
not explored this possibility.
Fortunately I have been able to advance in another direction and to get
what seems to me a consistent solution to the original problem. I open the
new thread *Using *fleurons** for explaining it more fully.
Regards
Francisco
[-- Attachment #1.2: Type: text/html, Size: 2301 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-10 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 15:07 Francisco Gracia [this message]
2013-11-10 21:21 ` Wolfgang Schuster
-- strict thread matches above, loose matches on Subject: below --
2013-11-04 22:48 Francisco Gracia
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=CACiybx5csP-yzKY5UjLAS53NaAbLSL+W9hMfYf44u6Zu2AnKHQ@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).