Re: [ft-devel] new CFF engine

2013-05-03 Thread Ross Lagerwall
On Thu, May 02, 2013 at 11:50:41PM +0200, Werner LEMBERG wrote: Basically, I took the following steps: $ git status # On branch master nothing to commit, working directory clean $ git rev-parse HEAD 9bf75e08199794c4a5fcefcbfe71b5d39f42e46d $ make devel make $ cd

Re: [ft-devel] new CFF engine

2013-05-03 Thread Nikolaus Waxweiler
Hello Werner, do I understand this correctly: 1. The new engine only works for .otf fonts with included hints and does nothing for .ttfs 2. Setting the new engine as the default like in your mail sets it up automatically for all .otf fonts regardless of hinting settings in fontconfig, meaning

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
Please send me the output of echo '#include limits.h' | cpp -dM -E From your 64bit box, I mean. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
1. The new engine only works for .otf fonts with included hints and does nothing for .ttfs Correct. Similar to TTFs, however, an eternal rule applies: A badly hinted font appears better if displayed without hints (or with auto-hinting). But this is beyond the control of FreeType, entering

Re: [ft-devel] new CFF engine

2013-05-03 Thread octoploid
03.05.2013, 11:48, Werner LEMBERG w...@gnu.org:  After trying on Fedora 19 64bit, Ubuntu 13.04 64bit with gcc 4.7 and  gcc 4.6 with the same result, I eventually tried Ubuntu 13.04 32 bit  and it seemed normal. Maybe it is a 64-bit issue? Yes, I think so.  BTW, does `make devel' really

Re: [ft-devel] new CFF engine

2013-05-03 Thread Ross Lagerwall
On Fri, May 03, 2013 at 11:47:51AM +0200, Werner LEMBERG wrote: After trying on Fedora 19 64bit, Ubuntu 13.04 64bit with gcc 4.7 and gcc 4.6 with the same result, I eventually tried Ubuntu 13.04 32 bit and it seemed normal. Maybe it is a 64-bit issue? Yes, I think so. BTW, does `make

Re: [ft-devel] new CFF engine

2013-05-03 Thread Behdad Esfahbod
On 13-05-03 05:47 AM, Werner LEMBERG wrote: Yes, I think so. BTW, does `make devel' really works out of the box on your 64bit platform? I suppose that you have UINT_MAX = ULONG_MAX = 2^64 - 1 On most 64 bit platforms int is still 32 bit. -- behdad http://behdad.org/

Re: [ft-devel] new CFF engine

2013-05-03 Thread vernon adams
I am also seeing the 'wavy text in ftview', with the Adobe engine + hinting: on. By 'wavy text' i assume we are meaning that some stems are not snapping to the xheight, baseline or capheight, but +1 or -1 pixel from those lines. Kubuntu 13.04 64bit. I would like to test this further, so i have

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
I am also seeing the 'wavy text in ftview', with the Adobe engine + hinting: on. By 'wavy text' i assume we are meaning that some stems are not snapping to the xheight, baseline or capheight, but +1 or -1 pixel from those lines. Kubuntu 13.04 64bit. Yep. This is a 64bit issue; I'm already

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
I've build freetype2 and freetype2-demos with clang's -fsanitize=undefined. Here's what I get when run ftview on an otf font: ttcmap.c:908:18: runtime error: left shift of negative value -1 [...] Thanks. clang is *very* picky :-) Virtually all compilers do the right thing for left

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
Yes, make devel appears to work except for the wavy text. Attached is the output of that command. Thanks. So `int' is 32bit. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] new CFF engine

2013-05-03 Thread octoploid
03.05.2013, 16:23, Werner LEMBERG w...@gnu.org:  I've build freetype2 and freetype2-demos with clang's  -fsanitize=undefined. Here's what I get when run ftview on an otf  font:    ttcmap.c:908:18: runtime error: left shift of negative value -1    [...] Thanks.  clang is *very* picky :-)

Re: [ft-devel] new CFF engine

2013-05-03 Thread Nikolaus Waxweiler
Thanks for the clarification :) Say, are there parts or tricks in the new engine that could be carried over to .ttf rendering or the auto-hinter? I would love to see improvements to typeface fidelity with hintslight :) Regards, Nikolaus ___

Re: [ft-devel] new CFF engine

2013-05-03 Thread Werner LEMBERG
Thanks for the clarification :) Say, are there parts or tricks in the new engine that could be carried over to .ttf rendering or the auto-hinter? I would love to see improvements to typeface fidelity with hintslight :) Well, stem thickening at small sizes is already available in the

Re: [ft-devel] new CFF engine

2013-05-03 Thread James Cloos
o == octoploid octopl...@yandex.com writes: o One issue that I've noticed is that turning hinting on o and using the new engine results in bad rendering (wave- o like) with many fonts. o See the attached screenshot (Minion font) as an example. That screenshot duplicates what I saw. -JimC --

Re: [ft-devel] new CFF engine

2013-05-03 Thread James Cloos
o == octoploid octopl...@yandex.com writes: o Compiler is gcc-4.8. I also used 4.8. -JimC -- James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6 ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] new CFF engine

2013-05-03 Thread James Cloos
WL == Werner LEMBERG w...@gnu.org writes: WL Thanks. So `int' is 32bit. The only system I'm aware of where int was 64 bits was alpha. (Cray's first alpha systems went so far as to have sizeof(char)==sizeof(int)== sizeof(long)==sizeof(int64_t)==1.) Everyone else, as far as I remember, kept

Re: [ft-devel] ft2build.h being regenerated each time.

2013-05-03 Thread Samuel Williams
On 25 April 2013 19:13, Antoine Leca antoine-freet...@leca-marti.orgwrote: Samuel Williams wrote: however other tasks (like hacking with Freetype being one subcomponent which happens to be hacked on; or having Freetype being build by various toolchains) might plainly break if you do that.