The FreeType Project - Bugs: bug #42522, Autohinter - dots too close with...
You are not allowed to post comments on this tracker with your current authentication level.
bug #42522: Autohinter - dots too close with 'i', 'j', '?', '!'
Submitter: | zboobzor <zboobzor> | ||
Submitted: | Sun 08 Jun 2014 02:33:54 AM UTC | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Confirmed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Open |
Planned Release: | None |
Jump to the original submission
Tue 26 May 2020 06:05:15 AM UTC, comment #11: |
Werner LEMBERG <wl> |
Tue 26 May 2020 05:45:25 AM UTC, comment #10: Another better option might be to allow adding 'important' gaps to Control Instructions File. This way font developers could select which gaps are critical due to design flaws, and add them. For instance e vs ɵ (it can be seen that Microsoft Arial preserves this gap even at 9ppem and 10ppem). |
- <_194785> |
Tue 26 May 2020 05:38:51 AM UTC, comment #9:
|
- <_194785> |
Tue 26 May 2020 05:04:05 AM UTC, comment #8: I heavily disagree. Ensuring a gap is exactly what TrueType bytecode instructions would do in such cases. Again: if an 'i' character looks like 'l' because the gap is missing, text becomes illegible. And such rounding problems sometimes can happen even at larger ppem values if the font design has just a narrow gap between dot and body. |
Werner LEMBERG <wl> |
Mon 25 May 2020 01:17:52 PM UTC, comment #7:
|
- <_194785> |
Mon 25 May 2020 12:31:40 PM UTC, comment #6: Well, the i dot must be separated from the body at any cost. Only if the ppem value is too small they might collide.
|
Werner LEMBERG <wl> |
Mon 25 May 2020 05:23:51 AM UTC, comment #5:
|
- <_194785> |
Sat 16 May 2020 04:19:54 AM UTC, comment #4: Since this also happens for sizes > 10ppem for some fonts, it should be eventually fixed.
|
Werner LEMBERG <wl> |
Fri 15 May 2020 07:34:03 PM UTC, comment #3: This is not a bug. The autohinter is working as intended and will not attempt to exaggerate those particular counters. Do not change this behavior. |
- <_194785> |
Sun 29 Jun 2014 04:41:09 PM UTC, comment #2: OK, I would be very grateful if you could look into this when you have time.
|
zboobzor <zboobzor> |
Mon 09 Jun 2014 07:52:41 AM UTC, comment #1: It has to be investigated whether this is easily possible. I say yes with some limitations, however, I currently don't have time to work on this.
|
Werner LEMBERG <wl> |
Sun 08 Jun 2014 02:33:54 AM UTC, original submission:
When using the autohinter set to hintslight the dot above 'i' and 'j' and below '?' and '!' is often too close to the rest of the character.
|
zboobzor <zboobzor> |
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 |
---|---|---|---|---|---|
2014-06-09 | wl | Status | None | Confirmed | |
Assigned to | None | wl |
Powered by Savane 3.13-02a9.
Corresponding source code
Whatever :-) I think an even better solution would be to make ttfautohint handling this as the default, with a possibility for the designer to switch it off in the control file.
I don't have time to dive into this topic, but your comments might be helpful to a forthcoming GSoC student to analyze the whole issue in more detail.