[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The current state of rendering and overlap
From: |
Skef Iterum |
Subject: |
The current state of rendering and overlap |
Date: |
Tue, 19 Dec 2023 01:10:57 -0800 |
User-agent: |
Mozilla Thunderbird |
Hello -
I've been looking into various FreeType issues related to the
combination of CFF2 and hinting. As part of that I ran into the
phenomenon represented in the attached capture of ftgrid. Which, to
summarize, has a rendering artifact caused by overlap.
It seemed like the simplest answer to this was to mark all outlines
extracted from a CFF2 font as FT_OUTLINE_OVERLAP, because there's no
inexpensive method of detecting it. And so I added code to do that and
verified it was heeded in ftsmooth.c -- but the ftgrid output didn't
look any different.
So I thought I would ask here: Is this what can be expected given the
path data or is there something else I should be looking at tweaking?
Thanks,
Skef Iterum (Adobe, Inc.)
uni0447_ftgrid.png
Description: PNG image
- The current state of rendering and overlap,
Skef Iterum <=
- Re: The current state of rendering and overlap, Werner LEMBERG, 2023/12/19
- Re: The current state of rendering and overlap, Skef Iterum, 2023/12/19
- Re: The current state of rendering and overlap, Cosimo Lupo, 2023/12/19
- Re: The current state of rendering and overlap, Werner LEMBERG, 2023/12/19
- Re: The current state of rendering and overlap, Skef Iterum, 2023/12/19
- Re: The current state of rendering and overlap, Alexei Podtelezhnikov, 2023/12/19
- Re: The current state of rendering and overlap, Alexei Podtelezhnikov, 2023/12/19
- Re: The current state of rendering and overlap, Hin-Tak Leung, 2023/12/19
- Re: The current state of rendering and overlap, Behdad Esfahbod, 2023/12/19
- Re: The current state of rendering and overlap, Cosimo Lupo, 2023/12/19