Unifont - Bugs: bug #52204, Problems with Ahom
You are not allowed to post comments on this tracker with your current authentication level.
bug #52204: Problems with Ahom
Submitter: | David Corbett <dscorbett> | ||
Submitted: | Tue 10 Oct 2017 11:55:50 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Works For Me |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed |
Sat 11 Aug 2018 06:13:00 AM UTC, comment #3: |
Paul Hardy <unifoundry> |
Mon 30 Jul 2018 03:37:49 AM UTC, comment #2: I have gone back to leaving all combining glyphs in combining.dat files, if nothing else because some font rendering engines are making up their own minds about combining glyph placement. As a consequence, I think this is too tangled a mess for a font that is not a full, high-resolution vector font with intelligent double- and triple-glyph placement. Because of the limitations inherent in Unifont, further complicated by different rendering engines interpreting (or not interpreting) the combining character information differently, I intend to leave Ahom as it is. The same holds for Saurashtra. |
Paul Hardy <unifoundry> |
Sat 14 Oct 2017 08:52:09 PM UTC, comment #1: David,
|
Paul Hardy <unifoundry> |
Tue 10 Oct 2017 11:55:50 PM UTC, original submission:
Some Ahom vowel signs are doubled and used with other vowel signs, so in Unifont, they overlap themselves and each each other. The solution is to make certain combining marks be spacing. Based on the combinations listed in the Unicode proposal (http://www.unicode.org/L2/L2012/12309r-n4321r.pdf) I think the best set of marks to be spacing is:
|
David Corbett <dscorbett> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-08-11 | unifoundry | Status | None | Works For Me | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-cf05.
Corresponding source code
I am marking this as "works for me" because the changes suggested will not render correctly given the shortcomings in the common font rendering engines. In particular, removing combining characters from combining character data files will not have the desired effect in common font rendering engines. If an individual glyph is incorrect, please submit a separate bug report.
Thank you,
Paul Hardy