\ohm does not work with newtxsf package

Question

\ohm does not work with newtxsf package

PrometeuszJasinski opened this issue a year ago · 15 comments

Great package and I'm currently moving from v2 to v3 where an issue came up: When I load the newtxsf package, the Omega is not displayed correctly with pdflatex. It is just a ' symbol in the output.

\documentclass[11pt, dvipsnames, oneside]{article}

\usepackage{geometry}
\usepackage[utf8]{inputenc}
\usepackage{siunitx}
\usepackage[T1]{fontenc}

%\usepackage{newtxsf} % ohm does not work with newtxsf
\begin{document}Enjoy writing your document!


\qty{2}{\kilo\Omega}

\qty{2}{\kilo\ohm}

\qty{2}{\micro\metre}

\qty{2}{\percent}

\qty{2}{\degreeCelsius}

\qty{2}{\degree}

$\omega$ $\Omega$
\end{document}

Any ideas how to restore this?

Answer 1 · 2024-01-22T13:04:41.000Z

Did you try moving newtxsf up before loading siunutx?

Answer 2 · 2024-01-22T13:19:42.000Z

Did you try moving newtxsf up before loading siunutx?

That in itself is a bug ... which I'll look at :)

Answer 3 · 2024-01-22T13:27:58.000Z

Thanks for the quick support. Yes, it works.
It seems like T1 must also be last, cause the below order does not work either.
Sorry that I'm not used to care about the order of inputs based on my c++ background.

\usepackage{geometry}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{newtxsf}
\usepackage{siunitx}

Answer 4 · 2024-01-22T13:45:26.000Z

Sorry that I'm not used to care about the order of inputs based on my c++ background.

Ideally it shouldn't matter - the LaTeX team have provides some tools to improve this, and I will look to avoid the issue

Answer 5 · 2024-01-22T13:49:49.000Z

Really appreciated!

Answer 6 · 2024-01-24T07:58:16.000Z

The ordering issue is out of the control of siunitx: it relates to how newxsf sets up fonts dependent on encoding:

\documentclass{article}
\usepackage{newtxsf} % Comment here for a difference
\usepackage[T1]{fontenc}
\usepackage{newtxsf}
\begin{document}
$\mathrm{\Omega}\mathrm{\upOmega}$
\end{document}

Answer 7 · 2024-01-24T07:59:43.000Z

Basic issue here is that siunitx places each unit inside \mathrm (as standard), and with the T1 encoding loaded, newtxsf gives problematic output for \Omega and \upOmega in that case. I will therefore have to check explicitly for the package and use an alternative definition: coming up.

Answer 8 · 2024-01-24T08:01:15.000Z

See #435 for discussion of the semantics of \mathrm and its relation to non-Latin symbols.

Answer 9 · 2024-01-24T08:24:28.000Z

Sorted but I have to say the package does itself no favours: try

\renewcommand{\familydefault}{\sfdefault}

before or after loading it and find ... pain with \mathrm.

Answer 10 · 2024-01-24T08:52:46.000Z

I’m the last one to complain and happy to hear a workaround. Thanks!

Answer 11 · 2024-01-25T06:42:21.000Z

I've had a mail from the package author: he's fixed at his end. Looking at the issue, that's the better approach, as what I was thinking of is a work-around. I'd rather avoid that if possible, so will back out my change - you can always apply locally.

Answer 12 · 2024-01-25T09:10:41.000Z

What a great community. Thanks!