Will Robertson

> > `{\addfontfeatures{Case=On}\MakeUppercase{[Ca-pitals]}}` does not sound user friendly to me. > > You can always define your own macros. I'd never considered this as an extension for fontspec. I generally...

For my own notes: this needs a way of activating font features "silently", so if the feature is missing there's no warning. Easily done, just not tonight `:)`

@rriemann How do you mean? It hasn't been implemented yet. Are you saying it's no longer needed or that I should get a move on? :) FWIW I think it's...

fontspec uses `*` as a way to abbreviate font names. I didn't think anyone would define a font name using it. I'll keep this open to consider adding a "NoStar"...

I will add something to the doc, but just quickly — fontspec declarations only act on families, so that rules out sf and tt. You'd still want `\setmainfont{cmur} \setsansfont{cmusf} \setmonofont{cmutt}`...

Hmmm. These examples are always tricky as the LaTeX wrappers around the TeX primitives in one sense hide a lot of the detail. I’ll try to develop a plain TeX...

Thanks, looks like you may have stumbled across an edge case. I’ll look into it...

Regarding fonts, is it possible to repeat the test using something like texgyrepagella-regular.otf ? It makes it much easier for me to write standardised tests if the font is in...

I see what you mean here; while `\addfontfeatures` is faster than loading a new font entirely, it probably still does more preliminary processing than it should. Ideally I think we'd...

I guess my first question would be: how can we make it easy to define font families that are variants of one another? I.e., would it help to have something...