# Tag Info

1

This works perfectly when compiled with pdflatex: \documentclass[]{article} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \begin{document} Niels Søgaard \end{document} If you get an inputenc error then the file with the ø is not utf8 encoded and you need to reencode it. Or create a new utf8 document and copy and paste the content to it. You ...

4

This answer is based on an email from Hans Hagen. One way to achieve the desired output is using formatters. For example: \starttext \startluacode local text='&\%*_' context("%!tex!", text) \stopluacode \stoptext The %!tex! is plug to the formatters and tex is one of the pre-defined formatters. Other pre-defined formatters are lua and xml (which ...

4

The bug fix has been released to CTAN as of the v2.5-1 release. \documentclass{scrartcl} \usepackage{luatextra} \defaultfontfeatures{Ligatures=TeX} \setmainfont{Linux Libertine} \begin{document} Test -- endash and --- emdash {\scshape Test -- endash and --- emdash} \end{document} with luaotfload.sty 2014/07/16 v2.5-1 OpenType layout system ...

2

Eventually I was able to find the reason with the great help of the comments to my question. For those observing similar problems, I post an answer here. The missing \partial comes from reassigning unicode ranges to different fonts. Don't do it unless you know what the side effects are. I didn't and therefore another problem was hidden by this wrong ...

1

I found the solution: Lua uses a font name data base, which I had to update using the command: luaotfload-tool --update

1

I am summarizing the comments here, but the gist is: @phg suggested that one can escape by using catcodes. There is the verbatim catcode, but it has issues with linebreaks. An alternative, albeit undocumented but seemingly preferable (i.e. escapes without wrapping issues), catcode is \notcatcodes. One can employ this in Lua to escape any string with the ...

5

You have to use a font that has the required glyphs. They are in FreeSerif, for instance. Here's how you can use them directly, by hiding the font change in a macro: \documentclass{scrartcl} \usepackage{fontspec} \usepackage{newunicodechar} \setmainfont{Linux Libertine O} \setsansfont{Linux Biolinum O} \newfontface{\freeserif}{FreeSerif} % for the ...

3

I've been using the following for mplib with OpenType fonts in luatex (no format): \input luaotfload.sty \input luamplib.sty %\mplibsetformat{metafun} % optional use of metafun extensions \mplibcode beginfig(1); label.rt(btex sup etex, origin); label.top("test", origin); endfig; \endmplibcode %%%% Example Using an OpenType font %%%% \font\bigfont = ...

8

The logos can be found on the internet. You can then insert the logos using the includegraphics command. \section{\includegraphics[scale=0.03]{linkedinLogo.png}} {linkedin.com/in/yourname} ~ \section{\includegraphics[scale=0.03]{skypeLogo.png}} {skype:yourname?call} ~ Another possibility is to draw the logos using Tikz. I have created the LinkedIN logo in ...

3

With utf8 the Unicode character € is mapped to \texteuro, which requires textcomp. The definition of \texteuro is \DeclareTextCommandDefault{\texteuro} {\CheckEncodingSubset\UseTextSymbol{TS1}\tc@fake@euro5\texteuro} If the TS1 font for the current family is known not to have the Euro symbol (that is, it belongs to class 5), the glyph is faked by means ...

7

LaTeX does not need to check anything, the T1 encoding doesn't include euro by definition. It is in the TS1 encoding (as used by textcomp) and of course in the EU1 and EU2 encodings used by lua and xe latex.

4

You can use these icons (that are part ot the font since version 4) with this code : \documentclass[a4paper, 12pt]{article} \usepackage[x11names]{xcolor} \usepackage{array} \usepackage{fontspec} \setmainfont{Minion Pro} \usepackage{fontawesome} \def\faSkype{\FA\symbol{"F17E}} \def\faLinux{\FA\symbol{"F17C}} \def\faTh{\FA\symbol{"F00A}} ...

1

A bit late to the party, but this fix to http://tex.stackexchange.com/users/243/topskip's answer does the job: in response to question in comments: In topskip's answer Hello World is still written to the pdf file, which is not typically what one would want. So I've taken his answer and made the change that if the line read does not contain "\end{foobar}" ...

4

The problem has been discussed some time ago http://comments.gmane.org/gmane.comp.tex.live/30992 but imho never really been investigated (it doesn't make much sense to use such fonts with lualatex and so there is not much pressure in resolving a rather harmless warning). You could open a bug report at ...

4

It seems that siunitx is missing some kind of "default" font for the cases except \mathscr and \mathscrbf: \documentclass{minimal} \usepackage{fontspec,luatextra,unicode-math} \usepackage[noload=abbr]{siunitx} \sisetup{decimalsymbol=comma, detect-all,debug} \let\nbu\SI \setmathfont{latinmodern-math.otf} ...

12

The PGF releases on CTAN and sourceforge contain a bug where the interaction of shadings/transparency and the standalone package and xelatex (and xdvipdfmx) causes problems. The code will work if, for example, the document class is set to article (and, obviously \usepackage{tikz} is added to the preamble). This was fixed in the CVS version back in January. ...

2

This is another solution, without extra package. \documentclass{article} \usepackage{fontspec} \usepackage{polyglossia} \setmainlanguage{french} \makeatletter \newcommand{\nospace}[1]{\nofrench@punctuation\texttt{#1}\french@punctuation} \makeatother \begin{document} \nospace{a:b} \end{document} Thanks all.

4

Probably Polyglossia should offer the possibility of disabling the automatic spacing feature for French in certain contexts such as monospaced text. However, here's how you can do it: \documentclass{article} \usepackage{fontspec} \usepackage{polyglossia} \usepackage{xpatch} \setmainlanguage{french} \xapptocmd\ttfamily{\XeTeXinterchartokenstate=0 }{}{} ...

4

I can reproduce the problem, if the white space before \end{luacode} is a tabulator character. Environment luacode is a special environment, because it changes category codes to read its contents in a more verbatim way. Therefore the end detection is not done by the usual macro expansion, but by searching for the string \end{luacode} at the start of a new ...

Top 50 recent answers are included