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.
I remember the time I did not know st existed: I used mlterm (which deals with even worse than rendering glyphs: asian/indian/thai/arabic/etc input methods). If I recall properly, its config file allows to map style(bold|non-bold)/unicode ranges to a specific font (fontconfig naming). I did that to display asian glyphs in lynx and ncurses links. Rendering/layout-ing correctly fonts from an international point of view is a huge task, and only _one_ software component does that: harfbuzz, a massive c++ pile of ... Could add a table in st config header to do so, but with x11 font naming. Terminals require only bold and/or non-bold versions of a font if I am correct. I don't recall a terminfo application that could use more styles (italic with vim for syntax coloring and style highlighting?). If I recall again properly, the xserver core font system does map fontconfig fonts into into core x11 fonts naming anyway. For a x11 terminal, that should be fairly enough, but we have to keep in mind that for a suckless wayland terminal (if wayland reaches its goals and becomes really stable in time), the rendering (probably pixmap and freetype) and input management (probably libinput), will have to be dealt by the terminal code itself. I have native x11 on my system only because I play video games and xwayland with vulkan/GL hardware acceleration is far from optimal last time I checked. -- Sylvain
