ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Scott Steele <scottlsteele@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: Re: Multiple pleas for help (long)
Date: Sun, 6 Jun 2010 20:03:02 -0400	[thread overview]
Message-ID: <AANLkTimkMh6X11aUoXnpVuu1M9cs00Aq4yMlNbnqpQPE@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 4010 bytes --]

>
> Am 01.06.10 00:29, schrieb Scott Steele:

> If anyone has any insight on how to keep the footnotes from having

> their numbers in the margin and from having line-breaks after each

> one, that is the only issue from the original email that is still

> unsolved, I think.

>

> ———

>

> In Latex, \fancybreak was part of a package called, I believe,

> fancyheader or fancypage. It produced a break frequently seen in

> published prose (I'm currently reading {\em Bluebeard} where Kurt

> Vonnegut uses it liberally) with significant vertical space between

> two paragraphs and, centered both in that vertical space as well as

> horizontally, a number of well-spaced marks. There are usually 3

> marks, and they are frequently asterisks or traditional

> dingbats/fleurons. This sort of break is generally used when the

> author wishes to indicate a break more significant than a change in

> paragraph but short of an outright new chapter.

>

> \def\FancyBreak{\par\blank\hfill* * *\hfill\hfill\par\blank}

> \starttext

> \input tufte

> \FancyBreak

> \input tufte

> \stoptext

>

> I don't understand why I need the two consecutive \hfill's at the end

> for the marks to be centered, but the definition works well for me.


> \unprotect


> \def\????fb{@@@@fb}


> \getparameters

[\????fb]

[\c!spacebefore=,

\c!spaceafter=]


> \def\fancybreakparameter#1%


>
> {\csname\????fb\ifcsname\????fb\currentfancybreak#1\endcsname\currentfancybreak\fi#1\endcsname}


> \def\setupfancybreak

{\dodoubleempty\dosetupfancybreak}


> \def\dosetupfancybreak[#1][#2]%

{\ifsecondargument

\getparameters[\????fb#1][#2]%

\else

\getparameters[\????fb][#1]%

\fi}


> \def\definefancybreak

{\dodoubleempty\dodefinefancybreak}


> \def\dodefinefancybreak[#1][#2]%

{\ifsecondargument

\getparameters[\????fb#1][#2]%

\fi

\setvalue{#1}{\dofancybreak{#1}}}


> \def\dofancybreak#1%

{\begingroup

\edef\currentfancybreak{#1}%

\everyvbox{\raggedcenter}%

\dowithnextbox

{\blank[\fancybreakparameter\c!spacebefore]%

\flushnextbox

\blank[\fancybreakparameter\c!spaceafter]%

\endgroup}

\normalvbox}


> \definefancybreak[fancybreak]


> \protect


> \starttext

\input knuth

\fancybreak{$* * *$}

\input ward

\stoptext


> Wolfgang


>
> ___________________________________________________________________________________




Thanks a lot for all of that! I'm having trouble getting it to run, though.
I tried copy/pasting it into the Context Live site but get

! Argument of \fancybreakparameter has an extra }.
<inserted text>
                \par
<to be read again>
                   }
\edefconvertedargument #1#2->\edef #1{#2}
                                         \edef #1{\detokenize \@EA {#1}}
\docomplexdoblank ...convertedargument \ascii {#1}
                                                  \ifcsname \??bo \??bo \asc...

\dodowithnextbox ...reakparameter \c!spacebefore ]
                                                  \flushnextbox \blank [\fan...
l.52 \fancybreak{$* * *$}

?
! Emergency stop.
<inserted text>
                \par
<to be read again>
                   }
\edefconvertedargument #1#2->\edef #1{#2}
                                         \edef #1{\detokenize \@EA {#1}}
\docomplexdoblank ...convertedargument \ascii {#1}
                                                  \ifcsname \??bo \??bo \asc...

\dodowithnextbox ...reakparameter \c!spacebefore ]
                                                  \flushnextbox \blank [\fan...
l.52 \fancybreak{$* * *$}



Thanks,

Scott
-----
This is a work of fiction.  Names, characters, places, and incidents either
are the product of the writer's imagination or are used fictitiously, and any
resemblance to actual persons, living or dead, businesses, companies,
events, or locales is entirely coïncidental.

[-- Attachment #1.2: Type: text/html, Size: 24751 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________

             reply	other threads:[~2010-06-07  0:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07  0:03 Scott Steele [this message]
2010-06-07  8:55 ` Wolfgang Schuster
2010-06-20 12:45 ` Wolfgang Schuster
  -- strict thread matches above, loose matches on Subject: below --
2010-05-31 22:29 Scott Steele
2010-06-01 20:36 ` Wolfgang Schuster
2010-06-02 19:18 ` Wolfgang Schuster
2010-05-10  0:28 Scott Steele
2010-05-13 14:48 ` Wolfgang Schuster
2010-04-26 22:44 Scott Steele
2010-04-27  7:47 ` Wolfgang Schuster
2010-04-27  7:55 ` R. Bastian
2010-04-27  9:16 ` Mojca Miklavec

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=AANLkTimkMh6X11aUoXnpVuu1M9cs00Aq4yMlNbnqpQPE@mail.gmail.com \
    --to=scottlsteele@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).