ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bibliography authoryears problem
Date: Fri, 04 Dec 2009 19:32:42 +0100	[thread overview]
Message-ID: <4B1955CA.4000307@wxs.nl> (raw)
In-Reply-To: <E6B13DDB-A078-4950-B88A-8F0B738480D2@gmail.com>

Michael Green wrote:
> On Dec 4, 2009, at 3:00 AM, ntg-context-request@ntg.nl wrote:
> 
>>
>> Message: 4
>> Date: Fri, 04 Dec 2009 09:23:13 +0100
>> From: Taco Hoekwater <taco@elvenkind.com>
>> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
>> Subject: Re: [NTG-context] bibliography authoryears problem
>> Message-ID: <4B18C6F1.5090803@elvenkind.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> Hi,
>>
>> Michael Green wrote:
>>> When using refcommand=authoryears and Mk IV the first reference is
>>> formatted incorrectly.
>>>
>>> There is the left parenthesis, then a line break, then the rest of the
>>> reference followed by the right parenthesis.
>>
>> Here is the cause: the first \cite in mkiv internally runs
>> \usepublications[\jobname]. This inputs bib-test.bbl, which
>> contains a \par, and that is where the new line comes from.
>>
>> A workaround is to add
>>
>>   \usepublications[\jobname]
>>
>> in the document preamble.
>>
>> It works in mkii because in mkii, that command is executed at
>> \starttext.
>>
>> For Hans: perhaps \usemodule[bib] should run the command? I know that
>> is supposed to be obsolete, but I assume you do not want to use the
>> odd logic from mkii in mkiv.
>>
>> Best wishes,
>> Taco
>>
> 
> That solves both the problems I noted. Thanks!

\unprotect

\def\dousepublications#1%
   {\doonlyonce{#1.\f!bibextension}
      {\let\@@savedpar\par
       \let\par\ignorespaces
       \ifhmode\kern\zeropoint\fi
       \readfile{#1.\f!bibextension}
         {\showmessage\m!publications{4}{#1.\f!bibextension}}
         {\showmessage\m!publications{2}{#1.\f!bibextension}}%
       \ifhmode\removeunwantedspaces\fi
       \let\par\@@savedpar}}

\protect

should also work ... the reason for the automatic loading is that it 
circumvents problems with projects, products, components etc where 
settings can come after teh first starttext so that's not the best hook 
then

of course implicit loading as suggested by taco is the best


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2009-12-04 18:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3.1259924403.8230.ntg-context@ntg.nl>
2009-12-04 15:57 ` texshow Wolfgang Werners-Lucchini
2009-12-04 16:02   ` texshow Wolfgang Schuster
2009-12-04 18:19 ` bibliography authoryears problem Michael Green
2009-12-04 18:32   ` Hans Hagen [this message]
2009-12-04 18:38     ` Wolfgang Schuster
2009-12-04 18:46       ` Hans Hagen
     [not found] <mailman.860.1259862604.22155.ntg-context@ntg.nl>
2009-12-03 19:14 ` Michael Green
2009-12-03  0:26 Michael Green
2009-12-03 17:27 ` Bernhard Rosensteiner
2009-12-03 17:36   ` Hans Hagen
2009-12-03 18:51 ` Taco Hoekwater
2009-12-04  8:23 ` Taco Hoekwater
2009-12-04 18:31   ` Wolfgang Schuster
2009-12-04 18:35     ` Hans Hagen
2009-12-04 18:43     ` Hans Hagen

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=4B1955CA.4000307@wxs.nl \
    --to=pragma@wxs.nl \
    --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).