# Tag Info

5

I would just separate the heading from the bibliography and put your page style commands in between: \documentclass{memoir} \usepackage[style=ieee, citestyle=numeric-comp, backrefstyle=none]{biblatex} \addbibresource{biblatex-examples.bib} \begin{document} \tableofcontents \nocite{*} \printbibheading[heading=bibintoc] \thispagestyle{empty} \pagestyle{empty} ...

5

As shown in Schrödinger's cat's answer, \iffieldequalstr{<field>}{<string>} really expects a string in the second argument and not a macro that expands to a string. For your definition of \authorhash one could define a new \iffieldequalsdefstring{<field>}{<macro>}, that expands the macro once to obtain a string (usually I prefer to ...

5

I guess you need to expand the macro before you compare it. % -- bib file -------------------------------------------------------- \begin{filecontents}{\jobname.bib} @InProceedings{identifier1, Title = {Some Awesome Title}, Author = {Author, Some N. and Another Author}, Booktitle = {Some Book about ...

5

It is usually a bad idea to try and mix biblatex-apa with other styles or to modify it heavily: biblatex-apa is supposed to be used as style=apa, so that bibliography and citation style are both apa. It is quite a complex style that does a lot of work to implement the requirements of the APA manual which means that some choices in the code sacrifice ...

4

As discussed in https://tex.stackexchange.com/a/301571/134144 and Keep lowercase in biblatex the correct solution to stop biblatex's French language module from typesetting family names in small caps is to add \DefineBibliographyExtras{french}{\restorecommand\mkbibnamefamily} in the preamble after biblatex was loaded. As it turned out in the comments the ...

4

This is an expandability issue paired with the fact that string manipulation is hard in TeX. Essentially biblatex's \mkcomprange{<text>} only works as advertised if its argument <text> is a literal string. If the argument is too complex to be parsed correctly by \mkcomprange, \mkcomprange will simply do nothing. Not even \newcommand\foo{23-24;...

4

One super easy and non-hacky way to get close to what you want is to alter the definition of \DeclareLabeldate to prefer origdate over date: This only requires adding this to your preamble: \DeclareLabeldate{% \field{origdate} \field{date} \field{year} \field{eventdate} \field{urldate} \literal{nodate} } MWE \documentclass{article} \begin{...

4

It is basically the same as here Document with custom bibliography driver compiling with babel 3.33 and biblatex 3.13a ; but not compiling with most recent package versions. Only that it is not only the hyphen but also the apostroph. Either disable all shorthands: \usepackage[slovak,shorthands=off]{babel} or patch the two offending chars away: \...

4

It is probably simplest to fill the sortname field with the name stripped of all diacritics. \documentclass{report} \usepackage[english]{babel} \usepackage[backend=biber, style=authoryear, giveninits=true, maxbibnames=10, date=year, isbn=false, doi=false, url=false ]{biblatex} \makeatletter \def\ifskipbib{\iftoggle{blx@skipbib}} \makeatother \def\...

3

biblatex-apa applies sentence casing with \MakeSentenceCase*. That macro is quite complex and can basically only handle plain text without breaking. If you have complex macros in your titles you need to hide/protect them with a pair of braces. The complex rules of brace protection mean that you need two pairs of braces if the content in the braces starts ...

3

This might be regarded as a fault with the standard bibliography environment in biblatex. In an article class what you are asking is no really appropriate as the bibliography is not designed to start on a separate page. But your problem persists in book and memoir, and the solution below works in all cases. Namely, I patch (updated: better than previous ...

3

This is structurally the same issue as discussed in Document with custom bibliography driver compiling with babel 3.33 and biblatex 3.13a ; but not compiling with most recent package versions. But for Slovak we don't only need to think about the dash (-) but also about the apostrophe ('). \documentclass[12pt,a4paper,twoside,openright]{book} \usepackage[T1]{...

3

If you like you can tell biblatex to print the contents of the keywords field. The contents of the field are not hidden from biblatex, they can be printed. But the field has a special format – it is not a normal list, which is separated with and, but a list comma-separated values, for which biblatex has no built-in \print... function. So we need to do some ...

2

Citation commands defined with biblatex's \DeclareCiteCommand always have the same argument structure \<commandname>[<prenote>][<postnote>]{<keys>} The argument structure is pretty much hard-coded into \DeclareCiteCommand and can not be changed. Of course you don't have to use <prenote> and <postnote> as pre- and post-...

2

This is intentional. citepages=omit tests if the postnote is a page range and only suppresses the pages field in that case. The idea being that in other cases it can not be guaranteed that the postnote contains page references that supersede the info in the pages field. Following discussions in 2 exact page numbers in footnotes biblatex-sbl and https://...

2

From biblatex 3.13 (2019-08-17) onwards, you can use the macro \pnfmt instead of \pno and \ppno. See https://github.com/plk/biblatex/issues/870. \pnfmt formats its argument exactly like biblatex formats the complete postnote argument. So if \pnfmt contains only a page range and the postnote format adds a page prefix, you will get a page prefix from \pnfmt. ...

2

The apabackref option was removed from biblatex-apa in version 9.1 (2019-11-27) and v8.2 (2019-12-01) of biblatex-apa6 because the coexistence of the standard backref option and a style-specific apabackref option was just confusing. See https://github.com/plk/biblatex-apa/issues/72 and https://github.com/plk/biblatex-apa/pull/84. Just use the normal backref ...

2

Use backref=true. The apabackref option has been remove some time ago from biblatex-apa. See https://github.com/plk/biblatex-apa/issues/72.

2

A bare punctuation/spacing command such as \newunit in a bibmacro throws off biblatex's punctuation tracker. Punctuation and spacing commands should always be wrapped in \setunit/\printunit if they appear in bibmacros or drivers; they can only appear without those wrappers in field formats. Instead of \renewbibmacro{in:}{\newline} you need something like ...

2

2

You can do this using the \notecite or \pnotecite citation commands. See p. 112 of the documentation. I'm not sure whether this is proper APA style, however. I would probably prefer \citeyear instead to make the reference clearer without having to repeat the author. \documentclass{article} \usepackage[style=apa]{biblatex} \addbibresource{biblatex-examples....

2

I think your approach is very sensible, but I would change three things Use a verbatim field (verba) and not a literal field (userd) for the URL path. This becomes relevant if the URL contains dangerous characters like # or %. Literal fields can not deal with those characters unless they are escaped. You can make the RegEx slightly shorter by simply ...

2

biblatex-abnt uses a very roundabout way to redefine the name formats. Family names are ultimately typeset with \UpperOrSC in the bibliography and \UpperOrSCCite in citations, so the quickest way is to redefine those macros. \documentclass{article} \usepackage[utf8]{inputenc} \usepackage[brazil]{babel} \usepackage{csquotes} \usepackage[style=abnt, ...

2

The full error message one gets in the .log file when trying to cite the entry from the question is a tiny bit more helpful than the digest from your editor (abstract-prob.bbl) Runaway argument? {Past, current and projected future population growth is outlined. Ba\ETC. ! File ended while scanning use of \field. <inserted text> \par ...

2

BibTeX and Biber can deal with name prefixes like "de", "van", "von" etc. better if you drop the braces and give the name as author = {Frank de León and George Orwell}, or author = {von Brandt, Ahasver}, See also How should I type author names in a bib file?. If you write Frank {de León} then BibTeX and Biber parse the name as as being made up of given ...

2

If your bibliography items are very short, an icon placed below the label number may clash with the label number of the next item. So I suggest to place the icon to the left of the label, together with the code from Audrey's answer to Creating bibliographies with biblatex and moderncv for better moderncv compatibility of the bibliography environment there is ...

2

Here's a pragmatic solution. First, define the following, initially quaint-looking, macro: \newcommand\noopsort[1]{} Second, change the author field from author = {Esra {\c{C}}ak{\i}r and E. Allen Foegeding}, to author = {Esra \noopsort{Cakir}{\c{C}}ak{\i}r and E. Allen Foegeding}, Third, run a full recompile cycle: latex-biber-latex. ...

1

With most biblatex styles you can hook into the beginning of the entry by redefining the bibmacro begentry. Then it's just a matter of checking the entry type and printing a suitable string. The original definition of begentry can be found in apa.bbx (ll. 673-674). \documentclass{article} \usepackage[style=apa]{biblatex} \NewBibliographyString{dataset} \...

1

tl;dr It has to do with sorting and directing attention to the relevant bits of information. With your settings (specifically style=authoryear,) the bibliography list is sorted by author names, year and title. This means the most relevant bit that determines the sort order is the author name. Western names are usually sorted by family (last) name and then ...

1

You are looking for a -comp version of the style you are currently using. -comp styles compress multiple citation labels by the same authors to avoid duplication of names. Luckily both the standard styles and biblatex-ext offer a -comp version of the author-year style. Replace style=ext-authoryear, with style=ext-authoryear-comp, For example \...

Only top voted, non community-wiki answers of a minimum length are eligible