Changes

These three suf­fixes are un­der­stood by the loader. Here the dataset has the name <tt>standard</tt> and the three data­base files are merged, where later en­tries hav­ing the same tag over­load pre­vi­ous ones. De­f­i­n­i­tions in the doc­u­ment source (coded in TEX speak) are also added, and they are saved for suc­ces­sive runs. This means that if you load and de­fine en­tries, they will be known at a next run be­fore­hand, so that ref­er­ences to them are in­de­pen­dent of when load­ing and de­f­i­n­i­tions take place.

<div stile="" >

</div>

<div stile="" >

</div>

<div stile="" >

</div>

<br/>

In this doc­u­ment we use some ex­am­ple data­bases, so let’s load one of them now:

<pre detail='buffer'>\definebtxdataset[example]

</pre>

<br/>

You can ask for an overview of en­tries in a dataset with:

<pre detail='buffer'>\showbtxdatasetfields[example]

</pre>

{|

The ren­der­ing it­self is some­what com­plex to set up be­cause we have not only many dif­fer­ent stan­dards but also many fields that can be set up. This means that there are sev­eral com­mands in­volved. Of­ten there is a pre­scribed style to ren­der bib­li­o­graphic de­scrip­tions, for ex­am­ple <tt>apa</tt>. A ren­der­ing is setup and de­fined with:

<div stile="" >

</div>

<div stile="" >

</div>

<br/>

And a list of such de­scrip­tions is gen­er­ated with:

<div stile="" >

</div>

<br/>

A dataset can have all kind of en­tries:

Each has its own ren­der­ing vari­ant. To keep things sim­ple we have their set­tings sep­a­rated. How­ever, these set­tings are shared for all ren­der­ing al­ter­na­tives. In prac­tice this is sel­dom a prob­lem in a pub­li­ca­tion as only one ren­der­ing al­ter­na­tive will be ac­tive. If this be not suf­fi­cient, you can al­ways group lo­cal set­tings in a setup and hook that into the spe­cific ren­der­ing.

<div stile="" >

</div>

<div stile="" >

</div>

<br/>

Ex­am­ples of list vari­ants are:

The first ar­gu­ment is op­tional.

<div stile="" >

</div>

<br/>

You can tune the way a ci­ta­tion shows up:

Be­cause we are deal­ing with data­base in­put and be­cause we gen­er­ally need to ma­nip­u­late en­tries, much of the work is del­e­gated to Lua. This makes it eas­ier to main­tain and ex­tend the code. Of course TEX still does the ren­der­ing. The ty­po­graphic de­tails are con­trolled by pa­ra­me­ters but not all are used in all vari­ants. As with most ConTEXt com­mands, it starts out with a gen­eral setup com­mand:

<div stile="" >

</div>

<br/>

On top of that we can de­fine in­stances that in­herit ei­ther from a given par­ent or from the top­most setup.

<div stile="" >

</div>

<br/>

But, spe­cific vari­ants can have them over­loaded:

This com­mand has two syn­onyms: <tt>\nocite</tt> and <tt>\nocitation</tt> so you can choose what­ever fits you best.

<div stile="" >

</div>