Error: Unicode char

[andreifoldes]

• I have verified in the Zotero addons screen that I am on the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero
• I am posting a single question, bug or feature request
• I have included a descriptive subject of the problem
• I am available for follow-up questions and testing

Non-export problems with BBT

Report id: N54AF8U9

When I try to cite this article: https://www.ncbi.nlm.nih.gov/pubmed/28069918
I get the following error msg when knitting an RMakrkdown document:

! Package inputenc Error: Unicode char α (U+3B1)
(inputenc) not set up for use with LaTeX.

pdflatex --version
pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)

[retorquere]

Two questions:

1. Did you export with Better BibTeX, or with Better BibLaTeX?
2. There are two options in the preferences to "Export unicode as plain-text", one for bibtex, one for biblatex, what are these set to?

[andreifoldes]

Hello, 1) I believe BibLaTex (I am using this addon https://github.com/crsh/citr and have not set options(citr.use_betterbiblatex = FALSE)) 2) For Bibtex it is set to "Export unicode as plain-text" for BibLatex it is not set.

…

On Fri, Apr 13, 2018 at 12:38 PM, Emiliano Heyns ***@***.***> wrote: Two questions: 1. Did you export with Better BibTeX, or with Better BibLaTeX? 2. There are two options in the preferences to "Export unicode as plain-text", one for bibtex, one for biblatex, what are these set to? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#950 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHHM2b45npQA0wX2GQRMXL5ADixfUnUrks5toIA9gaJpZM4TTOO4> .

[retorquere]

Better BibLaTeX exports as unicode by default, so you will either have to use better bibtex, or enable the "export as plain text" option for better biblatex.

[retorquere]

xref to crsh/citr#30 (comment)

[retorquere]

closing for lack of feedback.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.