the3dfxdude
commented
4 years ago This is happening for you because your latex version is out of date, and utf8 is the default encoding now. However this change should be fine. Not sure if we will need to require a minimum latex version.
J-Moravec
Some characters did not render properly (at least on pdflatex and on my system) because while they were written correctly in the source files (such as ø in Bjørn Lynne), by default LaTeX does not support anything but ASCII.
One choice is to fix all these UTF8 characters with a code that will render them (e.g.
\o{}will render as ø). The other option is to load the package inputenc, which for some reason was missing (the opposite package that renders these symbols is called fontenc and is already loaded).For more information, see: https://en.wikibooks.org/wiki/LaTeX/Special_Characters
Note that this might have hide some special characters that just look like normal letters but aren't. I have previously saw that there was some snafu around Balista. This fix does not solve the source of the error, but merely hide it so it is not visible in the manual. I think that trying to fix every special character that might have gotten into the source would be a lot of work and this does sufficiently solve the visible problem. Every non-standard characters can be fixed later when they become problem again (or when editing their local area).
I have went through the whole PDF to look if there is any special character that does not render properly, but couldn't find any, so I think this is a good fix.