"cambridge" style

"jdbillett" <[email protected]>
Newsgroups gmane.comp.tex.bibtex.jurabib.user
Message-ID <[email protected]>
I just recently discovered jurabib and only found this users' group
today.  I am most 
grateful for both.  I was especially pleased to see that Guido
Milanese is a regular 
contributor, since another Gregorian chant researcher obviously finds
the package 
useful (I am a great admirer of a recent piece of his on Carolingian
grammatical 
reform and its possible influence on chant notation).

To use jurabib to write my PhD dissertation, I am going to have to
learn to make 
some alterations to the oxford option, since I study at "the other
place" (Cambridge), 
and couldn't be caught using the citation style of the Auld Enemy!

There are seven things listed below that I need to learn how to do in
order to make 
this work.  I would appreciate any help that is offered.  Attempts to
work my way 
through the .sty and .bst files have thus far proven daunting!

Many thanks,

Jesse Billett
King's College
Cambridge, UK  CB2 1ST


1.  Suppress the publisher in citations and bibliography.

     e.g. [...] (London, 2004)

2.  In full citations and bibliography, Author/Editor first names
always abbreviated to 
initials.

     e.g. .bib file has AUTHOR = "Jesse Dean Billett"

     bibliography:

     Billett, J. D., `The Divine Office in Anglo-Saxon England' [...]

     first full citation:

     J. D. Billett, `The Divine Office in Anglo-Saxon England' [...]

     next cite (titleformat=all):

     Billett, `The Divine Office [...]

3.  Create some new entry types!

a) @manuscript % For medieval manuscripts

===> Needs fields for Address, Library, Shelfmark, and Comment. 
Citations would 
have to refer to folios or pages, depending on how the manuscript was
marked.

     e.g. London, British Library, MS Additional 56488 (s. xiii
breviary, Muchelney, 
Somerset)

b) @primarysource  % For editions of medieval texts

===> Needs fields for Author (if known), Title, Editor, EditionTitle,
and other things 
for @book or @inbook

     e.g. Bede, {\em Epistola ad Ecgberhtum}, ed. C. Plummer, {\em
Venerabilis Bedae 
Opera}, 2 vols. (Oxford, 1896), I, pp. 405--23

4. Other things to tinker with, like "(ed.)" and "(eds)", instead of
"editor/s" (I see this is 
already being addressed) and the order in which this is found.  In
the "cambridge" 
style, for @inbook or @incollection, the editor of the volume appears
after the 
booktitle:

     e.g. Barnard, L. W., `Bede and Eusebius as Church historians',
in {\em Famulus 
Christi}, ed. G. Bonner (London, 1976), pp. 106--24

but:

     Parsons, D. (ed.), {\em Tenth-Century Studies: Essays in Commemoration of the 
Millennium of the Council of Winchester and \textnormal{Regularis Concordia}} 
(London and Chichester, 1975)

5. I'm also wondering if a "volume in series" field might be created,
so that we might 
be able to show what number in a series is meant:

     e.g. {\em Two Anglo-Saxon Pontificals (the Egbert and Sidney
Sussex Pontificals)}, 
ed. H. M. J. Banting, Henry Bradshaw Society 104 (Woodbridge, 1989)

The reason for this being that some departments require a comma
before the series 
number, so it would need something like {/seriesnumbersep}{,\space},
yielding Henry 
Bradshaw Society, 104 [...].  The same applies to the separation
between journal titles 
and volumes, but I think there's already a variable for that.  I just
have to find it!

6. et al. to be italicized (should be a small thing?)

7. When the pages=always option is used, and a specific page is cited
as well, can the 
word "at" be included in the separation?

     e.g. Rudolf, {\em Vita S. Leobae}, ed. G. Waitz, {\em Vita
Leobae abbatissae 
Biscofesheimensis}, MGH Scriptores XVI (1887), pp. 118--31, at p. 119.



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/jurabib/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.