[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The current state of rendering and overlap
From: |
Alexei Podtelezhnikov |
Subject: |
Re: The current state of rendering and overlap |
Date: |
Tue, 19 Dec 2023 07:20:58 -0500 |
> 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.
FT_OUTLINE_OVERLAP mitigates the artifact but does not completely
remove it. The 4x4 resolution increase might still have some residual
artifacts. Further increasing it is impractical and prohibitive from
the performance standpoint. I think this is the issue in your example.
The most egregious overlaps which cover half-pixels are dealt with
quite successfully.
Alexei
- Re: The current state of rendering and overlap, (continued)
- 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, 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, Skef Iterum, 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, 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, Behdad Esfahbod, 2023/12/20
Re: The current state of rendering and overlap,
Alexei Podtelezhnikov <=