From: "Thomas Schmitz" <tschmit1@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bib problems
Date: Fri, 10 Dec 2010 14:55:11 +0100 [thread overview]
Message-ID: <web-5984644@be2.uni-bonn.de> (raw)
In-Reply-To: <AANLkTikcWidggS+ZHRcCH+1qKeHZ1xWqN1yx+bY4k0_e@mail.gmail.com>
On Fri, 10 Dec 2010 14:18:20 +0100
Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote:
> I should think about it a bit. But just a few
>possibilities ... At the
> moment I use:
> \startpublication
> [k=xy,
> t=xy]
> ....
> \stoppublication
>
> Options are:
When we think from the bibtex side, it would boil down to
processing the "keyword=" key (which is already there in
the bibtex specification). You could then order your
"publications" with terms such as "keyword=image"
"keyword=article" etc.
>
> 1.)
> \startpublicationlist[images] or
>\startpublications[images] or ...
> \startpublication[k=xy,t=xy]
> ....
> \stoppublication
> ...
> \stoppublicationlist
>
> 2.)
> \startpublication[k=xy,t=xy,list=images]
> ....
> \stoppublication
>
> 3.)
> \startpublication[images][k=xy,t=xy]
> ....
> \stoppublication
>
> And then
> \placepublications[list=images]
>
> Then \cite would work in exactly the same way (one would
>not need to
> provide any extra key to cite itself).
>
> But one would need to think of a proper model to number
>the
> references. That is: it would have to be configurable to
>be able to
> either number images with roman instead of arabic
>numerals (or with a,
> b, c, ...), or to prepend something, like [img1],
>[img2], [img3]
> instead of [1], [2], [3]. Or simply let the user do "in
> \cite{figure}[xy]", or to number images with numbers
>bigger than other
> references. For example:
>
> Books:
> [1]
> [2]
> [3]
> Articles:
> [4]
> [5]
> [6]
> [7]
> Images:
> [8]
> [9]
>
> or
>
> Books:
> [1]
> [2]
> [3]
> Articles:
> [a1]
> [a2]
> [a3]
> [a3]
> Images:
> [i1]
> [i2]
>
> or any other user-configurable option for numbering ...
>
> However, having a properly designed model is better than
>having some
> ad-hoc solution that turns out not flexible enough or
>clumsy to use
> and buggy later on ...
One syntax would be
\placepublications[filter=image,prefix={img.},option=continue,numberconversion=romannumbers]
>
> And yes, something that would allow splitting references
>across
> sections could just as well be used for this. It just
>needs to be
> designed properly ... (But section-based bibliography
>could work
> without any extra key, right?)
>
> And no, please don't count it as bug report. I just
>mentioned it
> because Hans wanted to have "a big bunch of everything
>at a single
> place".
>
> I suggest to reopen the topic and create exact
>specification before
> the actual implementation.
Yes, we can discuss it (on or off list) when it will be
implemented.
Thomas
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-10 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 11:54 Thomas A. Schmitz
2010-12-07 14:26 ` Mojca Miklavec
2010-12-07 15:01 ` Hans Hagen
2010-12-10 13:18 ` Mojca Miklavec
2010-12-10 13:55 ` Thomas Schmitz [this message]
2010-12-08 10:49 ` Florian Wobbe
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 9:32 Robert Blackstone
2010-12-08 9:08 Robert Blackstone
2010-12-08 10:47 ` Matija Šuklje
2010-12-10 10:28 ` Thomas Schmitz
2010-12-01 10:35 Thomas A. Schmitz
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=web-5984644@be2.uni-bonn.de \
--to=tschmit1@uni-bonn.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).