Tag Info

Hot answers tagged

8

This is an issue introduced in v2.6a to try to improve font coverage for some package combinations. For the present, use \ExplSyntaxOn \AtBeginDocument { \cs_undefine:N \c__siunitx_micro_int \int_const:Nn \c__siunitx_micro_int { "000B5 } } \ExplSyntaxOff A fix will be sent to CTAN today.


6

The command \' becomes \EU1-cmd\' \EU1\' and then \EU1-cmd checks if the combination \\EU1\'-. is defined; the control sequence has \EU1\'-. as name and can be checked by \expandafter\show\csname\string\EU1\string\'-.\endcsname which gives > \\EU1\'-.=macro: ->\TIPAaccent {\textdotacute }. Now the problem follows, because \TIPAaccent wants two ...


5

I'm not certain this is the right way to do it but the following seems to work for me, with very minimal testing. Caveat emptor... \documentclass{article} \usepackage[T1]{fontenc} \usepackage{fontspec} \makeatletter \DeclareRobustCommand\ttfamily{% \not@math@alphabet\ttfamily\mathtt \fontencoding{T1}\fontfamily\ttdefault\selectfont} \makeatother ...


5

You get the same error if you try to use >{\fontspec...} directly in the tabular. It is not a good idea to set up a font in this place (apart from the error, fontspec would have to do it again in every cell). Setup the fonts first and then use the normal font commands instead: \documentclass[12pt, a4paper]{article} \usepackage{fontspec} ...


5

You can access this glyph by setting the Alternate option to 0 (zero): \documentclass{article} \usepackage{fontspec} \setmainfont[Path = <path>, Alternate = 0]{WATERSTITLINGPRO-RG} \begin{document} R \end{document} (<path>is where I specify the folder to which I downloaded your font ... ) How did I know? Well, FontForge tells me that the ...


4

Letter spacing can't work across font changes. You have to emulate it with an explicit kern. Since the font is at 12pt, LetterSpacing=40 corresponds to adding a 4.8pt kern between letters. \documentclass[12pt]{article} \usepackage{fontspec} \setmainfont[LetterSpace=40]{EB Garamond} \begin{document} % No swashes \emph{ANAGRAMME} % Two swashes ...


4

If fontspec is unable to find the bold font associated to a medium series font, uou can use the normal options also with \newfontfamily: \newfontfamily{\monobt}{Monospace821BT}[ BoldFont={Monospace821BTBold} ] and then {\monobt\textbf{This is bold}} should work. Notice that the options should go before the font name with older versions of fontspec.


3

To enable the TeX-Shortcuts, setting the fonts should look like this: \usepackage{fontspec} \defaultfontfeatures{Ligatures=TeX} \setmainfont{Linux Libertine} To your preamble.


3

An acceptable workaround, which still let's you use \textsc without changing it, it defines a similar command \work which does have the desired spacing. I think that there's absolutely no reason to desire this spacing: letters overlap! They need room to breathe… \documentclass{scrartcl} \usepackage{blindtext} \usepackage{fontspec} \setmainfont{Latin ...


3

If you inspect your font files in Windows Explorer, you will indeed see that the fonts are called CMU Bright Medium and CMU Bright Medium Oblique. Since fontspec can't find those fonts, it means that those names are wrong. If you look at the font name in FontForge, for example, you can see that the actual font name of CMU Bright Medium is CMU Bright ...


2

The problem was, that I specified the font by filename, like this: \setmainfont[% UprightFont = *-regular, BoldFont = *-bold, ItalicFont = *-italic, BoldItalicFont = lmroman10-bolditalic.otf, SmallCapsFont = lmromancaps10-regular.otf, SmallCapsFeatures = {Scale=MatchUppercase}, SlantedFont = ...


2

You can't use kpfonts with fontspec and unicode-math. These fonts exist only in Type1 format for pdflatex.


1

Please Note: Robert and Sverre pointed out to me that my original reduction did not make any sense (and rightly so). Here's another swing at an mwe. I believe this one is proper. Here's a minimal document that triggers the issue for me. \documentclass[a4paper]{article} \usepackage{microtype} \usepackage{amsthm} \newtheorem{proposition}{Proposition} ...


1

So I did the following and the problem seems to be solved!!! 1- clean LuaLaTeX font cache (LuaTeX cannot find existing font): cd .texmf-var/luatex-cache/generic/fonts/otf/ rm * 2- update Lua font name data base (Arch Linux: fontspec does not find system fonts): luaotfload-tool --update 3- run: sudo texhash et voilà!



Only top voted, non community-wiki answers of a minimum length are eligible