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


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


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


8

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



Top 50 recent answers are included