ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Beta bib module release
Date: Thu, 29 Sep 2005 16:50:36 +0200	[thread overview]
Message-ID: <433BFF3C.1060705@elvenkind.com> (raw)
In-Reply-To: <814CE5C7-8AA1-4197-B150-ADE9D399546D@uni-bonn.de>



Thomas A. Schmitz wrote:
> Hi Taco,
> 
> disregard most of what I wrote yesterday: most of your new module is  
> working fine, thanks so much! Haven't tested the new features yet,  but 
> will very soon. I'm especially thrilled by the \cite[right=]  command 
> and hope it works!
> 
> One major (but probably easy-to-fix) problem is that your wonderfully  
> clear syntax {<before}{<after>}{<instead>} isn't working anymore.  
> Here's an example. I have this line in my setup for books:
>     \insertseries{ (}{), }{, }%
> which used to work: if the entry has information about the series,  put 
> it in parentheses and append a comma, if it doesn't, just put the  
> comma. With the new module, I get an extra (), after every title, and  
> the same is true for other constructs.

I have found this bug, and uploaded a new beta:

   http://tex.aanhet.net/bib/m-bib-beta-20050929.zip

The output here looks a whole lot better now.

> One question: in the parsed bbl file, the bibtex field "address" is  
> translated into "city," "publisher" into "pubname," and "year" into  
> "pubyear." Is there a reason for this? I found it a bit confusing  
> because you have a macro \insertpublisher which inserts "city,  
> pubname"; coming from the names in the database, I couldn't figure  out 
> what was happening until I looked at the source. Would it be  possible 
> to just keep the fieldnames as bibtex has them?

I did this originally to be compatible with the old context
publications macros as well as the base tex definition of \year,
and I guess it is no longer safe to change the names now. I bit
of a mistake, in hindsight. :-(


> As for  the vertical spacing problem: depending on the font and the  
> settings for interlinespace, it is more or less visible. To see a  
> really clear case, try setting the interlinespace to something really  
> big like 5ex, then you can see that space within the entries is  regular 
> while space between entries is somewhat smaller.

Not over here. with \showgrid on, everything is precisely lined up.
That's why I really need an example of what you are doing.

Cheers, Taco

  reply	other threads:[~2005-09-29 14:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 13:02 Taco Hoekwater
2005-09-28 20:46 ` Thomas A.Schmitz
2005-09-28 20:51   ` Idris Samawi Hamid
2005-09-29  6:57   ` Taco Hoekwater
2005-09-29  7:49     ` Thomas A. Schmitz
2005-09-29 14:50       ` Taco Hoekwater [this message]
2005-09-30  7:16         ` Thomas A. Schmitz
2005-09-30 12:39           ` Taco Hoekwater
2005-09-30 14:22             ` Thomas A. Schmitz
2005-09-30 14:41               ` Taco Hoekwater
2005-09-30 15:24                 ` Thomas A. Schmitz
2005-10-01  8:04                   ` Christopher Creutzig
2005-10-01  8:37                     ` Thomas A. Schmitz

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=433BFF3C.1060705@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).