ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Questions on new bibliography system (btx)
Date: Tue, 21 Feb 2017 19:38:11 -0500	[thread overview]
Message-ID: <a22b8da9-13d6-d12e-bb7e-f50385943100@rik.users.panix.com> (raw)
In-Reply-To: <20170221170940.0ae7a637@zoo.hsd1.co.comcast.net>

On 2017-02-21 19:09, Alan Braslau wrote:
> On Tue, 21 Feb 2017 18:46:18 -0500
> Rik Kabel <context@rik.users.panix.com> wrote:
>
>> I have a few questions about the new bibliography system. The
>> following example code illustrates the problems.
>>
>>      \startbuffer[TestBib]
>>      @OTHER{Author1975a,
>>         author = {An Author},
>>         title = {A title},
>>         year = {1975},
>>      }
>>      @OTHER{Author1975b,
>>         author = {Author, An},
>>         title = {Another title},
>>         year = {1975},
>>      }
>>      @OTHER{Else1975a,
>>         author = {Somebody Else},
>>         title = {A third title},
>>         year = {1975},
>>      }
>>      @OTHER{Else1975b,
>>         author = {Somebody Else},
>>         title = {A last title},
>>         year = {1975},
>>      }
>>
>>      @FILM{Movie,
>>         producer     = {Normal Name},
>>         director     = {Funny Name},
>>         title        = {Who Knew?},
>>         year         = {2010},
>>         publisher    = {Producer},
>>         address      = {Hollywood}
>>      }
>>
>>      @INBOOK{Subtitle,
>>         author       = {Sally Subtitle-Spacing},
>>         title        = {Another Country},
>>         year         = {1958},
>>         publisher    = {Publisher},
>>         address      = {City},
>>         volume       = {16},
>>         booktitle    = {On the road},
>>         booksubtitle = {Books and essays written while traveling under
>>      cover},
>>      }
>>
>>      \stopbuffer
>>        \loadbtxdefinitionfile[apa]
>>        \usebtxdefinitions    [apa]
>>        \usebtxdataset        [TestBib.buffer]
>>        \definebtxrendering   [Pubs][apa]
>>
>>      \starttext
>>
>>      \nocite[*]
>>
>>      \placelistofpublications[Pubs]
>>
>>      \stoptext
>>
>> How can I get “An Author” treated like “Author, An” as in the OTHER
>> examples? The result should like like that of “Somebody Else”. Bibtex
>> databases have both forms and it would be nice if the work was done
>> by ConTeXt automatically.
> Context, like bibtex, interprets "An Author" as "First Last", "Author,
> An" being the explicit form, useful when the last name contains several
> components.
>
> The APA style, that you use, abbreviates the first names. Thus, "An
> Author" gets rendered correctly as Author, A. and "Somebody Else" as
> Else, S.
Understood. The problem here is that  An Author  and  Author, An are 
treated as two different names, and so the name is repeated on the 
second bibliography reference. It would be nice if ConTeXt recognized 
that they are the same name and use a bibliography dash for the second 
occurrence.
>> The manual suggests that fields like director (see the FILM example)
>> can be induced to be treated as author/editor names by sufficiently
>> advanced users. Would such a user please share the method?
> producer= and director= are treated as names for @film{} in the APA
> specification.
But the output here simply puts it together as FunnyName, while it 
should be Name, F.
>> In the INBOOK example, can we get a BOOKSUBTITLE field to complement
>> the BOOKTITLE? My real bibliography has some very long titles, and I
>> would rather have only the main part appear with
>> \cite[booktitle][entry], yet have the title with subtitle in the
>> bibliography.
> We can easily add a booksubtitle field to the specification, to be
> handled like title/subtitle.
Thank you. That would be very nice.
>> Also in the INBOOK example, I notice that the spacing after “Vol.” is
>> a sentence space, and it should not be. The spacing after
>> abbreviations in the bibliography should not depend on setting
>> frenchspacing.
> The abbreviation is followed by a space. You suggest that they should
> be treated specially, not like the end of a sentence. This does not
> only pertain to bibliographies. How is this generally done in
> TeX/Context for any abbreviations anywhere? (I wouldn't know... ;-)
When I have direct control of the abbreviation, I can manage the space. 
But in this case the bibliography subsystem generates the abbreviation, 
so I do not have that ability.
>
> Alan

-- 
Rik

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2017-02-22  0:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 23:46 Rik Kabel
2017-02-22  0:09 ` Alan Braslau
2017-02-22  0:38   ` Rik Kabel [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=a22b8da9-13d6-d12e-bb7e-f50385943100@rik.users.panix.com \
    --to=context@rik.users.panix.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).