Note that there are some explanatory texts on larger screens.

plurals
  1. POInvalid characters in generated latex sources in Doxygen?
    primarykey
    data
    text
    <p>I'm running doxygen (1.5.8) on a C# project off of Visual Studio 2008 on a Windows machine running XP. While generating the latex code, some illegal sequences are included. It always involves the following sequence: "" (a latin-i with a dieresis, something like the binary shift operator, and a Spanish open-question-mark). I've seen it happen in the context "using {\bf System}", but maybe there are others.</p> <p>The generated latex file reads</p> <pre><code> \begin{CompactItemize} \item using {\bf System} \end{CompactItemize} </code></pre> <p>While the source is simply:</p> <pre><code>using System; using System.Collections.Generic; using System.Linq; </code></pre> <p>Some strange Windows BOF character? It seems it's only before the using System; directive (the first of each file).</p> <p>EDIT: Thanks to all. As it was stated in my accepted answer below, this is the BYTE_ORDER_MARK character. Obviously and unsurprisingly, Visual Studio is acting up. Good thing is that there is a way to save files in UTF-8 without the BOM signature. File -> Advanced Save Options -> Encoding (UTF-8 without signature) - Codepage 65001. Bad thing is that there seems to be no way to save all the existing files of a solution with this encoding in batch, so to speak, and each file has to be saved independently. Another quirk I found (at least in my case), is that File -> Advanced Save Options is not available until you double click on the class and the file is open in the editor. Oh well...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload