ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: bibmodule + project
Date: Wed, 14 Dec 2005 23:42:04 +0100	[thread overview]
Message-ID: <52A370A4-785A-4FE7-8EFD-B0454BE942DE@uni-bonn.de> (raw)
In-Reply-To: <43A06560.5050409@elvenkind.com>

Taco,

thanks a lot! Your bibtex module is an amazing one-man-show! Yes,  
this seems to work: having
\setupbibtex[database=bibliography]

in the products.tex file and a line

\usepublications[products]

in the components. I needed several runs of ConTeXt to get rid of  
many ?? when typesetting single components, but now it appears to  
work. More about this book project soon. (I'm negotiating with my  
publisher, Blackwell. They want it "typeset professionally," and I'm  
trying to convince them that typesetting doesn't get any more  
professional than that...).

Best

Thomas

On Dec 14, 2005, at 7:33 PM, Taco Hoekwater wrote:

>
> Hi Thomas,
>
> The beta has some code to deal with use of multiple bibliographies
> withing projects/products, the current one in the distribution does
> not.
>
> The beta is on my website, linked from :
> http://wiki.contextgarden.net/User::Taco/Bib
>
> The mailing list thread about 'multiple bibs' is here:
> http://archive.contextgarden.net/message/ 
> 20051003.000309.57881f41.en.html
>
> Biggest problem: I am not sure what the desired/correct functionality
> would be.
>
> If I understand your case correctly (with many components of a  
> single product, and a unified bibliography at the end of the full  
> product),
> then you probably should do the setupbibtex only in the product file
> (and creating products.bbl); and execute  only "\usepublications 
> [products]" in each component.
>
> But that's guesswork,  not prescription, and not a reliable advice. If
> can give me and exact description of your wishes, then I can create a
> new beta with your desires in mind.
>
> Cheers,
>
> Taco
>
> Thomas A. Schmitz wrote:
>> Hi all,
>> a question for the many happy users of Taco's bibmodule: I'm in  
>> the  process of splitting a larger project into several  
>> components. What I  have is:
>> transl.tex           --> main project file
>> environment.tex      --> environment for all components
>> products.tex         --> list of components
>> component1.tex
>> component2.tex
>> .
>> .
>> .
>> Index, TOC etc. seem to be working very well, but I can't get the   
>> bibliographic references right when compiling. Where should the  
>> call  to bibmodule reside, and how can I run bibtex on such a  
>> project?
>> Thanks
>> Thomas
>> _______________________________________________
>> ntg-context mailing list
>> ntg-context@ntg.nl
>> http://www.ntg.nl/mailman/listinfo/ntg-context
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

      parent reply	other threads:[~2005-12-14 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 10:47 Thomas A. Schmitz
2005-12-14 18:33 ` Taco Hoekwater
2005-12-14 18:38   ` Taco Hoekwater
2005-12-14 22:42   ` Thomas A. Schmitz [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=52A370A4-785A-4FE7-8EFD-B0454BE942DE@uni-bonn.de \
    --to=thomas.schmitz@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).