inputenc: Unicode character … not set up for use with LaTeX The Next CEO of Stack OverflowEntering Unicode characters in LaTeXHow to solve the `Package inputenc Error: Unicode char not set up for use with LaTeX` problem?solve “Unicode char is not set up for use with LaTeX” without special handling of every new interesting UTF-8 characterPackage inputenc Error: Unicode character ² (U+B2)(inputenc) not set up for use with LaTeX. acroI2C[I²C]package inputenc error unicode char (u + 190) not set up for use with latexPackage inputenc Error: Unicode char u8:′ not set up for use with LaTeX. 3′inputenc Error: Unicode char u8: not set up for use with LaTeX with G-BriefPackage Inputenc Error: Unicode char u8: not set up for use with LaTeXPackage inputenc Error: Unicode char ́ (U+301)(inputenc) not set up for use with LaTeX. includePackage inputenc Error: Unicode char ̂ (U+302)(inputenc) not set up for use with LaTeX. … $widehatleft (OA,AA' right )$Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc) not set up for use with LaTeX. printbibliography[heading=bibintoc]Package inputenc Error: Unicode char − (U+2212)(inputenc) not set up for use with LaTeXPackage inputenc Error: Unicode character α (U+3B1) not set up for use with LaTeXPackage inputenc Error: Unicode characterError: ! Package inputenc Error: Unicode char ⊘ (U+2298)(inputenc) not set up for use with LaTeX
Monthly twice production release for my software project
How to make a software documentation "officially" citable?
Was a professor correct to chastise me for writing "Prof. X" rather than "Professor X"?
How to safely derail a train during transit?
How can I filter or show only one of the duplicates in the results when using Find-Item command?
What happens if you roll doubles 3 times then land on "Go to jail?"
Clustering points and summing up attributes per cluster in QGIS
How easy is it to start Magic from scratch?
What can we do to stop prior company from asking us questions?
Science fiction short story involving a paper written by a schizophrenic
Is a stroke of luck acceptable after a series of unfavorable events?
I believe this to be a fraud - hired, then asked to cash check and send cash as Bitcoin
Why does standard notation not preserve intervals (visually)
How to prepend a string to only the lines of text which are numbers
Anatomically Correct Strange Women In Ponds Distributing Swords
How can I quit an app using Terminal?
Is it safe to use c_str() on a temporary string?
Why doesn't a table tennis ball float on a surface of steel balls? How do we calculate buoyancy here?
How to write the block matrix in LaTex?
Why do professional authors make "consistency" mistakes? And how to avoid them?
Is HostGator storing my password in plaintext?
Return the Closest Prime Number
What do "high sea" and "carry" mean in this sentence?
Would this house-rule that treats advantage as a +1 to the roll instead (and disadvantage as -1) and allows them to stack be balanced?
inputenc: Unicode character … not set up for use with LaTeX
The Next CEO of Stack OverflowEntering Unicode characters in LaTeXHow to solve the `Package inputenc Error: Unicode char not set up for use with LaTeX` problem?solve “Unicode char is not set up for use with LaTeX” without special handling of every new interesting UTF-8 characterPackage inputenc Error: Unicode character ² (U+B2)(inputenc) not set up for use with LaTeX. acroI2C[I²C]package inputenc error unicode char (u + 190) not set up for use with latexPackage inputenc Error: Unicode char u8:′ not set up for use with LaTeX. 3′inputenc Error: Unicode char u8: not set up for use with LaTeX with G-BriefPackage Inputenc Error: Unicode char u8: not set up for use with LaTeXPackage inputenc Error: Unicode char ́ (U+301)(inputenc) not set up for use with LaTeX. includePackage inputenc Error: Unicode char ̂ (U+302)(inputenc) not set up for use with LaTeX. … $widehatleft (OA,AA' right )$Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc) not set up for use with LaTeX. printbibliography[heading=bibintoc]Package inputenc Error: Unicode char − (U+2212)(inputenc) not set up for use with LaTeXPackage inputenc Error: Unicode character α (U+3B1) not set up for use with LaTeXPackage inputenc Error: Unicode characterError: ! Package inputenc Error: Unicode char ⊘ (U+2298)(inputenc) not set up for use with LaTeX
My system's configuration of inputenc
appears to be missing some fallback setup, so that Unicode characters produce an error:
documentclassarticle
begindocument
The remarkable double pulsar PSR J0737−3039A/B provides similar
higher-precision tests.
enddocument
The character in the middle of the name, there, is a dash, U+2212. On one system, this works fine:
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2017-04-15>
Babel <3.10> and hyphenation patterns for 84 language(s) loaded.
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
[1/usr/local/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map]
(./try.aux) )
(see the transcript file for additional information)</usr/local/texlive/2017/te
xmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on try.pdf (1 page, 16951 bytes).
Transcript written on try.log.
On another, not so much:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2018-12-01>
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
! Package inputenc Error: Unicode character − (U+2212)
(inputenc) not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H <return> for immediate help.
...
l.4 The remarkable double pulsar PSR J0737−
3039A/B provides similar
?
The first machine has (as you can see) TeXLive 2017, and has been used/tweaked/extended in normal use for a while (that is, it may be in a significantly but not drastically non-default state); the second is a freshly-downloaded TeXLive 2018 (both are macOS, but I'd be surprised if that's relevant).
I'm having difficulty seeing why this works on the first machine and not the second, and, separately, how to fix it.
The various related tex.stackexchange.com questions and answers (1, 2, 3, 4, 5) are generally concerned with specific characters, and the fixes suggested are to do with explicitly declaring characters, or using one or other alternative. I'm concerned with how it is that TeXLive 2017, or I (accidentally or deliberately), have apparently configured inputenc so that pdftex+inputenc works with this MWE, in a way that vanilla TeXLive 2018 doesn't.
A RedHat support question mentions updating the various map files that pdftex consults. This is clearly close to the answer, because I do notice that the first, working, system reads pdftex.map
, and the second doesn't. My updmap.cfg
looks broadly plausible, and kpsewhich pdftex.map
produces /usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map
with plausible contents. I've run updmap-sys
; I haven't run the commands suggested in that RedHat thread, partly because I don't know what they do, partly because they seem specific to a particular font map, and partly because I'd like to make this a useful site question.
Things that I'm ruling out on immediate practical grounds:
- I don't want to fiddle with the
inputenc
declarations: the source, that the above MWE is an extract of, is using a publisher's style file, which I don't want to monkey with. For what it's worth, I can't spot any Unicode cleverness in the style files, - Normally, the answer to any unicode question is ‘use XeTeX or LuaTeX’; since I'm using a publisher's workflow, that's not really open to me
- I could of course change the Unicode hyphen to just
--
, and this is what I'll probably do in fact, to make this problem go away.
Thus my question is: what do I do (or what have I done in the past) to make this MWE work unchanged with pdflatex?
I'm aware this is a slightly naïve question, and I haven't done a huge amount of digging into fixing it myself, but (a) to some extent I treasure my ignorance of pdftex+inputenc (just use XeTeX!), and (b) I'm surprised that I can't find a question matching this on TeX.SE, and it might be useful for this to be that question. I'd be surprised if I'm the only person to have this problem, but googling is surprisingly little help, partly since most folk ask, and have answered, a more specific ‘why doesn't character X work?’ question.
input-encodings updmap
add a comment |
My system's configuration of inputenc
appears to be missing some fallback setup, so that Unicode characters produce an error:
documentclassarticle
begindocument
The remarkable double pulsar PSR J0737−3039A/B provides similar
higher-precision tests.
enddocument
The character in the middle of the name, there, is a dash, U+2212. On one system, this works fine:
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2017-04-15>
Babel <3.10> and hyphenation patterns for 84 language(s) loaded.
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
[1/usr/local/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map]
(./try.aux) )
(see the transcript file for additional information)</usr/local/texlive/2017/te
xmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on try.pdf (1 page, 16951 bytes).
Transcript written on try.log.
On another, not so much:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2018-12-01>
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
! Package inputenc Error: Unicode character − (U+2212)
(inputenc) not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H <return> for immediate help.
...
l.4 The remarkable double pulsar PSR J0737−
3039A/B provides similar
?
The first machine has (as you can see) TeXLive 2017, and has been used/tweaked/extended in normal use for a while (that is, it may be in a significantly but not drastically non-default state); the second is a freshly-downloaded TeXLive 2018 (both are macOS, but I'd be surprised if that's relevant).
I'm having difficulty seeing why this works on the first machine and not the second, and, separately, how to fix it.
The various related tex.stackexchange.com questions and answers (1, 2, 3, 4, 5) are generally concerned with specific characters, and the fixes suggested are to do with explicitly declaring characters, or using one or other alternative. I'm concerned with how it is that TeXLive 2017, or I (accidentally or deliberately), have apparently configured inputenc so that pdftex+inputenc works with this MWE, in a way that vanilla TeXLive 2018 doesn't.
A RedHat support question mentions updating the various map files that pdftex consults. This is clearly close to the answer, because I do notice that the first, working, system reads pdftex.map
, and the second doesn't. My updmap.cfg
looks broadly plausible, and kpsewhich pdftex.map
produces /usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map
with plausible contents. I've run updmap-sys
; I haven't run the commands suggested in that RedHat thread, partly because I don't know what they do, partly because they seem specific to a particular font map, and partly because I'd like to make this a useful site question.
Things that I'm ruling out on immediate practical grounds:
- I don't want to fiddle with the
inputenc
declarations: the source, that the above MWE is an extract of, is using a publisher's style file, which I don't want to monkey with. For what it's worth, I can't spot any Unicode cleverness in the style files, - Normally, the answer to any unicode question is ‘use XeTeX or LuaTeX’; since I'm using a publisher's workflow, that's not really open to me
- I could of course change the Unicode hyphen to just
--
, and this is what I'll probably do in fact, to make this problem go away.
Thus my question is: what do I do (or what have I done in the past) to make this MWE work unchanged with pdflatex?
I'm aware this is a slightly naïve question, and I haven't done a huge amount of digging into fixing it myself, but (a) to some extent I treasure my ignorance of pdftex+inputenc (just use XeTeX!), and (b) I'm surprised that I can't find a question matching this on TeX.SE, and it might be useful for this to be that question. I'd be surprised if I'm the only person to have this problem, but googling is surprisingly little help, partly since most folk ask, and have answered, a more specific ‘why doesn't character X work?’ question.
input-encodings updmap
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago
add a comment |
My system's configuration of inputenc
appears to be missing some fallback setup, so that Unicode characters produce an error:
documentclassarticle
begindocument
The remarkable double pulsar PSR J0737−3039A/B provides similar
higher-precision tests.
enddocument
The character in the middle of the name, there, is a dash, U+2212. On one system, this works fine:
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2017-04-15>
Babel <3.10> and hyphenation patterns for 84 language(s) loaded.
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
[1/usr/local/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map]
(./try.aux) )
(see the transcript file for additional information)</usr/local/texlive/2017/te
xmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on try.pdf (1 page, 16951 bytes).
Transcript written on try.log.
On another, not so much:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2018-12-01>
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
! Package inputenc Error: Unicode character − (U+2212)
(inputenc) not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H <return> for immediate help.
...
l.4 The remarkable double pulsar PSR J0737−
3039A/B provides similar
?
The first machine has (as you can see) TeXLive 2017, and has been used/tweaked/extended in normal use for a while (that is, it may be in a significantly but not drastically non-default state); the second is a freshly-downloaded TeXLive 2018 (both are macOS, but I'd be surprised if that's relevant).
I'm having difficulty seeing why this works on the first machine and not the second, and, separately, how to fix it.
The various related tex.stackexchange.com questions and answers (1, 2, 3, 4, 5) are generally concerned with specific characters, and the fixes suggested are to do with explicitly declaring characters, or using one or other alternative. I'm concerned with how it is that TeXLive 2017, or I (accidentally or deliberately), have apparently configured inputenc so that pdftex+inputenc works with this MWE, in a way that vanilla TeXLive 2018 doesn't.
A RedHat support question mentions updating the various map files that pdftex consults. This is clearly close to the answer, because I do notice that the first, working, system reads pdftex.map
, and the second doesn't. My updmap.cfg
looks broadly plausible, and kpsewhich pdftex.map
produces /usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map
with plausible contents. I've run updmap-sys
; I haven't run the commands suggested in that RedHat thread, partly because I don't know what they do, partly because they seem specific to a particular font map, and partly because I'd like to make this a useful site question.
Things that I'm ruling out on immediate practical grounds:
- I don't want to fiddle with the
inputenc
declarations: the source, that the above MWE is an extract of, is using a publisher's style file, which I don't want to monkey with. For what it's worth, I can't spot any Unicode cleverness in the style files, - Normally, the answer to any unicode question is ‘use XeTeX or LuaTeX’; since I'm using a publisher's workflow, that's not really open to me
- I could of course change the Unicode hyphen to just
--
, and this is what I'll probably do in fact, to make this problem go away.
Thus my question is: what do I do (or what have I done in the past) to make this MWE work unchanged with pdflatex?
I'm aware this is a slightly naïve question, and I haven't done a huge amount of digging into fixing it myself, but (a) to some extent I treasure my ignorance of pdftex+inputenc (just use XeTeX!), and (b) I'm surprised that I can't find a question matching this on TeX.SE, and it might be useful for this to be that question. I'd be surprised if I'm the only person to have this problem, but googling is surprisingly little help, partly since most folk ask, and have answered, a more specific ‘why doesn't character X work?’ question.
input-encodings updmap
My system's configuration of inputenc
appears to be missing some fallback setup, so that Unicode characters produce an error:
documentclassarticle
begindocument
The remarkable double pulsar PSR J0737−3039A/B provides similar
higher-precision tests.
enddocument
The character in the middle of the name, there, is a dash, U+2212. On one system, this works fine:
This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2017-04-15>
Babel <3.10> and hyphenation patterns for 84 language(s) loaded.
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/local/texlive/2017/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
[1/usr/local/texlive/2017/texmf-var/fonts/map/pdftex/updmap/pdftex.map]
(./try.aux) )
(see the transcript file for additional information)</usr/local/texlive/2017/te
xmf-dist/fonts/type1/public/amsfonts/cm/cmr10.pfb>
Output written on try.pdf (1 page, 16951 bytes).
Transcript written on try.log.
On another, not so much:
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2018) (preloaded format=pdflatex)
restricted write18 enabled.
entering extended mode
(./try.tex
LaTeX2e <2018-12-01>
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/article.cls
Document Class: article 2018/09/03 v1.4i Standard LaTeX document class
(/usr/local/texlive/2018/texmf-dist/tex/latex/base/size10.clo)) (./try.aux)
! Package inputenc Error: Unicode character − (U+2212)
(inputenc) not set up for use with LaTeX.
See the inputenc package documentation for explanation.
Type H <return> for immediate help.
...
l.4 The remarkable double pulsar PSR J0737−
3039A/B provides similar
?
The first machine has (as you can see) TeXLive 2017, and has been used/tweaked/extended in normal use for a while (that is, it may be in a significantly but not drastically non-default state); the second is a freshly-downloaded TeXLive 2018 (both are macOS, but I'd be surprised if that's relevant).
I'm having difficulty seeing why this works on the first machine and not the second, and, separately, how to fix it.
The various related tex.stackexchange.com questions and answers (1, 2, 3, 4, 5) are generally concerned with specific characters, and the fixes suggested are to do with explicitly declaring characters, or using one or other alternative. I'm concerned with how it is that TeXLive 2017, or I (accidentally or deliberately), have apparently configured inputenc so that pdftex+inputenc works with this MWE, in a way that vanilla TeXLive 2018 doesn't.
A RedHat support question mentions updating the various map files that pdftex consults. This is clearly close to the answer, because I do notice that the first, working, system reads pdftex.map
, and the second doesn't. My updmap.cfg
looks broadly plausible, and kpsewhich pdftex.map
produces /usr/local/texlive/2018/texmf-var/fonts/map/pdftex/updmap/pdftex.map
with plausible contents. I've run updmap-sys
; I haven't run the commands suggested in that RedHat thread, partly because I don't know what they do, partly because they seem specific to a particular font map, and partly because I'd like to make this a useful site question.
Things that I'm ruling out on immediate practical grounds:
- I don't want to fiddle with the
inputenc
declarations: the source, that the above MWE is an extract of, is using a publisher's style file, which I don't want to monkey with. For what it's worth, I can't spot any Unicode cleverness in the style files, - Normally, the answer to any unicode question is ‘use XeTeX or LuaTeX’; since I'm using a publisher's workflow, that's not really open to me
- I could of course change the Unicode hyphen to just
--
, and this is what I'll probably do in fact, to make this problem go away.
Thus my question is: what do I do (or what have I done in the past) to make this MWE work unchanged with pdflatex?
I'm aware this is a slightly naïve question, and I haven't done a huge amount of digging into fixing it myself, but (a) to some extent I treasure my ignorance of pdftex+inputenc (just use XeTeX!), and (b) I'm surprised that I can't find a question matching this on TeX.SE, and it might be useful for this to be that question. I'd be surprised if I'm the only person to have this problem, but googling is surprisingly little help, partly since most folk ask, and have answered, a more specific ‘why doesn't character X work?’ question.
input-encodings updmap
input-encodings updmap
asked 18 mins ago
Norman GrayNorman Gray
5,61611929
5,61611929
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago
add a comment |
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f482100%2finputenc-unicode-character-not-set-up-for-use-with-latex%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f482100%2finputenc-unicode-character-not-set-up-for-use-with-latex%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The default encoding in 2018 is utf8, not so in 2017. In 2017, when there is no input enc specified ascii (?) seems to be assumes, so everything else is ignored, including your U+2212 and my Danish vowels æøå.
– daleif
15 mins ago