> On 24 Sep 2018, at 21:14, Roberto E. Vargas Caballero <k...@shike2.com> wrote: > > On Mon, Sep 24, 2018 at 09:35:11AM +0200, Hiltjo Posthuma wrote: >>> I don't think we should throw out support for a feature that more than a >>> billion >>> people on the planet rely on. That doesn't mean that we can't rethink how we >>> go about supporting that feature though. > > Of course no, I am not talking about that. Only saying that freetype was a > really > bad idea and we should try to search something different.
I think fontconfig is to blame here. It’s what st is using to find fallbacks. It’s just that we don’t want such highly sophisticated fallback mechanism. We all love simple infallible code, so that we can always blame users. ;) (Note that we still need fontconfig for loading and configuring fonts. It still makes our lives easier.) Also, I believe freetype is essential. st has one visual component and that’s text. st should render it good. At least that’s what people will consider suck-less.
