Re: [ft-devel] [ftgrid] Display rendered bitmap (new feature).

2016-03-07 Thread Werner LEMBERG
>> Is this the case in the released tool version 2.6.3? I've only messed >> with ftgrid since February 11. > > No idea, I think it's been happening since you first presented it? > I'm running git master. Cycle through the hinting modes, everything > snaps the advance width to the grid, including l

Re: [ft-devel] [ftgrid] Display rendered bitmap (new feature).

2016-03-07 Thread Alexei Podtelezhnikov
Nikolaus, The rounding is done here http://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/src/autofit/afloader.c#n447 Why do you think it is wrong? I tried disabling this rounding if LIGHT which did not change text rendering because bitmaps are placed at pixels, i.e., rounding is done anywa

Re: [ft-devel] [ftgrid] Display rendered bitmap (new feature).

2016-03-07 Thread Nikolaus Waxweiler
Is this the case in the released tool version 2.6.3? I've only messed with ftgrid since February 11. No idea, I think it's been happening since you first presented it? I'm running git master. Cycle through the hinting modes, everything snaps the advance width to the grid, including light AA wh

Re: [ft-devel] [ftgrid] Display rendered bitmap (new feature).

2016-03-07 Thread Alexei Podtelezhnikov
On Mon, Mar 7, 2016 at 10:57 AM, Nikolaus Waxweiler wrote: >> Oh and: Light AA seems to change the advance width when it shouldn't? > > > Ping Alexei :) > > Enabling any kind of hinting seems to snap the advance width to the grid > even it shouldn't. Bug in ftgrid or the lib? Is this the case in

Re: [ft-devel] [ftgrid] Display rendered bitmap (new feature).

2016-03-07 Thread Nikolaus Waxweiler
Oh and: Light AA seems to change the advance width when it shouldn't? Ping Alexei :) Enabling any kind of hinting seems to snap the advance width to the grid even it shouldn't. Bug in ftgrid or the lib? ___ Freetype-devel mailing list Freetype-deve

Re: [ft-devel] compile error with VS2013

2016-03-07 Thread Graham Asher
It's a bold statement, based on a lot of commercial production experience with both IDEs, but not a hyperbolic one. Sure, FreeType can be built with VS2013, but why bother now VS2015 is out? VS2013 wasn't a very long-lived version. If an old version should be supported it would be better to mai

Re: [ft-devel] compile error with VS2013

2016-03-07 Thread John Tytgat
On 3/7/2016 11:42 AM, Graham Asher wrote: I don' think it's necessary to support VS2013. It was buggy and incomplete compared to VS2015, which is much better. That's a pretty bold & hyperbolic statement. There is nothing intrinsically wrong with VS2013 Update 5 (or even earlier versions) to

Re: [ft-devel] compile error with VS2013

2016-03-07 Thread Graham Asher
I don' think it's necessary to support VS2013. It was buggy and incomplete compared to VS2015, which is much better. The community edition is free. Therefore I think it would be more productive to check whether the latest build works with VS2015, and fix any problems there first. - Graham On

Re: [ft-devel] compile error with VS2013

2016-03-07 Thread Werner LEMBERG
>There are errors when compiling FreeType 2.6.3 with Visual >Studio 2013, But 2.6.2 is OK. Details, please. We need a log file or something similar. BTW, it would be best if you could try to compile the current git version of FreeType. Werner _

[ft-devel] compile error with VS2013

2016-03-07 Thread 刘伶令
Hi All ! There are errors when compiling FreeType 2.6.3 with Visual Studio 2013, But 2.6.2 is OK.___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel