microsoft / microsoft/font-tools
EgyptianOpenType template contains red and slashed diagnostic glyph artifacts in production glyphs
- Dominant language
- HTML
- Stars
- 78
- Forks
- 18
- Avg merge
- 27m
- Merged PRs (30d)
- 2
Description
## Summary
Some glyphs in the EgyptianOpenType font/template appear to contain leftover diagnostic or placeholder artwork: red-colored glyphs and grey glyphs with a red slash.
This appears to affect the canonical EOT-derived font/template rather than being a rendering issue in a downstream color-font build.
## Observed behavior
In Egyptian Text / EOT-derived output, several glyphs render in red instead of the expected normal monochrome/production appearance.
Two rotational-variant glyphs also render as grey glyphs with a red slash. In testing, these appeared to correspond to rotational variants, e.g. signs such as M33A and F46A, but the rendered result includes a visible red slash artifact.
## Expected behavior
Production glyphs should not contain visible diagnostic red coloring or slash overlays unless those marks are intentional encoded characters.
The affected glyphs should render as ordinary production glyphs.
## Reproduction
1. Build or install the current EgyptianOpenType / Egyptian Text font.
2. Render the affected glyphs/signs.
3. Observe that the glyphs render in red or with a grey/red-slash overlay.
## List of affected Glyphs
Red glyphs:
U+1327C O29A
U+13339 U6A
U+133DC Y1A
U+133E9 Z2D
U+13406 Z16B
Grey/red-slashed glyphs:
U+13133 F46A
U+131E1 M33A
The same artifacts also appear in contextual/internal variants:
O29a_11, U6a_11, Y1a_11, F46a_11, M33a_11.
These do not have separate Unicode codepoints but are emitted by EOT shaping in some contexts, so they should be patched together with the directly encoded glyphs.
## Evidence
I can provide:
- screenshots comparing the affected glyphs before/after
- a patched version used in downstream testing
- notes identifying affected glyphs
- TTX or fontTools-based patch notes, if useful
## Proposed fix
Remove the diagnostic red/slash artwork from the affected glyphs and replace it with the intended production outlines.
I have a downstream patch that fixes these glyphs in my test font. I am happy to share the patch or prepare a pull request if the maintainers confirm the preferred source file/location to patch.
## Downstream fixed font available
I have a downstream fixed version of `eot_3.001.ttf` in which the red glyph artifacts and red slash overlays have been removed.
The fixed font is useful as a proof that the affected glyph artwork can be corrected, but I understand that an upstream fix should ideally be made in the source/template files that generate the font, rather than by submitting only a modified binary `.ttf`.
## Notes
This is separate from Egyptian Hieroglyph Format Control shaping behavior. It appears to be a glyph-artwork/template issue.
[List_of_affected_glyphs.odt](https://github.com/user-attachments/files/27772548/List_of_affected_glyphs.odt)
[List_of_affected_glyphs.pdf](https://github.com/user-attachments/files/27772549/List_of_affected_glyphs.pdf)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the EgyptianOpenType source or template that generates eot_3.001.ttf, then compare the listed encoded and contextual glyphs with the downstream fixed font and the attached glyph lists. Rebuild and render the affected signs to verify that the red coloring and grey/red-slash overlays are absent from all listed production and internal variants.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100