Unifont - Bugs: bug #50230, Fullwidth Latin-class characters...
You are not allowed to post comments on this tracker with your current authentication level.
bug #50230: Fullwidth Latin-class characters are no longer in sync with halfwidth
Submitter: | None | ||
Submitted: | Sun 05 Feb 2017 07:11:16 AM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Fixed |
Privacy: | Public | Assigned to: | unifoundry |
Open/Closed: | Closed |
Wed 21 Jun 2017 03:29:33 AM UTC, comment #2: |
Paul Hardy <unifoundry> |
Sun 05 Feb 2017 08:14:12 AM UTC, comment #1: Thank you for reporting this. Today (05-Feb-2017) is the date of the Debian freeze for the upcoming Debian 9 (stretch) release. I have planned to keep Unifont unchanged until either Debian 9 is released or Unicode 10.0.0 is released, whichever comes first. I am already working on changes for Unifont 10.0 in the meantime so they are ready for the next release. This bug does not sound like a catastrophic problem, so hopefully that time frame (approximately 5-6 months until the Unicode 10.0.0 release) will be suitable for you. |
Paul Hardy <unifoundry> |
Sun 05 Feb 2017 07:11:16 AM UTC, original submission:
Recently some characters were changed like f, { and 0 but the fullwidth style characters do not conform (well, 0 conforms somewhat but I think personally the "horizontal stretching" style should be kept for consistency.) |
Anonymous |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2017-06-21 | unifoundry | Open/Closed | Open | Closed | |
2017-06-21 | unifoundry | Status | In Progress | Fixed | |
2017-02-05 | unifoundry | Status | None | In Progress | |
Assigned to | None | unifoundry |
Powered by Savane 3.13-f8d8.
Corresponding source code
I believe that this bug has been fixed in the Unifont 10.0.01 release, just uploaded.