Changes

<p></p>

These three suffixes are understood by the loader. Here the dataset has the name <tt style="color:rgb(0,102,102);font-size:100%;" >standard</tt> and the three database files are merged, where later entries having the same tag overload previous ones. Definitions in the document source (coded in <span tag="MKIV" style="font-style:sans;">TEX</span> speak) are also added, and they are saved for successive runs. This means that if you load and define entries, they will be known at a next run beforehand, so that references to them are independent of when loading and definitions take place.

<span style="font-style:oblique;" > setup definition setupbtxdataset </span >

</div>

<span style="font-style:oblique;" > setup definition definebtxdataset </span >

</div>

<span style="font-style:oblique;" > setup definition usebtxdataset </span >

</div>

<p></p>

The rendering itself is somewhat complex to set up because we have not only many different standards but also many fields that can be set up. This means that there are several commands involved. Often there is a prescribed style to render bibliographic descriptions, for example <tt style="color:rgb(0,102,102);font-size:100%;" >apa</tt>. A rendering is setup and defined with:

<span style="font-style:oblique;" > setup definition setupbtxrendering </span >

</div>

<span style="font-style:oblique;" > setup definition definebtxrendering </span >

</div>

<p></p>

And a list of such descriptions is generated with:

<span style="font-style:oblique;" > setup definition placebtxrendering </span >

</div>

<p></p>

Each has its own rendering variant. To keep things simple we have their settings separated. However, these settings are shared for all rendering alternatives. In practice this is seldom a problem in a publication as only one rendering alternative will be active. If this be not sufficient, you can always group local settings in a setup and hook that into the specific rendering.

<span style="font-style:oblique;" > setup definition setupbtxlistvariant </span >

</div>

<span style="font-style:oblique;" > setup definition definebtxlistvariant </span >

</div>

<p></p>

The first argument is optional.

<span style="font-style:oblique;" > setup definition cite </span >

</div>

<p></p>

Because we are dealing with database input and because we generally need to manipulate entries, much of the work is delegated to <span tag="MKIV" style="font-style:sans;">Lua</span>. This makes it easier to maintain and extend the code. Of course <span tag="MKIV" style="font-style:sans;">TEX</span> still does the rendering. The typographic details are controlled by parameters but not all are used in all variants. As with most <span tag="MKIV" style="font-style:sans;">ConTEXt</span> commands, it starts out with a general setup command:

<span style="font-style:oblique;" > setup definition setupbtxcitevariant </span >

</div>

<p></p>

On top of that we can define instances that inherit either from a given parent or from the topmost setup.

<span style="font-style:oblique;" > setup definition definebtxcitevariant </span >

</div>

<p></p>

This command has two synonyms: <tt style="color:rgb(0,102,102);font-size:100%;" >\nocite</tt> and <tt style="color:rgb(0,102,102);font-size:100%;" >\nocitation</tt> so you can choose whatever fits you best.

<span style="font-style:oblique;" > setup definition nocite </span >

</div>