Unifont - Bugs: bug #48145, TTF Unifont since version 7.0.04...
You are not allowed to post comments on this tracker with your current authentication level.
bug #48145: TTF Unifont since version 7.0.04 renders badly with hinting, but no antialiasing
Submitter: | None | ||
Submitted: | Mon 06 Jun 2016 01:53:14 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Works For Me |
Privacy: | Public | Assigned to: | unifoundry |
Open/Closed: | Closed |
Discussion locked!
Jump to the original submission
Thu 21 Jun 2018 02:54:46 AM UTC, comment #7: |
Paul Hardy <unifoundry> |
Sun 10 Sep 2017 09:32:43 PM UTC, comment #6: Felix,
|
Paul Hardy <unifoundry> |
Thu 17 Aug 2017 05:14:43 PM UTC, comment #5:
|
felix <felix_s> |
Thu 17 Aug 2017 12:21:36 PM UTC, comment #4: First of all, what operating system are you using?
|
Paul Hardy <unifoundry> |
Wed 16 Aug 2017 03:51:47 PM UTC, comment #3: I'm seeing this quite late, but I can say I haven't seen significant improvement in Unifont 10.0.05.
|
felix <felix_s> |
Wed 28 Jun 2017 12:58:17 PM UTC, comment #2: To the anonymous poster of this issue: please contact me. I will need to give you some trial font builds to test. Thank you.
|
Paul Hardy <unifoundry> |
Wed 08 Jun 2016 02:52:14 AM UTC, comment #1: Thank you for taking the time to investigate and report this problem.
|
Paul Hardy <unifoundry> |
Mon 06 Jun 2016 01:53:14 PM UTC, original submission:
When rendering TTF Unifont 7.0.04 and later with hinting enabled, but antialiasing disabled, FreeType generates ugly-looking artifacts (screenshot of ftstring attached). Either disabling antialiasing or disabling hinting makes the artifacts disappear. Enabling antialiasing is out of the question, however; with subpixel antialiasing, some applications will render Unifont slightly off the pixel grid, which sometimes strains eyes severely (screenshot attached; rendered with gamma 3 to exaggerate the effect, since it's not very visible in ftstring)
|
Anonymous |
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 11 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-06-21 | unifoundry | Attached File | - | Added unifont-7.0.01-hinting-active.png, #44399 | |
Attached File | - | Added unifont-7.0.01-hinting-ignored.png, #44400 | |||
Attached File | - | Added unifont-11.0.01-hinting-active.png, #44401 | |||
Attached File | - | Added unifont-11.0.01-hinting-ignored.png, #44402 | |||
Status | Postponed | Works For Me | |||
Open/Closed | Open | Closed | |||
Discussion Lock | None | Locked | |||
2016-06-08 | unifoundry | Status | None | Postponed | |
Assigned to | None | unifoundry | |||
2016-06-06 | None | Attached File | - | Added artifacts.png, #37403 | |
Attached File | - | Added subpixel-aa.png, #37404 |
Powered by Savane 3.13-02a9.
Corresponding source code
I have tried various versions of Unifont with ftstring under Debian GNU/Linux with no antialiasing. The last was the newly-released Unifont 11.0.01, comparing it with Unifont 7.0.01, Unifont 7.0.02, Unifont 7.0.03, and Unifont 7.0.04. I cannot see a difference with Unifont 11.0.01 glyphs versus Unifont 7.0.01 to 7.0.03 and neither could other people I asked to look for differences.
I am attaching the last tests I did, between Unifont 7.0.01 and Unifont 11.0.01 on a 4k monitor for its high resolution. I set the point size for this to 48 pt in order to try to magnify any differences between hinting being active and hinting being disabled.
I am closing this bug as "works for me" because after trying multiple Unifont versions with hinting toggled on and off, neither I nor anybody I have asked can see any difference.
Paul Hardy