Tag Info

New answers tagged

1

Here's how to do it (with the help of answers 1 and 2): Obtain Adobe's AFDKO font tools and install them. Put the font file into an empty directory. Run tx -pdf -1 YOUR_FONT.otf > YOUR_FONT.pdf to map the glyphs of font. Open YOUR_FONT.pdf, search for the wanted glyph and its glyph tag (the upper left number, we will name it GLYPH_TAG). Create a dummy ...


9

You can use the LetterSpace option in fontspec. It preserves kerning as you can see if you compare it with the output of Renderer=basic: \documentclass{article} \usepackage{microtype} \usepackage{fontspec} \setmainfont{LinLibertine_R}[% Extension = .otf, SmallCapsFeatures = {% LetterSpace = 10, Letters = SmallCaps}] ...


5

There is no general answer to this question, nor could there be. It’s not just that some designers misuse calt and other features, or disagree in their interpretation of the specification. Even if they all used features as they were meant to be used, fonts would still exhibit different behaviors. Imagine that everyone agreed to use ss01 for Q, and ss02 for ...


1

OverLeaf's TeX Live installation is the root of the problem. It seems that OverLeaf is using XeLaTeX by default and, since their installation of TeX Live is not current, this features a bug which causes the problem. Switching to LuaLaTeX resolves the issue: this can be done by setting the engine explicitly in the Project options. I've confirmed this on ...


2

You are using \bf that has been deprecated for 20 years and placing \selectfont in the wrong place. Also \fontsize{10}{0} is wrong. \documentclass[12pt]{article} \usepackage{threeparttable} \usepackage{caption} \usepackage{fontspec} \setmainfont{Times New Roman} \setsansfont{Arial} \DeclareCaptionFormat{mytabformat}{% ...


10

The problem with this font -- as far as its ligatures are concerned -- is that the ligature names in the internal font table are, shall we say, utterly non-standard. For instance, instead of going with standard names such as f_f and f_f_i for the ligatures, a search with the FontForge app reveals that the font uses the names Omega and approxequal. No joke!! ...


4

It turns out that your font is freely available. As I suspected, the font doesn't have OpenType features (screen capture from FontForge): What's worse, the font is not a Unicode font. It has replaced various code points with ligatures. If you want to, you can access the ligatures by typing the characters that occupy those slots according to the Unicode ...


8

I assume you're using LuaTeX. If so, one can set up a macro called \Setxheight and use it with fontspec's Scale option. Note that the macro uses Lua's division routine instead of TeX's own built-in routine since the scaling factor will likely not be integer-valued. % !TEX TS-program = lualatex \documentclass{article} \usepackage{fontspec} %% x-height of ...


3

I have no problem with lualatex from up-to-date TL 2015 (I used "..." for some Japanese characters which the editor of SX doesn't allow.) \documentclass[a4paper]{article} \usepackage{fontspec} \setmonofont[ BoldFont = Source Han Code JP B, Scale=0.9 ]{Source Han Code JP L} \setmainfont{Source Han Sans Regular} \begin{document} This is Source Han ...


5

You shouldn't use the package with lualatex and xelatex. It uses the wrong font encodings for this engines. If I got it right from your various questions your problem is that you want to set the slanted font and that this disturbs the small caps. This is imho a bug in fontspec and I made a report: https://github.com/wspr/fontspec/issues/209. You can get ...


2

I assume you're using LuaLaTeX. An advantage of running \usepackage{erewhon} is that it lets you generate not only "regular" (i.e., upright) smallcaps but also bold smallcaps, slanted smallcaps, and bold-slanted smallcaps. (I'll let others weigh in on the subject of whether it's in fact a good idea to have these additional font shape and weight ...


1

Thanks to @AkiraKakuto, the problem was that MikTex was still using old versions of the fontawesome package from the AppData/Roaming folder despite the package was updated using package manager and the "update app" within MiKTex. The problem is solved by deleting the fontawesome folder within AppData/Roaming/MiKtTex/'version'.


7

\documentclass{article} \usepackage{fontspec} \setmainfont{Minion Pro} \newfontface\Swash{MinionPro-It}[Contextuals=Swash] \newcommand\textsw[1]{{\Swash#1}} \begin{document} \textsw{Qu’est que c’est?} \emph{Qu’est que c’est?} \textsw{Zygoma} \emph{Zygoma} \end{document}


4

Imho it is a problem of the implementation in polyglossia: the space is lost inside some boxes: \documentclass{article} \usepackage{fontspec, polyglossia} \setdefaultlanguage{french} \begin{document} \begin{tabular}{l} \today{} here: should have been a space before those two dots! \end{tabular} \mbox{\today{} here: should have been a space ...


3

After some more investigation I think the answer to the question "whose bug is it?" is that the problem is in xetex. Somehow the mu value of the scriptscriptsize font is leaking out. I made a bug report in the xetex bug tracker with an example using neither unicode-math nor siunitx. https://sourceforge.net/p/xetex/bugs/117/


2

It is rather unclear what you actually want. But here two suggestions: You could still use SourceSerifPro as main font and fake a slanted font: \documentclass[]{scrartcl} \usepackage{fontspec} \defaultfontfeatures{Ligatures=TeX} \setmainfont{SourceSerifPro}[ ItalicFont = SourceSerifPro, ItalicFeatures={FakeSlant=0.2}] \begin{document} This is a ...


5

The source of the problem The problem is caused by the fact the Junicode font has true proportional old style numbers, whereas some other fonts have, both, fixed width old style numbers and proportional old style numbers. The linguex package sets an internal length that is a multiple of the smallest width digit in the current font. The smallest width ...


10

With kind help from @cfr, you've established that: The font does contain ligature glyphs. fontspec can't make use of AAT ligature information even if it's available. The font omits OpenType feature data necessary for automatic ligature support. So what can you do? You can either add the missing mapping data to the font, or create an external OpenType ...


4

This works in both xelatex and lualatex and sets the document in Pagella for me: \documentclass[11 pt, a4paper]{article} \usepackage[T1]{fontenc} \usepackage{fontspec} \ExplSyntaxOn \NewDocumentCommand{\onlywarniffontnotfound}{} { \font_suppress_not_found_error: \msg_redirect_name:nnn {fontspec}{font-not-found}{warning} } \ExplSyntaxOff ...



Top 50 recent answers are included