Tag Info

New answers tagged


I don't know how is this feature implemented in the font, but I guess that Luaotfload is missing support for it. The following code is just quick fix for this issue, it should be fixed in Luaotfload ideally. The full code follows, some explanation is provided bellow: \documentclass{article} \usepackage{fontspec} \usepackage{luacode} \begin{luacode*} local ...


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!! ...


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 ...


If you compile with pdflatex you can do this: \documentclass{article} \usepackage{Alegreya} \input glyphtounicode \pdfgentounicode=1 \pdfglyphtounicode{fj}{0066 006A}% f j \begin{document} fb ffb ff fh ffh fi ffi fj ffj fk ffk fl ffl ft fft \end{document}


Just for the record: None of the above worked for me, but this thread:http://www.latex-community.org/forum/viewtopic.php?f=5&t=953 Precisely these lines: \usepackage{microtype} \DisableLigatures[f]{encoding=T1} before the \usepackage[T1]{fontenc} line. If all else fails this can be a quick-and-dirty solution. Take care, B


With the advent of MacTeX2014 and continuing in MacTeX2015 -- and likely to persist into the indefinite future :-( -- Lua(La)TeX can no longer directly access certain font features, such as ligatures, if the font is a system font whose ligature-related properties are AAT-encoded and not OpenType-encoded. Hoefler Text, Didot, and Baskerville are three such ...


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 ...

Top 50 recent answers are included