Will Robertson

I *think* I see what is going on here. For both XeTeX and LuaTeX, `Ligatures=TeX` is a "fake" approach to loading the font in a different way to achieve a...

Actually if what I said above was true, you'd expect to get the same results from something like this \newfontfamily\1{Latin Modern Roman}[WordSpace = {2, 0.25, 0.25}] \newfontfamily\2{Latin Modern Roman}[WordSpace =...

Thanks for the comments! I agree with you, definitely. It’s been a LONG TIME since this code was written — I like your suggest of having relative weights of \fontdimen2....

Thanks, I’ll put something together… Hopefully sooner rather than later but never any promises `:)`

Thanks for spotting this. The XeTeX on the latest version of macOS seems to have problems with the AAT fonts that are shipped with the OS. I'm not sure if...

@RuixiZhang42 — yes, that's right, the new default in LaTeX2e will be `b`. Sorry for my silence on this issue... I will be adding bx↔︎b substitution some time soon...

Since we're talking about both XeTeX and LuaTeX for now, let's restrict our discussion to only the fontspec side of things -- unfortunately automatically finding or using varieties of bold...

Sorry to think out loud here. Here're my current thoughts. - `\addfontfeatures{...}` could be renamed to `\fontspec*[...]` or `\fontspec*{...}` - A new option `[NFSS={family}{series}{shape}]` could allow something like: ``` \setmainfont[]{foo}...

Sorry for the extremely slow reply — and thank you so much for the detailed work you've done here! I hope to address many of these in the not-too-distant future.

I mostly limit fontspec’s interface to loading of font features. So yes, I can definitely make `opbd` etc available with a “friendly” name, but I would rely on others to...