23

When I use the copyright symbol $\copyright$ the messages:

Missing character: There is no © in font txr!
Missing character: There is no © in font txr!
Missing character: There is no © in font txr!
Missing character: There is no © in font txr!

these are displayed in the log file and the symbol is not displayed (why the message is printed four times instead of one)? is there another way to print this symbol? thanks a lot

Saravanan
  • 1,475

2 Answers2

24

The copyright and other textcomp package symbols are not usable in math mode.

In case you want the symbols to appear as a superscript in text mode, you can try to use

\textsuperscript{\textcopyright}
Cragfelt
  • 4,005
11

This is a good example of why questions need a MWE. Writing $\copyright$ should have worked. (Sort of: the spacing is wrong because you enter and leave math mode.) The error message says you were using the font txr, which is from txfonts and defines this symbol correctly. (At least, as of 2020, but the package has not been updated since you asked your question.)

Without a MWE or any information about what versions of packages you’re using, it’s impossible to tell what the problem is.

In TeX Live 2020, I get:

\tracinglostchars=2
\documentclass{article}
\usepackage{txfonts}

\pagestyle{empty}

\begin{document} \noindent Literal: © \ Textcomp: \textcopyright \ {\LaTeXe} (text): \copyright \ {\LaTeXe} (math): (\copyright) \ TS1: {\fontencoding{TS1}\selectfont\symbol{"A9}} \end{document}

txfonts

There’s a newer package to replace txfonts, which has not been updated since 2005. But that shouldn’t make a difference here. the LaTeX kernel defines \copyright to use the same symbol as \textcopyright in either text or math mode. It defines \textcopyright in at least four different ways, but the default definition takes the symbol from the 8-bit TS1 encoding. There is a TS1txr.fd in the txfonts package, and it contains this symbol.

Either some other package you loaded breaks \copyright, or you should upgrade your TeX distribution, or perhaps updating to fontspec or newtxtext would fix this for you.

Davislor
  • 44,045