Unifont - Bugs: bug #45538, Incorrent display of COMBINING...
You are not allowed to post comments on this tracker with your current authentication level.
bug #45538: Incorrent display of COMBINING ACUTE ACCENT, U+0301
Submitter: | Suntor <suntor> | ||
Submitted: | Mon 13 Jul 2015 05:54:24 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | unifoundry |
Open/Closed: | Closed |
Jump to the original submission
Sat 01 Jul 2017 08:00:43 PM UTC, comment #14: |
Paul Hardy <unifoundry> |
Fri 30 Jun 2017 11:24:39 PM UTC, comment #13: Suntor,
|
Paul Hardy <unifoundry> |
Fri 30 Jun 2017 09:33:45 PM UTC, comment #12: I am going to look into this further, so I am leaving this bug open.
|
Paul Hardy <unifoundry> |
Fri 30 Jun 2017 08:13:50 PM UTC, comment #11: Suntor,
|
Paul Hardy <unifoundry> |
Fri 30 Jun 2017 07:55:42 PM UTC, comment #10: Suntor,
|
Paul Hardy <unifoundry> |
Fri 30 Jun 2017 04:59:49 PM UTC, comment #9: I consider this to be working properly with the latest Unifont release, for the reasons described below. I have tested this with Unifont 10.0.01, which was built on Debian 9 ("stretch"), released on 17 June 2017, using an updated version of FontForge. Unicode Standard version 10.0.0 was released three days after Debian 9. So this testing was done with a Unifont version that was built with very recent versions of Unicode, Debian, and FontForge.
|
Paul Hardy <unifoundry> |
Sun 12 Mar 2017 11:17:33 PM UTC, comment #8: I will have to go through the code and see what the end difference is, and look through my notes to see why I made any changes. The one significant change I made was adding support for combining characters beyond Unicode Plane 0. I did test the change at the time and it worked on what I tried.
|
Paul Hardy <unifoundry> |
Sun 12 Mar 2017 10:34:26 PM UTC, comment #7: It looks like the positioning information in Unifont did change. The 2008 fix added the variable $xoffset to src/hex2sfd (https://github.com/SamB/debian-unifont/commit/adcf6b0db27f2c4041bdda9ed8076f9e7caf38cd#diff-8bd048f6aa5ea68f794d52b794e9a9d2R88) but Unifont 9.0.06’s src/hex2sfd does not include that variable. Therefore the problem is in the font, not in the font rendering engine. |
David Corbett <dscorbett> |
Sun 12 Mar 2017 09:25:59 PM UTC, comment #6: David, I did get this working correctly in Debian in 2008, but that was almost 10 years ago and things could have changed. THe positioning information in Unifont should not have changed, but font rendering engines definitely have changed over time.
|
Paul Hardy <unifoundry> |
Wed 08 Mar 2017 11:26:43 PM UTC, comment #5: Didn’t you already fix this bug in the Debian version of Unifont in 2008?
|
David Corbett <dscorbett> |
Tue 21 Jul 2015 01:41:39 PM UTC, comment #4: ftstring indeed renders the combining character over the next glyph. It renders correctly under Pango, however (which is what gtk uses).
|
Anonymous |
Mon 20 Jul 2015 01:03:44 AM UTC, comment #3: Thank you for reporting this.
|
Paul Hardy <unifoundry> |
Sat 18 Jul 2015 04:20:21 PM UTC, comment #2: Test last unifont-8.0.01.ttf version, and it does not correctly display this U+0301 combining symbol. See picture: |
Suntor <suntor> |
Thu 16 Jul 2015 05:52:00 PM UTC, comment #1: The 8.0.01 TTF renders correctly for me. The precompiled BDF and PCF don't show combining characters at all under gtk2 (which uses cairo), while ftstring displays them like spaced characters.
|
Anonymous |
Mon 13 Jul 2015 05:54:24 AM UTC, original submission:
COMBINING ACUTE ACCENT, U+0301 must be set AFTER target symbol as another combining symbols accoding Unicode standard, so the font must display combining glyph over previous symbol in text. But Unifont display combining glyph over next symbol in text. Such error was in Verdana font in Windows XP and had been fixed in Windows Vista and with “European Union Expansion Font Update” for early versions. |
Suntor <suntor> |
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 19 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-07-01 | unifoundry | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
2017-06-30 | unifoundry | Status | Works For Me | In Progress | |
Open/Closed | Closed | Open | |||
2017-06-30 | unifoundry | Attached File | - | Added x.c, #41093 | |
Attached File | - | Added x.txt, #41094 | |||
2017-06-30 | suntor | Attached File | - | Added Unifont-10.0.01 U+0301 error (WS2012R2).png, #41091 | |
Attached File | - | Added U+0301.utf16le-bom.txt, #41092 | |||
2017-06-30 | suntor | Attached File | - | Added Unifont-10.0.01 U+0301 error (WS2012R2).png, #41089 | |
Attached File | - | Added U+0301.utf16le-bom.txt, #41090 | |||
2017-06-30 | unifoundry | Attached File | - | Added kyrie.txt, #41085 | |
Attached File | - | Added Kyrie-eleison-Win7-Word2013.png, #41086 | |||
Attached File | - | Added Kyrie-eleison-Debian-stretch-LibreOffice.png, #41087 | |||
Attached File | - | Added Kyrie-eleison-Mac-TextEdit.png, #41088 | |||
Status | Postponed | Works For Me | |||
Open/Closed | Open | Closed | |||
2015-07-20 | unifoundry | Status | None | Postponed | |
Assigned to | None | unifoundry | |||
2015-07-18 | suntor | Attached File | - | Added U+0301 error.png, #34461 |
Powered by Savane 3.13-f8d8.
Corresponding source code
Suntor,
Great, I will close this bug report since it is now working for you. After Unifont 10.0.03 has been released for a while (to be determined), I will create a Unifont 10.0.04 release that has this change and some other things in it. At that point I will no longer consider this to be experimental (unless someone else reports a different problem).
Paul