Tag Info

New answers tagged

5

The fonts used by mathdesign are not compatible with XeLaTeX and fontspec, because they're neither OpenType nor TrueType fonts. Replace \usepackage{xltxtra} with \usepackage[utf8]{inputenc} and compile with pdflatex.


0

Note: The OP used xelatex for compilation and everything was fine after changing to pdflatex. However, I leave my old answer here for archive purposes. If it worked for that letter before, you probably saved the file with an editor that converted it from utf-8 to some other format. If it is a new letter you are entering (not ö, which should work), you can ...


10

There is no difference. The character Σ is translated into \u8:Σ which is a single macro whose name is five character long, because Σ is two byte in UTF-8. This macro, in turn, is translated into \IeC{\textSigma} and, in a typesetting context, it becomes \textSigma The definition of this macro is \LGR-cmd \textSigma \LGR\textSigma which is three ...


0

This shouldn't be a problem. UTF-8 is meanwhile even standard on Microsoft. Maybe you could try the following: Download a good cross-plattform Latex Editor like Texmaker or TeXstudio. Open with the program a new file and copy your existing code into it.


1

Well, most of your questions have already been answered either in the question itself or in the comments, so here's just a recap to satisfy the site's mores: The workaround to allow spaces in keywords that microtype.dtx employs is to use the "non-breaking space" in lieu of a normal space to make listings believe that it's a letter, while it will be output ...



Top 50 recent answers are included