TransWikia.com

inputenc Error: Unicode char u8: not set up for use with LaTeX

TeX - LaTeX Asked on October 3, 2021

This is with ref to my previous question Package clash in multilingual report.

documentclass[11pt,table,a4paper]{article}
usepackage{lmodern}
usepackage[utf8]{inputenc}
usepackage[T1]{fontenc}

usepackage{CJKutf8}
usepackage[english,russian]{babel}

newenvironment{SChinese}{%
 CJKfamily{gbsn}%
 CJKtilde
 CJKnospace}{}

 begin{document}
 selectlanguage{russian}
  Это мой первый многоязычный докладе.
  Инфантильный гипертрофический стеноз привратника - это серьёзное 
 selectlanguage{english}
  This is my first multilingual report.

 begin{CJK}{UTF8}{}
  begin{SChinese}
    这是我的第一个多语种的报告。
  end{SChinese}
  end{CJK}

  end{document}

when I try to compile it, I get following error message.

LaTeX Warning: Unused global option(s):
    [table].

(./data.aux
(/usr/local/texlive/2011/texmf-dist/tex/latex/cyrillic/t2acmr.fd))
(/usr/local/texlive/2011/texmf-dist/tex/latex/lm/t1lmr.fd)

LaTeX Font Warning: Font shape `T2A/lmr/m/n' undefined (Font)         
using `T2A/cmr/m/n' instead on input line 15.


! Package inputenc Error: Unicode char u8:  not set up for use with
LaTeX.

See the inputenc package documentation for explanation. Type  H
<return>  for immediate help.  ...                                    

l.18 ...�ный гипертрофический стеноз привра...

How can I avoid such error message.

13 Answers

The error you get is due to a "no-break space" character, according to what I can gather by copying an pasting your message.

This character is not usually set up by the [utf8] option and it's invisible to many editors, so it can slip in a document without the typist knowing it.

Solution: add in your preamble

DeclareUnicodeCharacter{00A0}{ }

if you don't mean to type a no-break space, or

DeclareUnicodeCharacter{00A0}{~}

if you want that the character stands for what its name says.

UPDATE

Recent (after 2015-01-01) versions of the UTF8 configuration file for inputenc do define U+00A0 as nobreakspace, so this should be of no concern, now.

Correct answer by egreg on October 3, 2021

usepackage[utf8x]{inputenc}

Ubuntu:

You must install texlive-latex-extra before use it.

Fedora:

You must install texlive-collection-latexextra before use it.

Answered by Evgenii on October 3, 2021

As this is one of the top google hits for this error message, here's a more general answer with an example:

The cause is a unicode character in one of your input files that isn't mapped to an output. This may -- especially if you're using the (unicode-supporting) biblatex/biber system -- be in your bibliography. This is a good place to look for errors as .bib files downloaded from publishers website are often malformed. You can tell if the error comes from the bib file - the line number in the error message will be that of your end{document}, which makes tracking down the actual error rather tricky (inspecting various aux files doesn't appear to help).

Some of these errors are subtle, like the non-breaking space in the question, or the hyphen (U+2010) character given to me by one journal, which looks identical to the hyphen-minus produced by the keyboard.

Copying the character after the hyphen and searching for it should help - unless your command window or editor "helps" by converting it to the more common equivalent or replacing unicode with blanks - in that case copy it from your .log and search all the input files.

(I'm happy to expand this in response to comments or watch it grow -- it's just an attempt to be helpful to searchers)

Answered by Chris H on October 3, 2021

You may get this error also if you use different language for bibtex. In that case project.bbl may contain characters in different encoding (e.g latin2).

What you need to do is swap encoding when rendering bibliography to latin2 and switch back to utf8 after.

inputencoding{latin2}
bibliography{mybib}
inputencoding{utf8}

Hope this helps.

Answered by zub0r on October 3, 2021

This happened to me when I did save my .tex file with utf8 but forgot to save also the .bib file with the same encoding (it was still in ANSI).

Instead of returning back to ANSI on my .tex file I just opened the .bib file with Notepad++ and chose to convert to utf8.

Then after compiling everything was working OK.

Answered by David on October 3, 2021

If this happens in the bibliography, try specifying the language explicitly to bibtextu:

bibtextu -l ru my_paper_with_russian_bibliography

This fixed it for me.

Answered by Igor on October 3, 2021

I had this Error because I accidentally saved an included .tex file as ANSI while the master file was in UTF-8.

You can change file encoding in Notepad++ for example. But you will need to copy it from the the ANSI version and paste it into the UTF-8 version.

Answered by Tobi G. on October 3, 2021

I have found the same problem but none of the above answers solved it. In the end, I found the code '{i} in my .bib file. This was supposed to yield í but was producing a crazy unicode char that broke compilation. This .bib file was exported from CiteULike based on a reference that I entered mannually or copy-&-pasted from somewhere else. I suppose something wrong happened while converting a mannually entered/pasted í to '{i}.

Answered by M.B. on October 3, 2021

I had two similar problems:

  1. "Unicode char u8: "
  2. "Unicode char u8:." (with dot)

The problems were related to the .bib file (references list).

The first problem was solved based on the DeclareUnicodeCharacter{00A0}{ } stated by @egreg.

The second one was helped by the @Chris H 's answer. I opened the generated file .log and looked for errors. I found:

! Package inputenc Error: Unicode char u8:C3. not set up for use with LaTeX.

Then, I looked the "C3" string in the generated file .bbl and I found out that the letter "Ó" (the first letter of an author's name, Óscar Oballe-Peinado) was the problem. So, I changed it in the bibliography file for {'{O}} and voilà!

Despite I'm using "usepackage[utf8]{inputenc}", it seems not working specifically with the accented first letter of the first name of authors.

Answered by Fernando on October 3, 2021

Inserting

% !TEX encoding = UTF-8 Unicode

at the beginning of the file solved this issue for me.

Answered by user27221 on October 3, 2021

XeTeX is more suitable than most other TeX engines for unicode : replace the lines

usepackage[T1]{fontenc}
usepackage[utf8]{inputenc}

with

usepackage{fontspec}

and compile with xelatex myfile.tex.

Answered by Skippy le Grand Gourou on October 3, 2021

My error was related, but slightly different:

! Package inputenc Error: Unicode character ╩│ (U+02B3)

or

! Package inputenc Error: Unicode character ᵉ (U+1D49)  
(inputenc)                not set up for use with LaTeX.

I had these errors because of a bibliographic entries generated in French babel which typesets the edition field, e.g. 1ʳᵉ éd. or 3ᵉ éd. using a raised re or e, resulting in U+02B3 and U+1D49 which apparently are not valid, even though (so far) all the other accented characters, e.g., é in édition are valid...

Because of my complex pandoc settings from Markdown with Libertine font, I don't want to swap to another *Tex engine...

So, my band-aid fix was to use the math mode to raise these letters:

DeclareUnicodeCharacter{1D49}{$^text{e}$}
DeclareUnicodeCharacter{02B3}{$^text{r}$}

Also, if you're using pandoc, put them in your header-includes: part of the front matter.

Answered by Fuhrmanator on October 3, 2021

An anwser for a slightly different case:

! Package inputenc Error: Unicode character ° (U+B0)
(inputenc)                not set up for use with LaTeX.

Here, the answer is very simple:

usepackage{textcomp}

This packages defines the textdegree macro and also sets up ° to use it.

Answered by Vincent Fourmond on October 3, 2021

Add your own answers!

Ask a Question

Get help from others!

© 2024 TransWikia.com. All rights reserved. Sites we Love: PCI Database, UKBizDB, Menu Kuliner, Sharing RPP