ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan BRASLAU <alan.braslau@cea.fr>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	thomas.schmitz@uni-bonn.de
Subject: Re: bibliography (interaction)
Date: Sat, 23 Mar 2013 12:50:06 +0100	[thread overview]
Message-ID: <20130323125006.69595c7c@iram-hb-003386.extra.cea.fr> (raw)
In-Reply-To: <514D72BD.6030009@wxs.nl>

On Sat, 23 Mar 2013 10:15:41 +0100
Hans Hagen <pragma@wxs.nl> wrote:

> > So, playing with a minimal example reveals that interaction does not
> > work when refcommand is set to authoryear, for example.
> > (removing the setuppublications below gives working hyperlinks).
> > Is this a bug?  
> 
> probably a mkii left-over (prevent breaking big hyperlinks) .. can
> you try with
> 
> \unexpanded\def\bibmaybeinteractive#1#2%
>    {\doifbibinteractionelse{\gotobiblink{#2}[#1]}{#2}}

Replacing bibmaybeinteractive in bibl-tra.mkiv with the above indeed
fixes the hyperlink. Thank you!



I have two further questions concerning bibliographies:

1. I would like to produce a list of authors, an index of names.
I am playing with list[pubs], but have not understood this yet. 
And I would like to add other names to this list, authors that are
named but not necessarily cited. I am sure that this is do-able and I
will try to figure it out, but would welcome any further hints. :)


2. Using \placepublications [criterium=chapter]
in order to put a list of references at the end of each chapter
has a side effect, probably a feature, that a citation in a later
chapter to a cited reference from an earlier chapter will *not* repeat
the reference in the later chapter's list of references. This seems
somewhat confusing to the reader but indeed is most likely a feature.

I see two solutions:

A. Better organization of the text so that this confusing situation
does not arise, either rewriting or else having the list of references
come at the end of all of the chapters involved, perhaps grouped in a
common structure such as a part.

B. Allowing a repeat of the publication in all the pertinent lists,
perhaps as an optional setting.

What do the bibliographical specialists think?

Alan
___________________________________________________________________________________
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
___________________________________________________________________________________


      reply	other threads:[~2013-03-23 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 21:14 Alan BRASLAU
2013-03-21 21:32 ` Thomas A. Schmitz
2013-03-21 21:53   ` Hans Hagen
2013-03-21 22:27   ` Alan BRASLAU
2013-03-23  7:39   ` Alan BRASLAU
2013-03-23  9:15     ` Hans Hagen
2013-03-23 11:50       ` Alan BRASLAU [this message]

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=20130323125006.69595c7c@iram-hb-003386.extra.cea.fr \
    --to=alan.braslau@cea.fr \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=thomas.schmitz@uni-bonn.de \
    /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).