freetype-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Devel] FT_Set_Hint_Flags problem


From: David Turner
Subject: Re: [Devel] FT_Set_Hint_Flags problem
Date: Thu, 24 Apr 2003 19:04:34 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Werner LEMBERG wrote:
David,


in Sept 2002 you've removed FT_Set_Hint_Flags from freetype.h.  I just
found out that the function is still in ftobjs.c.  Shall it be removed?

The reason this function is still there, even if it is dormant, is to avoid
completely breaking RedHat 8.0 systems when users upgrade to a newer FreeType
release !

RH 8.0 uses a modified version of FT 2.1.2 and libXft that directly
call FT_Set_Hint_Flags to modify the "hinting" settings in the
font control panel. Had this function disappeared from the library,
any user installing a more recent version of FT2 would break many
things on his machine.

I don't know about RH 9, by the way, the "problem" might still persist
as well.

Maybe we need a new "tag" to warn users that something shouldn't
be used for production code, since "EXPERIMENTAL" or "INTERNAL" seem
to be ignored constantly by certain people. what about one of the
followings:

 - YOU_DONT_MEAN_IT_DO_YOU_?
 - CRASH_IS_SO_FUNNY
 - INTEGRATION_?_WHAT_INTEGRATION_?
 - ROT_IN_HELL
 - OWEN_DONT_TOUCH_THIS__PLEAAAASE

Aaaaaaaaah, feel better :-)

- David Turner
- The FreeType Project  (www.freetype.org)

PS: I suspect the function will stay there for some time.
    But I don't know if we'll be so nice in the future...


--
This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender.
Any use not in accordance with its purpose, any dissemination or disclosure,
either whole or partial, is prohibited except formal approval.
The E-Mail transmission can not guarantee the integrity of this message.
CANAL+TECHNOLOGIES will not therefore be liable for the message if modified.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]