Re: [GSoC] Status of font-rs port
Anurag > > Can also look at some more challenging fonts with very fine curves, eg, > > Windows' KUNSTLER.TTF > > I tested it, and the rasterizer output is almost identical. > > Curiously, for this font, the dense rasterizer is faster even till 200-300 > ppem font size This is definitely because smooth is constrained by memory and has to restart (see longjmp) with narrower bands to handle the job. It looks like one restart for each glyph approximately. > Relevant files attached. Do you mind continuing this discussion as an issue on GitLab? A
Re: [GSoC] Status of font-rs port
Anurag, > 1 and 2 have been fixed, but monochrome output still crashes ftgrid for the > dense rasterizer Smooth returns Cannot_Render_Glyph for mono, thus passing the job to b/w raster. Dense should do the same. A.
Re: [GSoC] Status of font-rs port
> 1 and 2 have been fixed, but monochrome output still crashes ftgrid > for the dense rasterizer A good start would be a backtrace... Werner
RE: [GSoC] Status of font-rs port
Thanks for the quick fix! 1 and 2 have been fixed, but monochrome output still crashes ftgrid for the dense rasterizer I’ll investigate it and report Regards Anurag From: Alexei Podtelezhnikov Sent: Friday, September 16, 2022 9:16 AM To: Anurag Thakur Cc: freetype-devel@nongnu.org Subject: Re: [GSoC] Status of font-rs port On Thu, Sep 15, 2022 at 5:53 PM Anurag Thakur mailto:anurag105cse...@bpitindia.edu.in>> wrote: List of bugs I have encountered: 1. Ftgrid produces weird output and crashes at large sizes(~170ppem) 2. The inverted bitmap pitch causes rendering differences (can be seen in the “Q” letter of the ftview output) 3. Ftgrid crashes when selecting monochrome output Should be fixed by a005039b. Thanks for the report.
