Re: The current state of rendering and overlap
Hin-Tak Leung <[email protected]> Tue, 19 Dec 2023 16:49:42 +0000 (UTC)
| Newsgroups | gmane.comp.fonts.freetype.devel |
|---|---|
| Message-ID | <[email protected]> |
This is the same as the winding rule concept (overlap once = wounded twice) ... I seem to remember one of them is even-odd and the other is non-zero, and quite fundamental difference between truetype and cff.
On Tuesday, 19 December 2023 at 13:54:21 GMT, Alexei Podtelezhnikov <[email protected]> wrote:
It's easy enough to add FT_OUTLINE_OVERLAP to any glyph loaded from a
CFF2 font. Whether that makes sense is one thing I'd like advice about.
There's currently no such code.
I would suggest that CFF2 invent a special charstring to mark overlaps
with FT_OUTLINE_OVERLAP only when necessary. Let us know to implement
it in FreeType.
https://www.w3.org/TR/WOFF2/#p1
WOFF2 is moving towards accepting explicit overlap flags. Perhaps CFF2 can spare a reserved operator or a two-byte operator.