Re: [ft-devel] ftdump functionality in ftinstpect
> This patch adds the basic functionality of ftdump in ftinspect. > More changes/features will be added in subsequent patches. Very nice! Do you plan to work more on ftinspect? This would be great! > Please have a look & suggest the required changes for refinement of > this patch. Some comments. * I think it would be best if all the information is present in a single window. If necessary, there could be tabs to split the contents into smaller chunks. * Don't insert a space before the double colon character (`:') – this is correct for French typography but not for English. * For the charmap info it would be nice if the meaning of the numbers could be shown also, e.g. PID 3 = MS Windows, EID 1 = Unicode BMP, etc., etc. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Rendering issues with xpdf (and other Linux based pdf viewers)
> Btw, been wondering if something could/should be done on freetype > too - while we know where the broken hinting instructions came about > in this case, similar problem can come from a different source too. People can always run the hinter in paranoid mode, rendering a glyph without hinting if an error is returned... Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] Rendering issues with xpdf (and other Linux based pdf viewers)
On Saturday, 6 October 2018, 17:18:08 GMT+8, Werner LEMBERG wrote: >> Uh, oh. It's a regression in ttfautohint – version 1.7 works fine, >> version 1.8 and higher fails. Now fixed in git. > Thanks for all the work! I am glad we get to the bottom of this :-). It explains too why ghostscript fails but mupdf works, from the same-ish group of people - I think mupdf ignores hinting instructions. Btw, been wondering if something could/should be done on freetype too - whIle we know where the broken hinting instructions came about in this case, similar problem can come from a different source too. ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ccache support for `freetype-testing'
> Werner asked me about this a few days ago and since there are a few > people using this repo I thought it is worth mentioning it in the > ft-devel list: I just added `ccache' support to `freetype-testing' > (https://github.com/freetype/freetype2-testing). Thanks for the quick implementation! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
[ft-devel] ccache support for `freetype-testing'
Werner asked me about this a few days ago and since there are a few people using this repo I thought it is worth mentioning it in the ft-devel list: I just added `ccache' support to `freetype-testing' (https://github.com/freetype/freetype2-testing). It can be turned off (default is "on" though) and the option should only appear if `ccache' can be located on the target system. I ran a couple of tests on different machines and different setups but obvs. I cannot test EVERYthing so please let me know if you run into any weird caching issues (spec. when recompiling the thing over-and-over again with different settings) :) Apart from that, have a great Sunday :) ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
