[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Run-in heading for abstract
From: |
Michael Piotrowski |
Subject: |
Re: Run-in heading for abstract |
Date: |
25 Jul 2001 17:09:27 +0200 |
User-agent: |
Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Bryce Canyon) |
"Valeriy E. Ushakov" <address@hidden> writes:
> On Wed, Jul 25, 2001 at 15:34:12 +0200, Michael Piotrowski wrote:
>
> > I'm currently trying to get an abstract (report) with a run-in
> > heading, i.e., something like this:
> >
> > Abstract: Lorem ipsum dolor sit amet, consectetuer adipiscing elit,
> > sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna
> > aliquam erat volutpat.
>
> BTW :), do you know that this "canonical" text is trimmed badly?
> Here's the full text of that paragraph (I capitalized the "lorem
> ipsum"), quoted after
[...]
Yes, I knew that; and I think it's funny that in typesetting, the
mangled text is now maybe even more of a classic than Cicero's
original...
> > Unfortunately, setting
> >
> > @AbstractFormat { @Title: @Body }
> >
> > doesn't work if the abstract consists of multiple paragraphs.
>
> Yep. Because you've got, effectively:
>
> @Title: &1s @OneRow { some text @PP next para ... }
Uh huh, I suspected something like this...
> That's the situation @Insert is for:
>
> @AbstractFormat { { @Title: &1s } @Insert @Body }
>
> So to say, @Insert doesn't operate on objects, it operates at the
> parse tree level, inserting it's left paramter as if it was,
> textually, the start of its right parameter. I.e. the result will be
>
> { @Title: &1s some text @PP next para ... }
Thanks a lot, that's exactly what I wanted! I just looked up @Insert
in the Expert's Guide--it's easy to find if you know what you're
looking for ;-) I think I learned something...
Greetings
--
Michael Piotrowski, M.A. <address@hidden>