The FreeType Project - Patches: patch #6042, Unable to turn on unpatented hinter
You are not allowed to post comments on this tracker with your current authentication level.
patch #6042: Unable to turn on unpatented hinter
Submitter: | None | ||
Submitted: | Fri 22 Jun 2007 08:44:05 PM UTC | ||
Category: | None | Priority: | 5 - Normal |
Status: | Invalid | Privacy: | Public |
Assigned to: | freetype | Originator Email: | -email is unavailable- |
Open/Closed: | Closed |
Sun 01 Jul 2007 05:45:52 AM UTC, comment #2: |
Anonymous |
Sat 30 Jun 2007 10:27:45 PM UTC, comment #1: first of all, it's not possible to have both the unpatented and patented hinter in the library. You must select only one of them.
|
David Turner <freetype> |
Fri 22 Jun 2007 08:44:05 PM UTC, original submission:
It seems that when you've enabled the patented hinter, you can no longer turn on the unpatented one. I believe that is because the parsing code for the parameter to do so gets removed when you enable the patented code.
|
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2007-06-30 | freetype | Status | None | Invalid | |
Open/Closed | Open | Closed | |||
2007-06-23 | wl | Assigned to | None | freetype | |
2007-06-22 | None | Attached File | - | Added ttobjs.c.diff, #13139 |
Powered by Savane 3.13-caa5.
Corresponding source code
Well, I need them both to be in the library :)
For instance, I'm creating a testing harness. Some of the devices being tested match closer to the patented hinting and some to the autohinter. I do use both.
Also, I don't think there should be an option to turn on the unpatented hinter if the parsing of that option is ignored. If the decision of the freetype team is to not allow both to be used, I think the option should be removed also.
-- Ted Gould <ted@gould.cx>