1

I have some problem with the "Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc)". I am using Zotero and "export" the bibliography to a bib file. To correct certain information I recently used jabref. I don't know if this could have any influence. The preamble of the document:

\documentclass {report}

\usepackage[utf8]{inputenc}

\DeclareUnicodeCharacter{B0}{\textdegree}

\usepackage[T1]{fontenc}

\usepackage{textcomp}

\usepackage{amsmath}

\usepackage{amssymb}

\usepackage{longtable}

\usepackage{rotating}

\usepackage{todonotes}

\usepackage{enumerate} 

\usepackage[hyphenbreaks]{breakurl} 

\usepackage[backend=biber, citestyle=authoryear,sorting=nyt,natbib=true,ibidtracker=true]{biblatex}
\addbibresource{test.bib}

Please let me know if there is any important information missing (it is my first question here). I would be very grateful for any help on this issue.

closed as unclear what you're asking by moewe, Stefan Pinnow, CarLaTeX, Zarko, egreg Jul 30 '17 at 7:26

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 3
    U+2121 is TELEPHONE SIGN (℡) is that really in your bibliography? – David Carlisle Jul 20 '17 at 20:49
  • 3
    If it is you can add \DeclareUnicodeCharacter{2121}{\textsc{Tel}} to your preamble. – David Carlisle Jul 20 '17 at 21:07
  • 4
    U+2121 TELEPHONE SIGN (℡) in UTF-8 is three bytes E2 84 A1, so that's in your file. What you've pasted in the question are three characters â then then ¡. So at least your terminal that displayed the output(?) must be using an encoding in which 84 denotes and according to this table that's WINDOWS-1252. Whatever it is, there's some mismatch between the encoding specified (utf8) and the one actually used. You need to post your test.bib to help answer the question. – ShreevatsaR Jul 20 '17 at 21:07
  • @ShreevatsaR Well, you don't expect a match between input and output encoding, anyway. And the terminal's encoding in a third thing altogether. I agree there is probably an encoding mix-up here, but that reason seems a questionable one. – cfr Jul 21 '17 at 0:19
  • Does your .bib file contain any accents as macros e.g. \'e or whatever? If so, try replacing them with their unicode equivalents e.g. é and make sure that your .bib uses UTF8 encoding, as well as your .tex file. Biber/Biblatex does not cope gracefully with traditional LaTeX ways of doing accents and often generates strange warnings about unknown unicode character in response. Feeding it actual unicode characters makes it happy. – cfr Jul 21 '17 at 0:24