Re: [ft-devel] ttfautohint: Milestone reached!
On 06/17/11 23:53, Werner LEMBERG wrote: If I understand you correctly, there currently isn't a possibility to get such info from HarfBuzz easily (if at all)? No, currently there isn't. behdad ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
Finally, there is the problem of glyphs which can't be addressed with a cmap directly, like small caps which are activated by an OpenType feature. Similar to FreeType's autohinter, such glyphs don't get any special consideration and are treated by the default hinting module (in FreeType this is the `cjk' module currently, and in ttfautohint it can be either `dummy' or `latin', to be controlled by another yet-to-be-written configuration option :-). With HarfBuzz it's quite easy to list every glyph that can be accessed through, say, the 'latn' GSUB table. I probably can provide some API for such introspection. That may solve your ttfautohint problem, but not FreeType's. Yes, this would be very helpful. For FreeType, there could be an interface to the autorhinter also, extending the table which defines the latin ranges. If I understand you correctly, there currently isn't a possibility to get such info from HarfBuzz easily (if at all)? Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
One major problem still remains which I have to resolve in the next days: Composite glyphs are rendered incorrectly. I've fixed that now. However, letting the autohinter handle subglyphs separately will always produce inferior results if compared to handling all subglyphs together at the same time. In particular, diacritics are sometimes positioned too near to the base letter. So please test the library! As usual, comments, suggestions, critique, etc., is highly welcomed. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
great. but i am embarrassed to admit that i have built the library but have not found how to use the 'autohint' function :) a quick howto, please! vern On 16 Jun 2011, at 21:20, Werner LEMBERG wrote: One major problem still remains which I have to resolve in the next days: Composite glyphs are rendered incorrectly. I've fixed that now. However, letting the autohinter handle subglyphs separately will always produce inferior results if compared to handling all subglyphs together at the same time. In particular, diacritics are sometimes positioned too near to the base letter. So please test the library! As usual, comments, suggestions, critique, etc., is highly welcomed. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
[Vern, I take the liberty to answer on the list also.] That's very interesting and gives some pretty good results. If no-one else has done so i am happy to run some specimen tests produce screenshots. This would be great! Please wait a few days until I've fixed the problem with composite glyphs (I'm nearly done, and the solution was much easier than expected); I'll then send another mail to the list. Are there plans with ttfautohint to give the user any abilities to vary/manipulate hinting parameters? Yes. However, I need input from experienced designers like you who tell me what shall be configurable. The first parameter to be added is the size range covered by hinting. For the moment, it is fixed to 8=ppem=1000. Another one is whether the original font's outline shall be used, or whether the font's original hinting shall be applied (at the font units level, which means 2048 ppem for most TrueType fonts). Some fonts like ArialMT *always* apply hints to some composite glyphs to shift one or more subglyphs. Note that the latter option will probably take some time to implement. Finally, there is the problem of glyphs which can't be addressed with a cmap directly, like small caps which are activated by an OpenType feature. Similar to FreeType's autohinter, such glyphs don't get any special consideration and are treated by the default hinting module (in FreeType this is the `cjk' module currently, and in ttfautohint it can be either `dummy' or `latin', to be controlled by another yet-to-be-written configuration option :-). This is quite a generic problem and needs separate attention; for the moment it is beyond my work on ttfautohint. So please comment and make suggestions! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
Werner, Sounds good. I think i remember you saying that ttfautohint will not have a GUI. Is that still the case? vernon On 15 Jun 2011, at 11:28, Werner LEMBERG wrote: [Vern, I take the liberty to answer on the list also.] That's very interesting and gives some pretty good results. If no-one else has done so i am happy to run some specimen tests produce screenshots. This would be great! Please wait a few days until I've fixed the problem with composite glyphs (I'm nearly done, and the solution was much easier than expected); I'll then send another mail to the list. Are there plans with ttfautohint to give the user any abilities to vary/manipulate hinting parameters? Yes. However, I need input from experienced designers like you who tell me what shall be configurable. The first parameter to be added is the size range covered by hinting. For the moment, it is fixed to 8=ppem=1000. Another one is whether the original font's outline shall be used, or whether the font's original hinting shall be applied (at the font units level, which means 2048 ppem for most TrueType fonts). Some fonts like ArialMT *always* apply hints to some composite glyphs to shift one or more subglyphs. Note that the latter option will probably take some time to implement. Finally, there is the problem of glyphs which can't be addressed with a cmap directly, like small caps which are activated by an OpenType feature. Similar to FreeType's autohinter, such glyphs don't get any special consideration and are treated by the default hinting module (in FreeType this is the `cjk' module currently, and in ttfautohint it can be either `dummy' or `latin', to be controlled by another yet-to-be-written configuration option :-). This is quite a generic problem and needs separate attention; for the moment it is beyond my work on ttfautohint. So please comment and make suggestions! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
I think i remember you saying that ttfautohint will not have a GUI. Is that still the case? Yes. ttfautohint is a library (with a single API function :-), and the `hint' program is just a small demo using it. Writing a GUI front-end might be a nice job later on, but it has no priority for me right now. Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
Re: [ft-devel] ttfautohint: Milestone reached!
On 06/15/11 06:28, Werner LEMBERG wrote: Finally, there is the problem of glyphs which can't be addressed with a cmap directly, like small caps which are activated by an OpenType feature. Similar to FreeType's autohinter, such glyphs don't get any special consideration and are treated by the default hinting module (in FreeType this is the `cjk' module currently, and in ttfautohint it can be either `dummy' or `latin', to be controlled by another yet-to-be-written configuration option :-). This is quite a generic problem and needs separate attention; for the moment it is beyond my work on ttfautohint. With HarfBuzz it's quite easy to list every glyph that can be accessed through, say, the 'latn' GSUB table. I probably can provide some API for such introspection. That may solve your ttfautohint problem, but not FreeType's. behdad ___ Freetype-devel mailing list Freetype-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/freetype-devel
