The FreeType Project - Bugs: bug #19044, Arial spacing problem with 2.3.1...
You are not allowed to post comments on this tracker with your current authentication level.
bug #19044: Arial spacing problem with 2.3.1 (regression from 2.1.10), autohinting on, AA on, 10pt.
Submitter: | Alexander Shaduri <alex_sh> | ||
Submitted: | Mon 12 Feb 2007 06:37:17 PM UTC | ||
Votes: | 50 | ||
Severity: | 3 - Normal | Item Group: | Incorrect behaviour |
Status: | Fixed | Privacy: | Public |
Assigned to: | wl | Open/Closed: | Closed |
Planned Release: | 2.7.1 |
Jump to the original submission
Thu 17 Nov 2016 07:11:17 AM UTC, comment #8: |
Werner LEMBERG <wl> |
Wed 02 Nov 2016 02:29:52 PM UTC, comment #7: This code there is really suspect:
|
Alexei Podtelezhnikov <podtelez> |
Tue 12 Jun 2007 09:14:55 AM UTC, comment #6: Could you please re-open this bug report?
|
Alexander Shaduri <alex_sh> |
Thu 12 Apr 2007 03:13:43 PM UTC, comment #5:
|
Alexander Shaduri <alex_sh> |
Mon 09 Apr 2007 08:18:50 PM UTC, comment #4: Do you still think that this is necessary with the
|
Werner LEMBERG <wl> |
Wed 21 Feb 2007 07:22:29 PM UTC, comment #3: After about half an hour of random torturing of the freetype source code, I finally found what was causing the distance to be so large. While I have absolutely no idea why it worked or how I found it, I'm pretty sure the patch fixes the "distance too large" problem for Arial 8pt bold @ 96dpi.
|
Alexander Shaduri <alex_sh> |
Sat 17 Feb 2007 01:13:59 PM UTC, comment #2: Thanks, the inconsistency seems to be fixed (as of cvs 2007-02-16) - the font looks much better now.
|
Alexander Shaduri <alex_sh> |
Wed 14 Feb 2007 11:41:25 PM UTC, comment #1: I believe that this bug is now fixed in the CVS. Please test and I'll close it
|
David Turner <freetype> |
Mon 12 Feb 2007 06:37:17 PM UTC, original submission:
Arial rendering has suffered a regression from 2.1.10 to 2.3.1 with autohinting on.
|
Alexander Shaduri <alex_sh> |
Depends on the following items: None found
Items that depend on this one: None found
There are 50 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 14 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-11-17 | wl | Attached File | - | Added without-delta.png, #38997 | |
Attached File | - | Added with-delta.png, #38998 | |||
Status | Confirmed | Fixed | |||
Assigned to | freetype | wl | |||
Open/Closed | Open | Closed | |||
Planned Release | 2.3.2 | 2.7.1 | |||
2009-08-18 | pmw | Carbon-Copy | - | Added -email is unavailable- | |
2007-06-12 | wl | Open/Closed | Closed | Open | |
2007-02-17 | alex_sh | Attached File | - | Added ft_compare_2110_cvs2007-02-14_hintfull_autohint_size8.png, #11994 | |
Carbon-Copy | - | Added alex_sh | |||
2007-02-16 | wl | Open/Closed | Open | Closed | |
Planned Release | None | 2.3.2 | |||
2007-02-12 | wl | Status | None | Confirmed | |
Assigned to | None | freetype |
Powered by Savane 3.13-f8d8.
Corresponding source code
If you are going to use strong hinting, you must apply side bearing correction (i.e., the fields `lsb_delta' and `rsb_delta' in `FT_GlyphSlot') to compensate the increased side bearings that are intentionally added by the auto-hinter.
The attached ftstring images `without_delta.png' and `with_delta.png' showing `arialbd.ttf' at 10pt@96dpi neatly demonstrate this.
Note that it doesn't harm if the necessary code (as explained in the `FT_GlyphSlot' documentation) gets applied to any other hinting mode; the delta correction values are simply zero then.
This is a documentation bug. I've added a comment to the source code to explain why `pp1.x' is not needed. I've also improved the documentation of the delta values.