Re: [ft-devel] [GSoC] [Doubt] CSS Sprite animation

> I've been trying a lot to change the CSS keyframe animation values > using pure javascript. I wasn't able to find any solution(s). > > This is what I want to do. > > @-webkit-keyframes play { > 100% { background-position: -480px; } > } [You also want to use the CSS3 keyword `@keyframes' so

Re: [ft-devel] problems with synthetic cmaps

> Please, don't add more magic to FreeType. Just remove old magic... It rather looks like pdfium now, much like skia before, is caught hacking around Freetype API. ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] problems with synthetic cmaps

Please, don't add more magic to FreeType. Just remove old magic... On Wed, Aug 16, 2017 at 7:11 AM, Werner LEMBERG wrote: > > Alexei, > > > there is a bug report > > https://bugs.chromium.org/p/chromium/issues/detail?id=754574 > > that directly affects synthesized cmaps. The

[ft-devel] [GSoC] [Doubt] CSS Sprite animation

I've been trying a lot to change the CSS keyframe animation values using pure javascript. I wasn't able to find any solution(s). This is what I want to do. @-webkit-keyframes play { 100% { background-position: -480px; } } Lets say above block is from a CSS file. I want to be able to change

Re: [ft-devel] problems with synthetic cmaps

That's interesting, you mean haunt us through official font packages? Which ones? ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel

Re: [ft-devel] problems with synthetic cmaps

On Wed, Aug 16, 2017 at 9:22 PM, Alexei Podtelezhnikov wrote: > On Wed, Aug 16, 2017 at 2:06 PM, Werner LEMBERG wrote: >> > (1) Don't synthesize a Unicode cmap map for symbol OpenType fonts > (i.e., fonts having a (3,0) cmap). > > (2) Discard

Re: [ft-devel] problems with synthetic cmaps

On Wed, Aug 16, 2017 at 2:06 PM, Werner LEMBERG wrote: > (1) Don't synthesize a Unicode cmap map for symbol OpenType fonts (i.e., fonts having a (3,0) cmap). (2) Discard a synthesized Unicode cmap if the number of mappings is much lower than the

Re: [ft-devel] problems with synthetic cmaps

>>> (1) Don't synthesize a Unicode cmap map for symbol OpenType fonts >>> (i.e., fonts having a (3,0) cmap). >>> >>> (2) Discard a synthesized Unicode cmap if the number of mappings >>> is much lower than the mappings in another cmap of the font. > > Since Wingdings and Webdings are in

Re: [ft-devel] Font Validator 2.1 binaries.

Congrats on getting this release out there :) On 15 August 2017 at 16:52, Hin-Tak Leung wrote: > Finally got round to build the binary - just get > FontVal-2.1.0-py-bin-net4.zip from > https://sourceforge.net/projects/hp-pxl-jetready/files/Microsoft%20Font% >

Re: [ft-devel] problems with synthetic cmaps

>> >> (1) Don't synthesize a Unicode cmap map for symbol OpenType fonts >> (i.e., fonts having a (3,0) cmap). >> >> (2) Discard a synthesized Unicode cmap if the number of mappings is >> much lower than the mappings in another cmap of the font. Since Wingdings and Webdings are in

Re: [ft-devel] problems with synthetic cmaps

On Wed, Aug 16, 2017 at 10:11 AM, Werner LEMBERG wrote: > > Alexei, > > > there is a bug report > > https://bugs.chromium.org/p/chromium/issues/detail?id=754574 > > that directly affects synthesized cmaps. The corollary: It is a bad > idea to synthesize a Unicode cmap in FreeType

[ft-devel] problems with synthetic cmaps

Alexei, there is a bug report https://bugs.chromium.org/p/chromium/issues/detail?id=754574 that directly affects synthesized cmaps. The corollary: It is a bad idea to synthesize a Unicode cmap in FreeType if the number of `hits' is too low. For symbol fonts like `wingding.ttf' (which

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

> Ewald, are you using freetype2-demos/bin/* wrapper scripts? They > supposed to LD_PRELOAD from the neighboring freetype2/objs/.libs > folder. Even standard (not devel) build works for me like this. Hm... when I used those, callgrind seemed to be unable to capture the process, grabbing

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

> By the way, there is this outstanding bug > https://savannah.nongnu.org/bugs/?43248. Perhaps you can profile > the engine and post the details. Uh, oh, he is doing this partly for this very bug report – you recommended to him to have a look :-) Werner

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

> git clean -fdx > git reset --hard # or manually check for missing files/interfering changes > make devel > make Thanks, it works now. I've managed to reproduce the slow load times, turns out I had forgot to compile CFF old engine and it was using the new engine regardless(whoops!).

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

>> In fact, it seems like the demos >> are linking to my system-provided libfreetype instead of the git >> devel one, hence no debug information. I'm trying to fix that right >> now. > > Are you doing a `developer's build' (i.e., `make devel; make' in > `freetype2', then a simple `make' in

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

>> git clean -fdx (Use with caution! Check before with `git clean -ndx) >> make devel >> make > > I get: > config.mk:25: builds/unix/unix-def.mk: No such file or directory > config.mk:26: builds/unix/unix-cc.mk: No such file or directory > make: execvp: ./include/freetype/freetype.h:

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

> git clean -fdx (Use with caution! Check before with `git clean -ndx) > make devel > make I get: config.mk:25: builds/unix/unix-def.mk: No such file or directory config.mk:26: builds/unix/unix-cc.mk: No such file or directory make: execvp: ./include/freetype/freetype.h: Permission

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

>> Are you doing a `developer's build' (i.e., `make devel; make' in >> `freetype2', then a simple `make' in `freetype2-demos')? This >> should create statically linked binaries quite easily. > > Strange... make insists that there is nothing to be done for > `devel'. What am I missing? git

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

> Are you doing a `developer's build' (i.e., `make devel; make' in > `freetype2', then a simple `make' in `freetype2-demos')? This should > create statically linked binaries quite easily. Strange... make insists that there is nothing to be done for `devel'. What am I missing? Ewald