Hi,
On Wed, 15 Feb 2006 20:31:13 +0800
DingLi(丁力) [EMAIL PROTECTED] wrote:
When I use Freetype, I found that some phenomenon
that some fragmentized characters.
For example, the mingliu.tcc(True Collection), is it a bug?
This is not bug of FreeType.
MingLiU.ttc requires bytecode hinting support
On Wed, 2006-02-15 at 17:31, Werner LEMBERG wrote:
- do the required modifications, encapsulating each of the old
internals in a configuration macro
(e.g. FT_CONFIG_OPTION_OLD_INTERNALS)
Sounds good. We should mention in the docs that these steps are
performed only *once*, and that
As the author of a rogue client for which no patch is contemplated
(and for which we decided last year that there was no good way to
provide a patch) I must beg that
TT_RunIns
remain reachable.
We add `TT_RunIns' manually to the list of exported symbols. This
should be sufficient,
George Williams a écrit :
On Wed, 2006-02-15 at 17:31, Werner LEMBERG wrote:
- do the required modifications, encapsulating each of the old
internals in a configuration macro
(e.g. FT_CONFIG_OPTION_OLD_INTERNALS)
Sounds good. We should mention in the docs that these steps
We add `TT_RunIns' manually to the list of exported symbols. This
should be sufficient, shouldn't it?
That's all I want.
Please, please, please.
It's already implemented so in the GNU makefile since a few weeks.
Werner
___
Freetype-devel
On Thu, 2006-02-16 at 06:15, Werner LEMBERG wrote:
As the author of a rogue client for which no patch is contemplated
(and for which we decided last year that there was no good way to
provide a patch) I must beg that
TT_RunIns
remain reachable.
We add `TT_RunIns' manually to the
On Thu, 2006-02-16 at 07:08, david turner wrote:
I still don't understand why you absolutely want the ability to
dynamically peek into the
internals of the libfreetype installed on the system, especially since
it will not have the
bytecode interpreter on most distros anyway...
I want
