New answers tagged

0

The hplain.bst file is intended as a blank starting place for you to build your own linking around - i.e. it doesn't do the linking for you, as defined in the .bst: FUNCTION {format.eprint} { eprint empty$ { "" } { eprint } if$ } so the eprint formatting is essentially blank. The question of how to setup linking, has been answered ...


0

I had a strange problem that the {\&}, which I thought was properly escaped, only caused an issue if it was used in the author field with biblatex. For this field, remember to use two brackets ({{…}}) if you have a non-human name, such as an organization. Because BibLaTex/BibTex otherwise change the author name according to their citation format, and ...


0

BibTex Tidy is an open source online tool, I've used it, and personally I found it to be very reliable. It supports formatting and clean up, but also checks duplicate entries, including not just the key but also titles. The tool's self-description is: This tool tidies bibtex files by fixing inconsistent whitespace, removing duplicates, removing unwanted ...


0

The first BibTeX styles predate the standardisation of the URL protocol by a few years. This means that the base BibTeX styles do not have a dedicated url field. Newer styles may support a url field, but the exact implementation and handling of that field is not uniform across styles. With most styles that support a url field, however, the rule is to give ...


1

For biblatex you should not (LaTeX-)escape any US-ASCII chars in the url field. That means that % should remain % and should not be escaped as \%. With BibTeX the situation is not as uniform. The original standard BibTeX styles date back to the eighties before URLs were standardised and therefore don't have a dedicated url field. Later BibTeX styles have URL ...


0

Remove all the authors whom you want to replace with et al. Then add and others suffix to the author field. e.g. Code segment in .bib file @ARTICLE{hao, author={Hao, M. and Bai, Y. and Zeiske, S. and others}, journal={Nature Energy}, title={Ligand-assisted cation-exchange engineering for high-efficiency colloidal Cs1−xFAxPbI3 quantum dot solar cells with ...


1

Apparently the issue was a follow up cause from a fatal error. A picture I newly inserted while editing (file ./Images/Lifecycle_HA.jpeg) created a fatal error, according to the .log. The picture file must have been damaged and thus it mucked up everything else. Removing the picture fixed everything. I could still open the original picture on my PC but to be ...


2

Does it have to BibTeX? If not, with BibLaTeX it's pretty simple: You just put the article data inside your bib-file as is. Unless you compile with xelatex or lualatex, you need to make sure to load \usepackage[T2A]{fontenc}. Just have a go at it: \documentclass{article} \usepackage[T1,T2A]{fontenc} \usepackage[russian,english]{babel} \usepackage{csquotes} ...


3

Use cite$ write$ instead of key write$. From TameTheBeast, p. 33 cite$ puts on the stack the internal key of the current entry or btxhak, p. 6 cite$ Pushes the string that was the \cite-command argument for this entry. As far as I know the entry key of the bibliography entry is usually not available as a regular field in the BibTeX language, you need to ...


1

\documentclass{amsart} \usepackage[backref]{hyperref} \title{Title} \begin{document} \begin{abstract}\makeatletter\phantomsection\def\@currentlabel{(abstract)}\makeatother reference : \cite{doody} \end{abstract} \maketitle \bibliographystyle{abbrv} \bibliography{biblatex-examples} \end{document}


1

Probably you could use something like: \documentclass[letterpaper,11pt,oneside]{article} \usepackage[T1]{fontenc} \usepackage[utf8]{inputenc} \usepackage{setspace} \usepackage{booktabs} \usepackage{longtable} \usepackage{kotex} \usepackage{url} \usepackage{xcolor} \usepackage{xltabular} \newcommand{\MYhref}[3][blue]{\href{#2}{\color{#1}{#3}}} \usepackage{...


0

As discussed in the comments, this is extremely tricky with standard BibTeX, because the citation data is only available and usable if the entry in question is added to the bibliography. BibTeX has no built-in way to treat certain entries different from 'normal' citations. So you would have to bypass BibTeX and obtain the citation data via other means, but ...


1

I have two suggestions. Both start by making a copy of the file plainnat.bst and naming the copy, say, plainnat-nolab.bst. (Don't edit an original file of the TeX distribution directly.) Comment out the three instructions starting at line 1392 in plainnat-nolab.bst: EXECUTE {initialize.longest.label} ITERATE {forward.pass} REVERSE {reverse.pass} This ...


5

natbib does not really have the list of authors of your citation available in machine-readable form in citations. So a command that lets you typeset a particular author of your citation is a bit tricky to implement. So I suggest you just type the name manually. If you want to be able to link it, the following should help you \documentclass{article} \...


0

Theoretically the presentation of the citation label in the bibliography is up to the document class you use and can additionally be modified by bibliography-related packages. So it is not possible to say with absolute certainty what you should do. The following works for most standard setups. In the standard classes the citation label in the bibliography is ...


3

There are two aspects to asking whether a character is safe in entry keys. The character needs to be safe when it is read by BibTeX (or Biber) in the .bib file. The character needs to be safe when it is later processed by LaTeX. Examples of characters that are unsafe on the .bib side would be ,, =, { and }. Those characters have special meaning in the .bib ...


2

There's a mistake in your bib entry: The name of the field that contains the entry's URL address should be url, not address: @Manual{nmonchart, title = {nmonchart}, author = "Griffiths, Nigel", url = {http://nmon.sourceforge.net/pmwiki.php?n=Site.Nmonchart}, } Second, load the xurl package rather than the url package to allow ...


0

# FILENAME: abbrv_bib.py #!/usr/bin/env python3 from bibtexparser.bwriter import BibTexWriter import bibtexparser from pybtex.database import parse_file import argparse parser = argparse.ArgumentParser() parser.add_argument('input', help='input file name') parser.add_argument('output', help='output file name') parser.add_argument('--no-middle', action='...


3

Since you're using the natbib citation management, I suggest that you (a) load the package with the option authoryear and (b) employ the unsrtnat bibliography style. That said, I'd like to repeat the concern voiced in @leandriis' comment: Assuming your paper cites more than half a dozen pieces, how on earth are your readers supposed to find the ...


1

The alphabetic styles are utterly confused when accented letters are present at the beginning of the name. Do you really need this very old-fashioned method? It was used in the olden times of typewriters, when there was no real way to have a sensible numbering scheme in case of changes to the document during its preparation. Here's a workaround that however ...


0

I suppose you are using natbib like this: \usepackage[numbers]{natbib} If so, just try this: \renewcommand{\bibnumfmt}[1]{[1.#1]} \makeatletter \let\cite@orignal\cite \def\cite{\cite@original[1.\@gobble][]} \makeatother Explanation: \@gobble eats the space between 1. and X.


1

You are mixing two incompatible methods to generate citations and a bibliography in LaTeX. You have \bibliographystyle{plain} and \bibliography{ref.bib} in the document body, which are used to generate BibTeX-based bibliographies. (It doesn't matter on a current system, but technically \bibliography{ref.bib} is wrong. The file name argument to \bibliography ...


1

To fulfill your requirement number 8, you should actually load article with the size option 9pt, \documentclass[9pt]{article}. As we can see from the file size9.clo it then defined small as: \newcommand\small{% \@setfontsize\small\@viiipt\@ixpt% \abovedisplayskip 5\p@ \@plus2\p@ \@minus2\p@ \abovedisplayshortskip \z@ \@plus1\p@ \...


2

It looks like the column balancing has collected and examined the last line on the page using \lastbox, and in doing so it has lost the horizontal offset (lists use \parshape). What is the \flushend command? I guess it comes from the flushend package. Looking at the package documentation I see an obvious package option: keeplastbox It skips removing anything ...


2

Maybe you have a look at this minimal example \documentclass[12pt]{article} \usepackage[a4paper]{geometry} \usepackage{natbib} \usepackage{filecontents} \begin{filecontents}{\jobname.bib} @book{Gnus, author = {David A. Zoo}, title = {Gnats of the world}, publisher = {Epic}, Year = {2018}, } @book{Gnats, author = {David A. ...


0

After some searching I found a suitable answer. It is not exactly what I was hoping for in terms of a master list but I am happy with the results I have for now, so I am posting this answer for anyone that has the same problems. I made use of the standalone package along with the nomenclpackage. I added the following to my preamble: \usepackage{standalone} \...


0

Tool doi2bib has moto "give us a DOI and we will do our best to get you the BibTeX entry" and it works for DOI specified in given json.


2

In a current version of biblatex labelprefix=P must be given as argument of the refcontext. Note that refcontexts are not fully supported by BibTeX, but with biblatex 3.14 the following will work. \documentclass[a4paper, twoside, 12pt]{thesis} \usepackage[natbib=true, style=numeric-comp, backend=bibtex8, defernumbers, maxnames=99]{biblatex} \begin{...


-2

It is always better to use a reference manager such as jabref to generate and manage reference rather than manually inserting them.


0

This error fundamentally happens because your entry in *.bib contains data that are not being written to your *.bbl file by your *.bst file. The stack contents should appear in your *.blg file (starting on a new line after stack=), allowing you to see which items weren't written. It can be resolved by editing the bst file so it writes everything, or by ...


1

There are several problems in myplain.bst mostly in relation to the date and series field. Please report this as a bug to the maintainer/developer of your template. If there is no one maintaining the template you should seriously consider not using the template and/or protesting if you are required to use it. It is unreasonable to require people to use an ...


0

Under the wlscirep package bib items should contain at least the following entries: @article{..., title = {...}, author = {...}, journal = {...}, pages = {...}, year ={...}, publisher = {...} } If not all of the above entries are available, you can consider to switch to a @misc reference: @misc{..., title = {...}, author = {...}, howpublished = {...} }


Top 50 recent answers are included