From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: indented footnotes
Date: Wed, 26 Jul 2006 15:17:59 +0200 [thread overview]
Message-ID: <B077847F-8B60-4E41-A81E-6F05C8F70163@st.estfiles.de> (raw)
In-Reply-To: <2C417A37-E98D-418D-A470-A546FEC21D7E@st.estfiles.de>
> Hi,
>
> I want my footnotes (bottom page) to be indented first line.
> So I tried this
>
> \setupfootnotes[indentnext=yes,numbercommand=\hskip1em\high]
> \setupfootnotedefinition
> [indentnext=yes,distance=0.5em,location=serried]
>
> But "\hskip1em" is now the distance to the right corner of the
> footnote's number.
This one looks *quite* good:
\def\myFNnumber#1{\hskip1.5em\inframed[width=2em,offset=.
0em,frame=off,align=right]{#1}}
\setupfootnotedefinition[command=
\myFNnumber,indentnext=yes,location=serried]
But I have to define "\hskip1.5em" in order to get real 1em space
before the frame!
So I guess it's not a very healthy code.
Someone has a better suggestion?
Steffen
next prev parent reply other threads:[~2006-07-26 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 12:53 Steffen Wolfrum
2006-07-26 13:17 ` Steffen Wolfrum [this message]
2006-07-26 14:13 ` Peter Rolf
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=B077847F-8B60-4E41-A81E-6F05C8F70163@st.estfiles.de \
--to=context@st.estfiles.de \
--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).