From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: First document — problems with bib module and layout
Date: Fri, 28 Dec 2007 15:27:49 +0100 [thread overview]
Message-ID: <477507E5.6000706@elvenkind.com> (raw)
In-Reply-To: <200712271951.10673.matija.suklje@rutka.net>
Matija Šuklje wrote:
> Dne četrtek 27. decembra 2007 je Taco Hoekwater napisal(a):
>> The solution is probably along the lines of
>> [...]
>> More tomorrow, maybe. You have picked the worst possible time to ask
>> me about computer stuff. ;-)
>
> Thanks, will try tomorrow. My day has been amazingly awful as well. I'll
> probably just do additions to the pf_ul.tex file where I think I'm on halfway
> familiar ground already.
Your pf_ul.tex had a spurious (or incomplete) \insert command at
the end, that is what was causing an error problems "Missing number".
For the footnoted references, this seems to work:
% two new fields, for use in \mycite
\newbibfield[avtor]
\newbibfield[kratko]
% footnote-based definition of \cite, with extra data
\def\mycite[#1][#2]%
{\bgroup
% this adds the reference to the publication list
% in the back:
\nocite[#2]%
% you can get all single-valued fields with this
% \commands (title,issue,journal etc.) but not the
% \author,\artauthor and \editor because they have
% special arguments:
\getcitedata[avtor][#2] to \localavtor
\getcitedata[kratko][#2] to \localkratko
% you may want more fields and/or better formatting:
\footnote{\localavtor, \localkratko, #1}%
\egroup}
% use is like so:
This is known\mycite[str. IV-VI in XI][bavcon_zkp]
% this setup needs the extra \avtor and \kratko in the bbl file :
\startpublication[
k=bavcon_zkp,
a=Bavcon,
t=clanek,
y=2003]
\title{Na rob peti noveli zakona o kazenskem postopku}
\kratko{Na rob}
\avtor{L. Bavcon}
\author{Ljubo}[L.]{}{Bavcon}
\journal{Pravna praksa}
\volume{22}
\issue{6/7}
\pubyear{2003}
\stoppublication
You are operating on the border of what is doable for the current
bibliographic module, and I have no time to spend a month on a rewrite
just now, so if this is still not good enough, you are out of luck.
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-28 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-25 22:39 Matija Šuklje
2007-12-26 11:15 ` Taco Hoekwater
2007-12-26 22:50 ` Matija Šuklje
2007-12-27 10:38 ` Matija Šuklje
2007-12-27 10:56 ` Matija Šuklje
2007-12-27 15:46 ` Taco Hoekwater
2007-12-27 18:51 ` Matija Šuklje
2007-12-28 14:27 ` Taco Hoekwater [this message]
2007-12-29 12:20 ` Matija Šuklje
2007-12-29 19:06 ` Aditya Mahajan
2007-12-29 20:06 ` Matija Šuklje
2008-04-06 18:51 ` Matija Šuklje
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=477507E5.6000706@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).