From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: a footnote bug?
Date: Fri, 20 Aug 2004 16:49:32 +0200 [thread overview]
Message-ID: <a06002001bd4bbf3f47de@[62.134.72.246]> (raw)
Hi Hans,
I'm very sorry - maybe i'm blind today - but I can't see any change.
What does "headcommand=\llap" actually mean?
I tried with various parameter, but again no effect.
Could you give a small example please?
Steffen
> >>>Does this distance cannot be adjusted?
> >>>
> >>>
> >>>
> >>>
> >>can you make me a small demo file?
> >>
> >>Hans
> >>
> >>
> >
> >
> >
> >
> >Yes, sure.
> >I just made a frame around the footnote number so you'll can clearly see the gap:
> >
> >\def\myFNnumber#1{\inframed[width=\leftmarginwidth,offset=.0em,frame=on,align=left]{#1}}
> >\setupfootnotedefinition[command=\myFNnumber,location=inleft]
> >\setuppagenumbering [alternative=doublesided,location={header,right}]
> >\showframe \showgrid
> >
> >\starttext
> >test\footnote{first note}
> >\page testest\footnote{second note}
> >\stoptext
> >
> >
> this is not so much a bug but a missing feature -)
>
> in cont-new.tex, add:
>
> \startconstants dutch english
> german czech
> italian romanian
>
> kopcommando: kopcommando headcommand
> headcommand headcommand
> headcommand headcommand
>
> \stopconstants
>
> \unprotect
> \setvalue{@@definitie\v!commando}#1{\do@@definitie{\executeifdefined{\??dd#1\c!kopcommando}\framed}{#1}}
> \protect
>
> Now you can say:
>
> \setupfootnotedefinition[location=command,headcommand=\llap]
>
> and go wild with putting footnote markers anywhere
>
> Hans
next reply other threads:[~2004-08-20 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 14:49 Steffen Wolfrum [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-18 20:01 Steffen Wolfrum
2004-08-20 9:40 ` Hans Hagen
2004-08-18 13:10 Steffen Wolfrum
2004-08-18 15:00 ` Hans Hagen
2004-08-18 13:09 esther+steffen
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='a06002001bd4bbf3f47de@[62.134.72.246]' \
--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).