From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: bib and bibltx problems
Date: Tue, 24 Oct 2006 15:13:12 +0200 [thread overview]
Message-ID: <453E1168.8040600@elvenkind.com> (raw)
In-Reply-To: <453DFB07.20103@tttech.com>
Hi Matthias,
I goofed somewhere, that's for sure. Are you in a real hurry, or can
I take a day or two staring at it?
Taco
Matthias Wächter wrote:
> Hi Taco,
>
> I ran into the following problems:
>
> 1. see attached files. Three bib entries with different authors, but the
> resulting references are the same for two of them (!). Appearantly,
> without sorting the bib entries, the extra label numbering does not work
> correctly. Changing \setupbibtex to "sort=short" fixes the issue
> (appending "a" and "b") as well does changing "ITERATE {presort.none}"
> to "ITERATE {presort.clabel}" in cont-no.bst. But is this a
> once-and-for-all fix?
>
> 2. see attached files. In \setuppublications, numbering is given as
> "short", but the resulting list of references is only as good as "yes" -
> I only get the numbers, not the short references in the list. Hmmm,
> what's the cause for this? Any ideas? Or is it My Fault(TM)?
>
> 3. In general: If I'd use bib handwriting \{start,stop}publication
> without bibltx, would I have to care about the uniqueness of the "short"
> document names (the "s=" option to \startpublication)? Really?
> Considering hundreds of possible bibliography entries, this would double
> the effort: Not only the key (the "k=" option) but also the short name
> must be unique for correct references.
>
> 4. Sometimes, the build process ("texexec --pdf test") breaks after
> changing some text in the bibliography. Appearantly, sometimes the .bbl
> file is not updated. removing the .bbl file fixes the build. No recipy
> available, sorry.
>
> Thanks,
> - Matthias
>
>
> ------------------------------------------------------------------------
>
> \usemodule[bib]
> \usemodule[bibltx]
> \setupbibtex[database=mybibs,sort=no]
> \setuppublications[refcommand=short,numbering=short]
> \starttext For all times, \cite[TRUE] is right and \cite[FALSE] is wrong.
> \completepublications
> \stoptext
>
>
> ------------------------------------------------------------------------
>
> @techreport{TRUE,
> Title = "True Values",
> Author = "True Author",
> Year = "2005",
> }
>
> @techreport{GNUS,
> Title = "Gnus in the Wild",
> Author = "Another Doctor",
> Year = "2005",
> }
>
> @techreport{FALSE,
> Title = "False values",
> Author = "False Author",
> Year = "2005",
> }
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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
next prev parent reply other threads:[~2006-10-24 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 11:37 Matthias Wächter
2006-10-24 13:13 ` Taco Hoekwater [this message]
2006-10-24 13:22 ` Matthias Wächter
2006-11-02 8:11 ` Matthias Wächter
2006-11-04 16:50 ` new bib module Taco Hoekwater
2006-11-04 17:37 ` Thomas A. Schmitz
2006-11-04 17:43 ` Taco Hoekwater
2006-11-04 19:28 ` gnwiii
2006-11-04 21:41 ` Thomas A. Schmitz
2006-11-04 22:24 ` Taco Hoekwater
2006-11-05 12:12 ` gnwiii
2006-11-05 13:52 ` Taco Hoekwater
2006-11-05 17:30 ` gnwiii
2006-11-05 14:04 ` 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=453E1168.8040600@elvenkind.com \
--to=taco@elvenkind.com \
--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).