diff options
Diffstat (limited to 'doc/context/sources/general')
-rw-r--r-- | doc/context/sources/general/manuals/luametatex/luametatex-introduction.tex | 18 | ||||
-rw-r--r-- | doc/context/sources/general/manuals/luatex/luatex-fonts.tex | 6 |
2 files changed, 24 insertions, 0 deletions
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-introduction.tex b/doc/context/sources/general/manuals/luametatex/luametatex-introduction.tex index b16b4aaf4..6081be4f3 100644 --- a/doc/context/sources/general/manuals/luametatex/luametatex-introduction.tex +++ b/doc/context/sources/general/manuals/luametatex/luametatex-introduction.tex @@ -104,3 +104,21 @@ developers and users. \stopchapter \stopcomponent + +% I'm not that strict with incrementing numbers, but let's occasionally bump +% the number. Once we're stable it might happen more systematically. For sure +% I don't want to end up with these redicoulous 0.99999999 kind of numbers. +% +% We started with 2.00.0 and kept that number till November 2019, after Alan +% Braslau and I did the initial beta release at April 1, 2019. After more than +% a year working on the code base after the \CONTEXT\ 2019 meeting a state was +% reached where nothing fundamental got added for a while. When \LUATEX\ needs +% a patch, I check the \LUAMETATEX\ code base as the same patch might be needed +% there. On the other hand, we don't need a strict compatibility, so some +% patched in \LUATEX\ are not applied here. +% +% In November 2019 I started wondering if we should bump the number, just for +% the sake of showing that there's still some progress. So I decided to bump to +% 2.01.0 then. Just as a reminder for myself: it was the day when I watched +% Jacob Collier perform Lua (feat. MARO) live on YouTube (of course that is not +% about the language at all, but still a nice coincidence). diff --git a/doc/context/sources/general/manuals/luatex/luatex-fonts.tex b/doc/context/sources/general/manuals/luatex/luatex-fonts.tex index d49c63afe..e5b6e1cb2 100644 --- a/doc/context/sources/general/manuals/luatex/luatex-fonts.tex +++ b/doc/context/sources/general/manuals/luatex/luatex-fonts.tex @@ -43,6 +43,7 @@ the table are as follows: complete control to the loader. \NC \NR \NC \type{fullname} \NC no \NC no \NC yes \NC string \NC output font name, used as a fallback in the \PDF\ output if the \type {psname} is not set \NC \NR +\NC \type{subfont} \NC no \NC no \NC yes \NC number \NC default: 0, index in (\type {ttc}) font with multiple fonts \NC \NR \NC \type{header} \NC yes \NC no \NC no \NC string \NC header comments, if any \NC \NR \NC \type{hyphenchar} \NC no \NC no \NC yes \NC number \NC default: \TEX's \prm {hyphenchar} \NC \NR \NC \type{parameters} \NC no \NC yes \NC yes \NC hash \NC default: 7 parameters, all zero \NC \NR @@ -105,6 +106,11 @@ font in \type {font.fonts}. It is the actual expansion factor (a value between \type {-shrink} and \type {stretch}, with step \type {step}) of a font that was automatically generated by the font expansion algorithm. +The \type {subfont} parameter can be used to specify the subfont in a \type {ttc} +font. When given, it is used instead of the \type {psname} and \type {fullname} +combination. The first subfont has number~1. A zero value signals using the names +as lookup. + Because we store the actual state of expansion with each glyph and don't have special font instances, we can change some font related parameters before lines are constructed, like: |