Bug#683620: texlive-latex-base: ts1enc.dfu has incorrect Unicode character definitions, overriding the user's settings
On 2012-08-03 11:02:38 +0900, Norbert Preining wrote:
> I don't see a bug here. It depends on the font or additional
> packages if \textpm is defined or not, that was always like this
> afair.
>
> Same with mathmode vs non math mode.
>
> So unless you see a document that stated that this should work out
> if the box (which would surprise me) this is not a bug.
In such a case, the file should not be included without an explicit
request from the user (or possibly via a package directly related to
it).
> Furthermore, it it seems to be a problem with siunitx, not latex
> itself, right?
I don't know. I've looked at the problem more closely, and what
happens is that siunitx.sty does something equivalent to:
\AtBeginDocument {
\DeclareFontEncoding{TS1}{}{}
}
I can reproduce the problem with:
\documentclass{article}
\usepackage[utf8]{inputenc}
\DeclareUnicodeCharacter{00B1}{\ensuremath{\pm}}
\DeclareUnicodeCharacter{00B7}{\ensuremath{\cdot}}
\DeclareFontEncoding{TS1}{}{}
\begin{document}
Plus or minus: $±$ and ±.
Cdot: $·$ and ·.
\end{document}
\DeclareFontEncoding{TS1}{}{} has the effect to load
/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.dfu
because utf8.def (loaded by \usepackage[utf8]{inputenc}) modifies
\DeclareFontEncoding to do, in particular:
\InputIfFileExists{#1enc.dfu}
Is it normal that declaring a font encoding messes with the
input encoding? (I don't see how this could make sense when
the font encoding isn't even active like here.)
What is in cause?
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: