Tag Info

New answers tagged


I found a partial solution with adding \usepackage{newunicodechar} \newunicodechar⊥{{$\bot$}} This is somewhat unsatisfactory, because it requires an addition for each symbol desired.


The package wasysym has nothing to do with \textrecipe. The command is defined in standard LaTeX by the textcomp package, which is not to be loaded with XeLaTeX and fontspec. The problem is that the Sanskrit 3000 font has no glyph for ℞ (U+211E PRESCRIPTION TAKE) so \textrecipe produces nothing (with XeLaTeX a small square is drawn). You can substitute the ...


I guess that your font does not provide this symbol (here is a collection of fonts, which do). Therefore, you will have to redefine this command in order to use an other font for this very symbol: % arara: xelatex \documentclass{article} \usepackage{fontspec} \setmainfont{Sanskrit2003.ttf} ...


Vollkorn Here is a great open-source font from Friedrich Althausen with eight styles and multilingual support. http://vollkorn-typeface.com/. The following font flavors are supported: PostScript OpenType .otf TrueType OpenType .ttf Web open Font Format .woff Embedded OpenType .eot Ligatures Glyphs Kerning Found in this tex.stackexchange ...


The class europecv says \DeclareOption{utf8}{\AtEndOfClass{\inputencoding{utf8x}}} which is a very big mistake. At the time the class was first released, utf8 didn't support direct input with Greek, which was the main reason for using utf8x. Since some years, utf8 does support Greek, so there's no reason for keeping the option in that way. However, for ...


The mapping substitutions work on a character basis, but XeTeX never uses the space character; rather, it changes space tokens into horizontal glue, so when the substitution stage is reached, there's never a combination U+0020 U+00B7. You can use newunicodechar for this purpose: \documentclass{article} \usepackage{fontspec} ...


Presumably (you did not say) you are using lualatex or xelatex. These engines do not work with inputenc methods. The class seems to make assumptions about use of inputenc so it is only written for latex or pdflatex.


You can input any Unicode characters directly and compile them to PDF simply by using LuaLaTeX or XeLaTeX to compile (e.g., lualatex file in the terminal). You can also rotate text using the rotating package. With the turn environment you can rotate text to any desired degree (see texdoc rotating). The source must be encoded UTF-8, you must compile with ...


If you use a unicode based tex such as xelatex or luatex it works naturally: \documentclass{article} \usepackage{fontspec} \setmainfont{Arial} \begin{document} ˙ʎɐpoʇ ʎddɐɥ ɯɐ I ? \end{document}


\documentclass{standalone} \usepackage{tikz} \newcommand{\whatzit}{\tikz{\path node[anchor=base,inner sep=0pt](a){$<$} (a.center) +(0pt,.25ex) node[rotate=-30,scale=.6]{$=$};}} \begin{document} Text with \whatzit{} in the middle. \end{document}


Ok, figured it out, and how to do it with latexmk. Put $biber = 'biber --bblsafechars %O %B'; in ~/.latexmkrc.


You don't need \foreignlanguage in the .bib file. Use biblatex option autolang=other instead. It automatically wraps bib entries in the otherlanguage environment. For this to work you also need langid fields in the .bib file. This is your MWE corrected (I removed the font setup, it doesn't work on my machine for some reason --- but I guess it's a different ...


I see nothing strange with \lstset{ extendedchars=true, language=java, basicstyle=\ttfamily, showspaces=false, showstringspaces=false, literate=% {€}{\euro}1% {§}{\S}1% {°}{\textdegree{}}1% {ä}{{\"a}}1% {ö}{{\"o}}1% {ü}{{\"u}}1% {ß}{{\ss}}1% {Ä}{{\"A}}1% {Ö}{{\"O}}1% {Ü}{{\"U}}1% {µ}{\textmu}1% ...


You may get this error also if you use different language for bibtex. In that case project.bbl may contain characters in different encoding (e.g latin2). What you need to do is swap encoding when rendering bibliography to latin2 and switch back to utf8 after. \inputencoding{latin2} \bibliography{mybib} \inputencoding{utf8} Hope this helps.


The listings package is not compatible with Unicode, only with extended ASCII. The listingsutf8 package provides some support for UTF-8 but, in general, if you want to typeset listings that contain Unicode characters, you're better off using one of the packages that fully support it, such as minted or pythontex. Besides, copying & pasting listings is ...

Top 50 recent answers are included