# How to write the symbol >

I had a look at the symbols list, and it is written that the input text ">" should be rendered as ">". In my document, however, it is rendered as "¿".

How do I write a normal ">"?

• as Heiko says in his answer it is only an issue on OT1 encoding, but also, it is only an issue in text > should almost always be in math mode where a > will always be typeset as > – David Carlisle May 19 '18 at 16:50
• I think the real question is in what context are you trying to "write a normal >"? My guess is that you should be in math mode, or using a verbatim environment. – Teepeemm May 19 '18 at 20:37
• while the comments and answers are valid, this question would make much more sense if you showed the context in which you are using the symbol. – barbara beeton May 19 '18 at 21:33

Very likely you are using the old OT1 encoding:

\documentclass{article}
\begin{document}
<Hello> \textless world\textgreater
\end{document}


The example also shows how to typeset < and > by using \textless or \textgreater.

The issue is resolved with the T1 font encoding:

\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{lmodern}% optional
\begin{document}
<Hello> \textless world\textgreater
\end{document}


Alternatively, load fontspec (or a package that loads it, such as unicode-math or polyglossia) to use Unicode as your encoding. This will support a much wider variety of symbols.

However, David Carlisle points out that, if your TeX engine supports fontspec, it is unlikely that you would have this bug to begin with.

• unicode-math is very unlikely to make any difference to the > in the question, which is not in math mode. – David Carlisle May 19 '18 at 18:53
• @DavidCarlisle Agreed. As you know,fontspec is what affects text mode and unicode-math loads it as well. So, loading either would work. – Davislor May 19 '18 at 20:24
• I think you would be hard pressed to make an example where loading either fontspec or unicode-math changes a ¿ to a >, basically this answer is wrong. – David Carlisle May 19 '18 at 20:25
• It's still wrong – David Carlisle May 19 '18 at 20:26
• @DavidCarlisle If the problem is the OT1 encoding, changing to Unicode will work as well as T1. If it's the encoding of the input file, any engine that can load fontspec supports Unicode anyway. – Davislor May 19 '18 at 20:29