[NTG-context] Formatting bibliographic inline references and publications list

Jörg Weger joerg.weger at web.de
Sun Jan 25 20:10:13 CET 2015

Thank You Alan and Hans for your efforts regarding my questions so far.

After I had played a while with the examples Hans had attached, I have 
had a little success bei renaming copies of 
~/context/tex/texmf-context/tex/context/base/publ-imp-apa.lua and 
~/context/tex/texmf-context/tex/context/base/publ-imp-apa.mkiv to 
publ-imp-daf.lua and publ-imp-daf.mkiv (DaF stands for “Deutsch als 
Fremdsprache” = “German as a foreign language”, my subject of study) and 
putting those renamed copies into the same folder as a test file that 
should contain only in-text references and a publications list.

I have started to set up a “real world” BibTeXt example from the 
examples in the style sheet we were given by the university. So far I 
have different examples for “book” and “incollection”.

  Inside the two new configuration files I replaced every occurrence of 
“apa” by “daf”. Then I edited publ-imp-daf.mkiv by trial and error. I 
managed to change punctuation/delimiters in the publications list, but 
did not fully succeed with the in-text reference. I understand now that 
it is not trivial to set up a style as there are many decisions to be 
taken. The problem I have regarding the publications list is that the 
order I need differs in some ways from apa which means I have to split 
some of the macros defined for apa. E.g. for “book” my order is

author(s), year, title, (optional: edition), adress, publisher, 
(optional: series, volume)

and for incollection

author(s), year, title, editor(s), booktitle, publisher’s city adress, 
publisher, (optional: series, volume), page(s)

I think I have yet to translate the other real world examples (mainly 
electronic media) into BibTeX before I start to ask further questions 
regarding the order in the publications list.

For now I have an important question regarding in-text references:

Is there a way to switch between the following citation modes?

I have to manage:

* normal reference in brackets: author <space> year, no comma: e.g. 
“(Einstein 1904)”

* author is named in the text, only year in brackets: e.g. “As it has 
been proven by Einstein (1904) …”

* if page numbers are to be given in the citation: colon after year, 
followed directly (without space) by page number(s)/range: e.g. 
“(Einstein 1904:351)” or “(Einstein 1904:251 f.)” or “(Einstein 1904:251 
ff.)” or “(Einstein 1904:226–231)”.

(“f.” and “ff.” are the German abreviations for “et seq.” respectively 
“et seqq.”)

Is it possible to switch between those three modes? If not it would be 
great to implement that.

“\cite[extras={<page_numbers>}][<key>]” doesn’t seem to work anymore, so 
I cannot put page numbers manually.

Greetings from Munich


PS: Regarding the small caps from my original question: Those would be 
nice, but they are not obligatory—it is just my idea to let the 
references stick out more from the surrounding text and giving the whole 
thing more the impression of sophisticated typesetting :)

For me it is much more important to get the information in the 
publications list into the right order first.

On 23.01.2015 07:26, Alan BRASLAU wrote:
>  From what I can see, the only *significant* style difference that you
> seek is the use of \letterspace and \sc for names (authors or editors).
> The use of old numbers is trivial as they will be used if specified for
> the rest of the document.
> How else does your university's standard differ from the APA?
> All of the details of the layout are programmable using setups.
> By the way, the APA sort order is: authors(or editors), year,
> title (and possibly journal, volume, number, page).
> Alan
> On Mon, 19 Jan 2015 19:44:56 +0100
> Hans Hagen <pragma at wxs.nl> wrote:
>> On 1/17/2015 7:23 AM, Jörg Weger wrote:
>>> Hi Alan
>>> What I am trying to achieve is the following (of which typesetting
>>> the author’s name is only a detail): setting up an environment that
>>> I can use for all papers and works that I have to write during my
>>> academic studies. With the basic layout I am almost done. The main
>>> remaining problem is to get the bibliographic information details
>>> in the publications list into the right order for every possible
>>> type of publication according to the standards demanded by my
>>> university department which differ from APA style.
>>> You ask what I am looking for:
>>> It would be great to be able at the same time to format every
>>> detail of information while defining said order.
>>> Defining that order could be done by giving a kind of “maximum case”
>>> with the exact order of the desired variables and the punctuation
>>> and blanks between them for every particular type of publication
>>> cited. Out of that “maximum case” the underlying mechanism would
>>> ignore everything not needed in the particular case of a certain
>>> publication.
>>> In the case of publication type “book” it could be something like:
>>> \setpublicationstyleforlist [type:book]
>>> [{invertedauthor1}{/}{invertedauthor2}{/}{invertedauthor3}{et al.}{
>>> (}{year}{): }{title}{. }{address}{: }{publisher}{.}]
>> ... that not good enough: fields can be absent, there is no way to
>> distinguish authors from titles and so ...
>> the new mechanism we're making tries to cover a lot of aspects and
>> it's not that trivial to also keep the interface simple then
>> anyway, what we're talking of (currently) is:
>> - datasets, where data comes from bib files, lua tables xml files or
>> whatever gets interfaced
>> - optional typing, which means that one can tell what fields
>> represents what kind of data
>> - fallback sets i.e a sequence that will be checked when a field is
>> requested
>> - virtual fields (think of numbers and author year combinations)
>> - control via settings (the et-al thing as well as fences and
>> punctuation)
>> - rendering driven by setups so that users have full control (if they
>> want) over what comes out
>> - a bunch of helper macros (checking, spacing etc)
>> - a collection of methods that can be applied to fields when they are
>> called up
>> - calling up citations by tag but also by a query
>> - control over lists
>> - automatic generation of registers
>> - passing along extra data entered in the source
>> - and more
>> we don't know how many users will define renderings themselves but in
>> principle it should not be too hard to copy existing setups and mess
>> with them
>> there is quite some tracing available because it can go wrong in many
>> places (depending on the quality of the data)
>> attached are two simple examples of how users can define things
>> Hans
>> -----------------------------------------------------------------
>>                                             Hans Hagen | PRAGMA ADE
>>                 Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>>       tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
>>                                                | www.pragma-pod.nl
>> -----------------------------------------------------------------

More information about the ntg-context mailing list