From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \inmargin / full textwidth line interaction (was Toward the use of inleft…)
Date: Fri, 26 Nov 2010 11:52:38 +0100 [thread overview]
Message-ID: <130129C8-22F5-467D-A6CB-A443381EB54A@gmail.com> (raw)
In-Reply-To: <4CEEC6AA.6030906@nibua-r.org>
Am 25.11.2010 um 21:27 schrieb Renaud AUBIN:
> Since my previous post doesn't seem inspiring at all (sniff), here is a
> simplified and more precise description of what need to be done:
>
> [...]
\setupbodyfont[10pt]
\setuplayout
[leftedge=0mm,
leftmargin=45mm,
rightedge=0mm,
rightmargin=0mm,
backspace=60mm,
topspace=10mm,
bottomspace=10mm,
header=0mm,
headerdistance=0mm,
footer=0mm,
footerdistance=0mm,
margindistance=0mm,
height=middle,
width=middle,
grid=yes]
\setuppagenumbering[state=stop]
\setuphead[section] [style=,command=\SectionCommand]
\setuphead[subsection][style=,command=\SubsectionCommand]
\define[2]\SectionCommand
{\inleftmargin{\leftaligned{\structuretitle}}%
\blackrule
[ width=\textwidth,
height=+.3\lineheight,
depth=-.2\lineheight]}
\define[2]\SubsectionCommand
{\vbox\bgroup
\inleftmargin{\leftaligned{\em\structureuservariable{date}}}%
{\bfa\structuretitle}\wordright{\tfx\structureuservariable{topic}}
\blank
{\em\structureuservariable{info}}%
\egroup}
\starttext
\startsection[title={A Section}]
\startsubsection
[title={The detailled topic (which takes more than one line)}]
[date={The date},topic={Knuth’s topic},info={some text}]
\input knuth
\stopsubsection
\startsubsection
[title={The detailled topic (which takes more than one line)}]
[date={Another date},topic={Zapf},info={some text}]
\input zapf
\stopsubsection
\stopsection
\startsection[title={Section}]
\startsubsection
[title={Some details}]
[date={A date},topic={Tufte}]
\input tufte
\stopsubsection
\stopsection
\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:[~2010-11-26 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 18:32 Toward the use of inleft for custom section's command… or not… Renaud AUBIN
2010-11-25 20:27 ` \inmargin / full textwidth line interaction (was Toward the use of inleft…) Renaud AUBIN
2010-11-26 10:52 ` Wolfgang Schuster [this message]
2010-11-26 19:25 ` BUG? Strange behavior (vertical space added!!!) with accentuated letters (was \inmargin / full textwidth line interaction) Renaud AUBIN
2010-11-26 21:06 ` Renaud AUBIN
2010-11-27 8:17 ` Otared Kavian
2010-11-27 8:57 ` Strange behavior (vertical space added!!!) with accentuated letters Wolfgang Schuster
2010-11-27 12:03 ` Renaud AUBIN
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=130129C8-22F5-467D-A6CB-A443381EB54A@gmail.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).