Generally fontspec only expects a name for the font in it's main argument, ll other options are given in a separate optional argument. So all the things you wrote between `{}` need to go between `[]` and you additionally need to provide some name in `{}`. So e.g.
\documentclass{memoir ...
Search found 4 matches
- Sat Nov 06, 2021 10:39 pm
- Forum: Fonts & Character Sets
- Topic: fontspec cannot resolve font
- Replies: 1
- Views: 5141
- Thu Oct 14, 2021 6:25 pm
- Forum: XeTeX
- Topic: ligatures not forming with some fonts with XeLaTeX
- Replies: 4
- Views: 39386
ligatures not forming with some fonts with XeLaTeX
The same problem occurs with the Georgia font which is readily available on Linux.
For Georgia (at least the Georgia version in my system, 5.59) the ligatures you are looking for are defined as "Discretionary Ligatures" and not as "Default Ligatures" in the font file and are therefore disabled ...
For Georgia (at least the Georgia version in my system, 5.59) the ligatures you are looking for are defined as "Discretionary Ligatures" and not as "Default Ligatures" in the font file and are therefore disabled ...
- Thu Apr 25, 2019 9:06 am
- Forum: General
- Topic: Own text rendering
- Replies: 1
- Views: 2064
Own text rendering
Hi,
If you want to customize the word spacing and the justification, you can use Lua(La)TeX: There you can overwrite the `linebreak_filter` callback. This callback replaces the built-in logic for breaking paragraphs into lines. You get a list of nodes, representing the text of the paragraph, passed ...
If you want to customize the word spacing and the justification, you can use Lua(La)TeX: There you can overwrite the `linebreak_filter` callback. This callback replaces the built-in logic for breaking paragraphs into lines. You get a list of nodes, representing the text of the paragraph, passed ...
- Thu Jan 24, 2019 10:06 pm
- Forum: General
- Topic: expl3: don't understand behavior of tl_if_novalue:nTF
- Replies: 1
- Views: 5063
expl3: don't understand behavior of tl_if_novalue:nTF
Actually this is the expected behaviour even if the documentation is a bit misleading:
\tl_if_novalue:nTF tests if the token list is exactly equal to c_novalue_tl , meaning equal to the special token list which is stored inside c_novalue_tl . This is not the same as {c_novalue_tl} , the token list ...
\tl_if_novalue:nTF tests if the token list is exactly equal to c_novalue_tl , meaning equal to the special token list which is stored inside c_novalue_tl . This is not the same as {c_novalue_tl} , the token list ...