Repository files navigation

This package provides advanced bibliographic facilities for use with LaTeX.

The package is a complete reimplementation of the bibliographic facilitiesprovided by LaTeX. A custom backend Biber is used by default whichprocesses BibTeX format data files and then performs all sorting, labelgeneration (and a great deal more).

Biblatex does not use the backend toformat the bibliography information as with traditional BibTeX: instead ofbeing implemented in BibTeX style files, the formatting of the bibliographyis entirely controlled by TeX macros.

This package supports subdividedbibliographies, multiple bibliographies within one document with differentsorting, separate lists of bibliographic information such as abbreviationsof various fields.Bibliographies may be subdivided into parts and / orsegmented by topics.

Just like the bibliography styles, all citationcommands may be freely defined.

With Biber as the backend, features suchas customisable sorting, multiple bibliographies with different sorting,customisable labels, dynamic data modification and custom data models areavailable.

The package is completely localised and can interface withthe Babel and Polyglossia packages. Read below for how toupdate and/or add translations.

• Philipp Lehman
• Philip Kime, Joseph Wright, Audrey Boruvka (since 2011)

• Copyright 2006 --- 2011 Philipp Lehman
• Copyright 2011 --- ... Philip Kime

This work may be distributed and/or modified under the conditions of the LaTeX Project Public License, either version 1.3 of this license or (at your option) any later version.

The latest version of the license is inhttps://www.latex-project.org/lppl.txt and version 1.3 or later is part of all distributions of LaTeX version 2003/06/01 or later.

This work has the LPPL maintenance status "maintained".

biblatex is bundled with TeXLive and its variants as well as MikTeX.Normally you can install and update biblatex through your TeX distribution.

biblatex starts life on Github where you can always find developmentreleases:

https://github.com/plk/biblatex

From here, it is packaged for general consumption to SourceForge:

https://sourceforge.net/projects/biblatex

this is where users can download the current development version.

The latest official release is then put onto CTAN, which is where users canget the latest stable version:

https://ctan.org/pkg/biblatex

For this you'll need to be on a UNIX-like system (usehttps://www.cygwin.com on Windows) that has bash and perl.

You should only install from github if you want to check out the bleeding edgeof development or if there is absolutely no way to obtain either the officialhistorical releases fromSourceForgeor the current release fromCTAN.Remember that you will need a matching Biber version (the binaries aredistributed onSourceForge).

First clone the repo:

git clone https://github.com/plk/biblatex.git

Then from the clone root:

obuild/build.sh install <version> <texmf root>

for example, say the currently released version is 3.3 and you want to trythe 3.4 development version. Suppose your personal texmf root is at~/texmf:

obuild/build.sh install 3.4 ~/texmf

If this is the first time you are installingbiblatex into~/texmf, you will haveto tell TeX that it can find the files in this new location withtexhashor the equivalent command from your TeX distribution.

Note that the install script does not fetch and install the official biblatexrelease version corresponding to the version argument supplied. It just takesthe files that are currently checked out, moves them and changes their versionidentifications so that they identify as the version given in the argument.If you want a specific version, you must check out the corresponding tag orobtain the corresponding sources otherwise before running the script.

Obviously, its is easier to get the TDS format package from the Sourceforgedevelopment folder and just unpack it into your~/texmf but this mightnot be quite as recent as the git development branch (but is usually veryclose).

The language files (*.lbx) are located intex/latex/biblatex/lbx. To adda new translation copyenglish.lbx (or another existing translation that iscloser to your language; note thatenglish.lbx andgerman.lbx arereference translations, all other files are not guaranteed to be complete)tolanguagename.lbx, wherelanguagename is the name used by Babelfor the language.

To debug or verify that a translation is complete, copydoc/latex/biblatex/examples/03-localization-keys.tex totex/latex/biblatex/lbx. Edit03-localization-keys.tex so Babel (and henceBiblatex) uses the language you are translating. Compiling the file willwarn you about missing strings, and looking at the generated file willhelp you to proofread your translation.

If you are translating for an upcoming release, i.e., you have cloned theGit repository, please remember to build and install the package as describedabove before trying to compile03-localization-keys.tex.

If your language inherits from another, you'll have to take extra care asnew strings aren't reported if they are already translated in the inheritedlanguage.

• biblatex comes with example files in thedoc/latex/biblatex/examplesdirectory in the distribution. There are a lot of practical examples herealong with comments in the source.tex files which help to explaindetails not dwelt on in the PDF manual.
• StackExchange

Suggestions and bug reports are welcome.

• Go to the Githubissues page.
• Open an issue.
• Add aminimal working example ifpossible. This helps a great deal facilitate a swift response.