From: "Derek Schmidt" <derekschmidt@gmail.com>
Subject: Re: typesetting verse?
Date: Wed, 23 Aug 2006 20:22:41 -0400 [thread overview]
Message-ID: <221cc89e0608231722s30bfeb6es3826a0eba287ecad@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0608231837400.784@nqvgln>
Ok guys, thanks. I eventually went with this:
\setupindenting[medium,first]
\def\startverse%
{\bgroup
\setupinterlinespace[medium]
\setuplines[indenting=yes]
\startlines}
\def\stopverse%
{\stoplines
\endgraf\egroup}
On 8/23/06, Aditya Mahajan <adityam@umich.edu> wrote:
> On Wed, 23 Aug 2006, Derek Schmidt wrote:
>
> > Aditya,
> >
> > With the first group of code, I get "indenting=yes" actually appearing
> > in there; yet the lines aren't indented or closer together
> > (vertically). I removed the '%' but that didn't seem to make a
> > difference.
>
> Sorry, that should have been \setuplines[indenting=yes]. Have a look
> at the code posted by Hans sometime back.
>
> Aditya
>
> > On 8/23/06, Aditya Mahajan <adityam@umich.edu> wrote:
> >> On Tue, 22 Aug 2006, Derek Schmidt wrote:
> >>
> >>> Hi,
> >>>
> >>> Another simple question--have at it!
> >>>
> >>> I'd like to typeset some poetry. It should be
> >>
> >>> indented,
> >>
> >> \startnarrower .... \stopnarrower
> >>
> >>> obey lines,
> >>
> >> \startlines ... \stoplines (it is more customizable than \obeylines)
> >>
> >> You can actually say
> >>
> >> \setupindenting[medium] \startlines[indenting=yes] (other options are
> >> no, yes, odd, even) and see which one you like.
> >>
> >>> and the lines should be close together, not like separate paragraphs.
> >>
> >> \setupinterlinespace[line=2em] .... \endgraf (default is 2.4 em)
> >>
> >>> So far I've got
> >>>
> >>> \definestartstop[verse][commands=\obeylines]
> >>
> >> So you can try
> >>
> >> \def\startverse%
> >> {\bgroup
> >> \setupinterlinespace[line=2em]
> >> \startlines[indenting=yes]}
> >>
> >> \def\stopverse%
> >> {\stoplines
> >> \endgraf\egroup}
> >>
> >>
> >> You could have also done the equivalent
> >>
> >> \definestartstop[verse][before={\setupinterlinespace[line=2em]\startlines},
> >> after={\stoplines\endgraf}]
> >>
> >> Aditya
> >> _______________________________________________
> >> ntg-context mailing list
> >> ntg-context@ntg.nl
> >> http://www.ntg.nl/mailman/listinfo/ntg-context
> >>
> > _______________________________________________
> > ntg-context mailing list
> > ntg-context@ntg.nl
> > http://www.ntg.nl/mailman/listinfo/ntg-context
> >
> >
> >
>
> --
> Aditya Mahajan, EECS Systems, University of Michigan
> http://www.eecs.umich.edu/~adityam || Ph: 7342624008
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2006-08-24 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 3:39 Derek Schmidt
2006-08-23 4:24 ` Aditya Mahajan
2006-08-23 22:35 ` Derek Schmidt
2006-08-23 22:38 ` Aditya Mahajan
2006-08-24 0:22 ` Derek Schmidt [this message]
2006-08-23 8:09 ` Hans Hagen
2006-08-23 14:44 ` Aditya Mahajan
2006-08-23 22:17 ` Hans Hagen
2006-08-23 14:02 ` John R. Culleton
2006-08-23 14:12 ` Derek Schmidt
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=221cc89e0608231722s30bfeb6es3826a0eba287ecad@mail.gmail.com \
--to=derekschmidt@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).