Re: [ft-devel] Haarmony LCD rendering

2017-08-09 Thread Jan Alexander Steffens
On Wed, Aug 9, 2017 at 5:11 AM Alexei Podtelezhnikov wrote: > What do you think? Great! As it's in master now I've given it a try. Unfortunately, it seems Firefox now cuts off many glyphs on the right side. A lowercase i or l can become almost invisible. On Wed, Aug 9, 2017 at 8:15 AM Markus T

Re: [ft-devel] Haarmony LCD rendering

2017-08-09 Thread Markus Trippelsdorf
On 2017.08.09 at 09:26 +, Jan Alexander Steffens wrote: > On Wed, Aug 9, 2017 at 5:11 AM Alexei Podtelezhnikov > wrote: > > > What do you think? > > > Great! As it's in master now I've given it a try. Unfortunately, it seems > Firefox now cuts off many glyphs on the right side. A lowercase

[ft-devel] more on the preferred setup for `make tests'

2017-08-09 Thread Werner LEMBERG
Kushal, attached is a revised version of your `README' file.[*] I think you still haven't fully grasped how I would like the setup, so I've tried to be quite explicit – in particular, you are still talking about `installing', which I don't want... I now ask you to implement everything according

Re: [ft-devel] Haarmony LCD rendering

2017-08-09 Thread Markus Trippelsdorf
On 2017.08.09 at 12:10 +0200, Werner LEMBERG wrote: > > > Unfortunately, it seems Firefox now cuts off many glyphs on the > > right side. A lowercase i or l can become almost invisible. > > IIRC, this is a bug in Firefox; it relies on a certain glyph buffer > layout that is not covered by the API

Re: [ft-devel] Haarmony LCD rendering

2017-08-09 Thread Werner LEMBERG
> Unfortunately, it seems Firefox now cuts off many glyphs on the > right side. A lowercase i or l can become almost invisible. IIRC, this is a bug in Firefox; it relies on a certain glyph buffer layout that is not covered by the API but (incorrectly) derived from FreeType's internal representati

Re: [ft-devel] more on the preferred setup for `make tests'

2017-08-09 Thread Kushal K S V S
> > I think you > still haven't fully grasped how I would like the setup, so I've tried > to be quite explicit – in particular, you are still talking about > `installing', which I don't want... As per my last commit, I don't think I am 'installing'. dbd3da066e888c77a51bc37426667d29d603d390

Re: [ft-devel] Haarmony LCD rendering

2017-08-09 Thread Alexei Podtelezhnikov
On Wed, Aug 9, 2017 at 6:15 AM, Markus Trippelsdorf wrote: > On 2017.08.09 at 12:10 +0200, Werner LEMBERG wrote: >> >> > Unfortunately, it seems Firefox now cuts off many glyphs on the >> > right side. A lowercase i or l can become almost invisible. >> >> IIRC, this is a bug in Firefox; it relies

Re: [ft-devel] more on the preferred setup for `make tests'

2017-08-09 Thread Werner LEMBERG
>> I think you still haven't fully grasped how I would like the >> setup, so I've tried to be quite explicit – in particular, you are >> still talking about `installing', which I don't want... > > As per my last commit, I don't think I am 'installing'. In your (original) README I find the follow

[ft-devel] Speeding up PNG loading

2017-08-09 Thread Behdad Esfahbod
Hi, I thought I see if I can speed up PNG loading by vectorizing alpha premultiplication, and it actually does give a nice speedup: commit d7d592b0acb25ad8084b1d60459dd40bfd9c3356 (HEAD -> png-faster, github/png-faster) Author: Behdad Esfahbod Date: Tue Aug 8 21:29:25 2017 -0700 Process f

Re: [ft-devel] [GSoC] CID font support, and others

2017-08-09 Thread Ewald Hew
> OK, I'll be finding a way to add this in with minimal clutter to the > code. I'm thinking to add an extra check to the top to skip stuff > other than stem hints first time round, then rewinding on `endchar'. Done. Pushed along with some other minor changes. I've checked this with all the known

Re: [ft-devel] [GSoC] CID font support, and others

2017-08-09 Thread Werner LEMBERG
>> OK, I'll be finding a way to add this in with minimal clutter to >> the code. I'm thinking to add an extra check to the top to skip >> stuff other than stem hints first time round, then rewinding on >> `endchar'. > > Done. Pushed along with some other minor changes. > > I've checked this with a