Re: [dev] freetype2/fc pain

2018-09-25 Thread sylvain . bertrand
Hi again, I did refresh my knowledge on unicode/font stuff, and yes, st will be screwed: An unicode string has 4 canonical normalizations. But only one (NFD) seems to be futur proof regarding what features will be supported by font files (opentype(microsoft tm)/open font format). Ofc, this is

Re: [dev] freetype2/fc pain

2018-09-25 Thread Roberto E. Vargas Caballero
On Mon, Sep 24, 2018 at 10:26:52PM +0600, Eon S. Jeon wrote: > 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. ;) >

Re: [dev] tabbed should not touch the child window until it has the _XEMBED_INFO property

2018-09-25 Thread Quentin Rameau
On Tue, 25 Sep 2018 11:21:27 +0200 Dimitrios Semitsoglou-Tsiapos wrote: > Hello everyone, Hello Dimitrios, > I have been hunting a bug where zathura windows do not get rendered > inside tabbed. It seems that the issue boils down to both Gtk+ and tabbed. And X11 embedding alltogether, I think.

Re: [dev] tabbed should not touch the child window until it has the _XEMBED_INFO property

2018-09-25 Thread Dimitrios Semitsoglou-Tsiapos
On 25/09/18 11:38, Quentin Rameau wrote: > On Tue, 25 Sep 2018 11:21:27 +0200 > Dimitrios Semitsoglou-Tsiapos wrote: > >> Hello everyone, > > Hello Dimitrios, > >> I have been hunting a bug where zathura windows do not get rendered >> inside tabbed. It seems that the issue boils down to both

[dev] tabbed should not touch the child window until it has the _XEMBED_INFO property

2018-09-25 Thread Dimitrios Semitsoglou-Tsiapos
Hello everyone, I have been hunting a bug where zathura windows do not get rendered inside tabbed. It seems that the issue boils down to both Gtk+ and tabbed. To avoid repeating too much content here, you can see the list of bugs I have opened so far linked here [1]. Most relevant to you should

Re: [dev] freetype2/fc pain

2018-09-25 Thread Eon S. Jeon
> On 25 Sep 2018, at 14:10, Roberto E. Vargas Caballero wrote: > >> On Mon, Sep 24, 2018 at 10:26:52PM +0600, Eon S. Jeon wrote: >> 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

Re: [dev] freetype2/fc pain

2018-09-25 Thread Laslo Hunhold
On Tue, 25 Sep 2018 21:25:12 + sylvain.bertr...@gmail.com wrote: Dear Sylvain, > An unicode string has 4 canonical normalizations. But only one (NFD) > seems to be futur proof regarding what features will be supported by > font files (opentype(microsoft tm)/open font format). this is true,

Re: [dev] freetype2/fc pain

2018-09-25 Thread AR Garbe
On 25 September 2018 at 16:32, Laslo Hunhold wrote: > On Tue, 25 Sep 2018 16:28:22 -0700 > AR Garbe wrote: >> This is something I was considering, however it looks like the water >> of the babie's bathtub is poisoned with freetype2/fc bacteria. I don't >> wanna introduce abstractions that might

Re: [dev] freetype2/fc pain

2018-09-25 Thread sylvain . bertrand
On Tue, Sep 25, 2018 at 04:28:22PM -0700, AR Garbe wrote: > This is something I was considering, however it looks like the water > of the babie's bathtub is poisoned with freetype2/fc bacteria. I don't > wanna introduce abstractions that might be premature, hence I suggest > to fully revert back

Re: [dev] freetype2/fc pain

2018-09-25 Thread AR Garbe
Hi Silvain, On 25 September 2018 at 14:25, wrote: > The suckless futur proof solution: it is over, st goes 7bits ascii only with > it's own bitmap fonts... non english-only terminal users will just trash it. Sounds like a better plan for longevity. > ... or a suckless futur proof unicode/font

Re: [dev] freetype2/fc pain

2018-09-25 Thread AR Garbe
Hi Laslo, On 25 September 2018 at 16:06, Laslo Hunhold wrote: > On Tue, 25 Sep 2018 21:25:12 + > sylvain.bertr...@gmail.com wrote: >struct sfl { ... }; > >sfl_init(struct sfl *s, char **files, size_t nfiles); >sfl_draw(...); >sfl_free(struct sfl *s); This is something I was

Re: [dev] freetype2/fc pain

2018-09-25 Thread Laslo Hunhold
On Tue, 25 Sep 2018 16:28:22 -0700 AR Garbe wrote: Dear Anselm, > This is something I was considering, however it looks like the water > of the babie's bathtub is poisoned with freetype2/fc bacteria. I don't > wanna introduce abstractions that might be premature, hence I suggest > to fully

Re: [dev] freetype2/fc pain

2018-09-25 Thread sylvain . bertrand
On Wed, Sep 26, 2018 at 01:06:52AM +0200, Laslo Hunhold wrote: > On Tue, 25 Sep 2018 21:25:12 + > sylvain.bertr...@gmail.com wrote: > > - a full xml smile/svg vector renderer (like librsvg/expat for > > the svg part) > > No, forget about SVG fonts. Nobody sane would think about

Re: [dev] freetype2/fc pain

2018-09-25 Thread Eon S. Jeon
> On 25 Sep 2018, at 00:12, Manu Raster wrote: > > "Eon S. Jeon" writes: > Hiltjo Posthuma writes: > I agree its useful. (Complex) fall-back font support has been on my mind also. An idea could be of instead of supporting fallback fonts we could write some

Re: [dev] freetype2/fc pain

2018-09-25 Thread sylvain . bertrand
On Tue, Sep 25, 2018 at 08:17:51PM +0600, Eon S. Jeon wrote: > I use all of CJK and am not the only one who use non-Latin language in > terminal. In the past, I too assumed I would use only English on terminal, > but I cannot control what other people send to me. It is really stupid if I > have to