From: Florian Wobbe <Florian.Wobbe@awi.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setuppublications problem
Date: Sat, 12 Mar 2011 11:45:16 +0100 [thread overview]
Message-ID: <430B533D-33EE-4697-94E0-04DB7744060A@awi.de> (raw)
In-Reply-To: <web-6658865@be2.uni-bonn.de>
> Have you tried \placepublications[criterium=all] or \placepublications[criterium=text]?
Hi Thomas,
you gave me exactly the same hint last week. We should add criterium=cite and criterium=text to the Wiki (Bibliography MKIV page: http://wiki.contextgarden.net/Bibliography_mkiv).
In the beginning it was not clear to me, that http://wiki.contextgarden.net/Bibliography refers to the MKII implementation of Taco. Therefore, I would suggest to rename Bibliography to Bibliography_mkii and create an alias Bibliography that redirects to Bibliography_mkiv instead. In the wiki pages Bibliography_mkiv and Bibliography_mkii the first sentence should state that the page is related to mkii/mkiv only and link to the other page. Do you think this is reasonable?
I would like to add a section on customising bibstyle files and add space for sharing reference styles of different journals. What do you think?
In general I find it difficult to differentiate between mkiv and mkii related information in the wiki. How could we better structure the wiki to make it easier for the reader? Disambiguation pages, mkiv/mkii sections, independent pages with mkiv/mkii in headerline?
Best,
Florian
___________________________________________________________________________________
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:[~2011-03-12 10:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:38 Jean Magnan de Bornier
2011-03-11 12:00 ` Thomas A. Schmitz
2011-03-12 7:37 ` Jean Magnan de Bornier
2011-03-12 10:09 ` Thomas Schmitz
2011-03-12 10:36 ` Jean Magnan de Bornier
2011-03-12 10:45 ` Florian Wobbe [this message]
2011-03-12 11:08 ` Thomas Schmitz
2011-03-12 12:21 ` Ideas for restructuring the ConTeXt garden? Florian Wobbe
2011-03-12 13:05 ` Marco
2011-03-12 14:08 ` Mojca Miklavec
2011-03-12 16:20 ` Procházka Lukáš
2011-03-12 20:02 ` Jaroslav Hajtmar
2011-03-12 20:08 ` C.
2011-03-12 23:04 ` Pontus Lurcock
2011-03-14 7:46 ` Taco Hoekwater
2011-03-14 20:26 ` Mojca Miklavec
2011-03-14 21:15 ` mathew
2011-03-13 7:01 ` Vnpenguin
2011-03-13 4:48 ` mathew
2011-03-13 5:03 ` Pontus Lurcock
2011-03-13 6:25 ` luigi scarso
2011-03-13 7:42 ` Minimals (was: Ideas for restructuring the ConTeXt garden?) Alan BRASLAU
2011-03-13 7:56 ` Minimals Taco Hoekwater
2011-03-13 8:22 ` Minimals luigi scarso
2011-03-13 21:35 ` Minimals (was: Ideas for restructuring the ConTeXt garden?) Henning Hraban Ramm
2011-03-14 7:40 ` Mojca Miklavec
2011-03-14 13:04 ` Ideas for restructuring the ConTeXt garden? Carlos Breton Besnier
2011-03-14 15:16 ` Carlos Breton Besnier
2011-03-16 12:37 ` Vedran Miletić
2011-04-26 10:27 ` Ian Lawrence
2011-03-14 15:17 ` Carlos Breton
2011-03-12 16:02 ` \setuppublications problem John Haltiwanger
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=430B533D-33EE-4697-94E0-04DB7744060A@awi.de \
--to=florian.wobbe@awi.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).