From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: New bibliography beta
Date: Fri, 16 Dec 2005 19:57:51 +0100 [thread overview]
Message-ID: <43A30E2F.5080802@elvenkind.com> (raw)
In-Reply-To: <3A1AE4F4-BD77-4659-80D0-F54DD0A32055@trichotomic.net>
David Wooten wrote:
> Greetings all, esp. Taco,
> I'm finally working with the new bib module, it works quite well. I've
> found one curiosity: I have a /defineparagraphs (semi?)-kludge in a
> modified bibl- file to take care of some wonky (but beautiful) layout
> demands. It worked perfectly in the last version:
>
> \defineparagraphs [bibpar]
> [n=3,before=\vskip -1.75\baselineskip,after=\vskip -1.25
> \baselineskip,distance=.2em,align={hz,hanging}]
Possibly because I added some unskips as a quick fix for whitespace
problems in the bibl- definitions. Try this:
\defineparagraphs [bibpar]
... after=\vskip -1.25\baselineskip\vskip1sp
(so using two skips in succession instead of just one)
If that doesn't work, then I need a more elaborate example.
Cheers, Taco
prev parent reply other threads:[~2005-12-16 18:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 18:18 David Wooten
2005-12-16 18:57 ` Taco Hoekwater [this message]
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=43A30E2F.5080802@elvenkind.com \
--to=taco@elvenkind.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).