Hello, 1 bug report + 3 questions: ___ # Bug report: \definefallbackfamily ignoring font features ```tex \definefallbackfamily[mainface][rm][Noto Serif][preset=range:greek, sl={style:tf, features:slanted}] \definefontfamily[mainface][rm][latinmodernroman] \setupbodyfont[mainface] \starttext \sl something αβγ \stoptext ``` The three greek letters are slanted when compiled with older ConTeXt LMTX (before Oct.19, 2024), but they remain upright under the latest version. ___ # Question: ad-hoc font features I tried to specify ad-hoc font features (see below) in `\definefontfamily` like slant+bold, without naming the feature with `\definefontfeature` since they're not supposed to be reused. But the resulting fonts are always thicker than expected. Then I found that, even with empty effects, `features:{effect={}}` itself makes the font ultra bold. ```tex \definefontfamily[mainface][rm][Noto Serif][sl={style:tf, features:{effect={}}}] \setupbodyfont[mainface] \starttext \sl something αβγ \stoptext ``` Is this a bug, or is there any justification behind it? ___ # Question: feature inheritance of `\definefontfamily` When I customize fonts with \definefontfamily, e.g: ```tex % some other customization with \definefallbackfamily ... \definefontfamily[mainface][rm][latinmodernroman] \definefontfamily[mainface][tt][latinmodernmono] \setupbodyfont[mainface] \starttext \tt\sl something \stoptext ``` the slanted monospace becomes some kind of italic. To recover the default behavior, the slant variant must be explicitly specified: ```tex % some other customization with \definefallbackfamily ... \definefontfamily[mainface][rm][latinmodernroman] \definefontfamily[mainface][tt][latinmodernmono][sl=lmmonoslant10regular] \setupbodyfont[mainface] \starttext \tt\sl something \stoptext ``` But it's unproductive to copy-paste full specification (slanted, bold, ...) of the builtin latin modern. Is there any way to avoid this by somehow inheriting the default specification? ___ # Question: ConTeXt LMTX version control Where can one find older releases of ConTeXt LMTX when encountering problems like the bug above? https://github.com/contextgarden/context looks promising, but it doesn't provide release artifacts, nor build instructions. I could help add a workflow for automated release to it if someone kindly provides a built instruction. ___ Best regards, Sylvain