Open
Bug 1401870
Opened 8 years ago
Updated 3 years ago
Mark is positioned incorrectly after forming ligature
Categories
(Core :: Graphics: Text, defect, P3)
Tracking
()
NEW
People
(Reporter: mozillabugs, Unassigned)
Details
(Whiteboard: [gfx-noted])
Attachments
(5 files)
The attached font and HTML file demonstrate a bug that was found during development of a Burmese font. Burmese requires glyph reordering, ligature formation, and mark-to-base and mark-to-mark positioning.
In the test font, the marks u (U+102F) and anusvara (U+1036) are positioned relative to the base nna (U+100F) via anchor attachments. When tested by themselves, this works fine. Positioning of the anusvara also works fine when a medial ra (U+103C) is present. However, when a medial ra is present, the font forms a ligature from medial ra and u in order to position them together. The rule for this is
feature blws {
script mym2;
lookup raMedial_uMark_myanmar {
lookupflag IgnoreBaseGlyphs UseMarkFilteringSet @below_base_myanmar;
sub raMedial-myanmar uMark-myanmar by raMedial_uMark-myanmar;
} raMedial_uMark_myanmar;
};
After the ligature is formed, the anusvara is no longer positioned correctly. It appears that the shaping engine loses track of nna as the base and positions relative to the medial ra + u ligature instead.
The same problem does not occur in Safari 11.0.
Firefox 55.0.3
Reporter | ||
Comment 1•8 years ago
|
||
Reporter | ||
Comment 2•8 years ago
|
||
Reporter | ||
Comment 3•8 years ago
|
||
Reporter | ||
Comment 4•8 years ago
|
||
Comment 5•8 years ago
|
||
This would be a harfbuzz issue, better reported at https://github.com/behdad/harfbuzz/issues. (Note that Chrome renders the same as Firefox.)
Also, how does it render in MS Edge?
Updated•8 years ago
|
status-firefox55:
--- → wontfix
status-firefox56:
--- → wontfix
status-firefox57:
--- → fix-optional
status-firefox58:
--- → fix-optional
status-firefox-esr52:
--- → wontfix
Priority: -- → P3
Whiteboard: [gfx-noted]
Reporter | ||
Comment 6•8 years ago
|
||
Filed as harfbuzz issue:
https://github.com/behdad/harfbuzz/issues/543
Comment 7•7 years ago
|
||
status-firefox59:
--- → ?
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•