. Add `FT_FACE_FLAG_TRICKY'. If set, the font is tricky. To
access it, add a macro `FT_IS_TRICKY'. [This is a read-only
flag.]
. Change the meaning of `FT_LOAD_NO_HINTING' so that fonts which
always need TrueType instructions (these are fonts which have
One last (perhaps stupid) question:
What happens (with or w/o the proposed change) for tricky fonts when ft
is compiled with -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER?
OK. Two questions.
What about the cases where autofitting or light autofitting is requested
and the font is tricky? Do the
What happens (with or w/o the proposed change) for tricky fonts when
ft is compiled with -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER?
The patented hinting is forced then.
What about the cases where autofitting or light autofitting is
requested and the font is tricky? Do the instructions get
After some thinking I can imagine that the following works.
. Add `FT_FACE_FLAG_TRICKY'. If set, the font is tricky. To access
it, add a macro `FT_IS_TRICKY'. [This is a read-only flag.]
. Change the meaning of `FT_LOAD_NO_HINTING' so that fonts which
always need TrueType
. Add `FT_FACE_FLAG_TRICKY'. If set, the font is tricky. To
access it, add a macro `FT_IS_TRICKY'. [This is a read-only
flag.]
. Change the meaning of `FT_LOAD_NO_HINTING' so that fonts which
always need TrueType instructions (these are fonts which have
FT_FACE_FLAG_TRICKY
So anyone who use freetype or libraries that use freetype (like
cairo) will have to be make awared of this problem. I'm not sure
how practical this will be.
Graham's suggestion of introducing a flag in FT_Face sounds good.
If I understand his sugguestion correctly, the user always has
That proposal looks right. It, of course, has the advantage of
backwards compatability in that current apps and libs will just work
once ft is upgraded.
Now to deal with the quarter or two metres of snow which fell since I
last posted here. [SIGH] If you don't hear from me again I'm probably
On 2008-12-05, Werner LEMBERG [EMAIL PROTECTED] wrote:
After some thinking I can imagine that the following works.
. Add `FT_FACE_FLAG_TRICKY'. If set, the font is tricky. To access
it, add a macro `FT_IS_TRICKY'. [This is a read-only flag.]
. Change the meaning of
FT_LOAD_NO_HINTING now has a implication: I will do some auto fixing
with the hinting when neccessary unless your also prevent me with
NO_AUTOHINT.
? I fear I don't understand. Please explain what you mean.
Werner
___
Freetype-devel
The tricky fonts like PMingLiU need unpatented hinting. Those
fonts are unusable at all when programmers accidently turns on
FT_LOAD_NO_HINTING. So I think freetype should force fonts like
those to ignore FT_LOAD_NO_HINTING.
This is a fundamental question. My opinion is that shifting of
:[EMAIL PROTECTED] On
Behalf Of Werner LEMBERG
Sent: 04 December 2008 08:06
To: [EMAIL PROTECTED]
Cc: freetype-devel@nongnu.org
Subject: Re: [ft-devel] Force PMingLiU like font do HINTING
The tricky fonts like PMingLiU need unpatented hinting. Those
fonts are unusable at all when programmers
FreeType can't normally 'emit warning messages' because it is a
library, not an app - it's up to the caller how to deal with
errors. A new, well documented, error code that the caller can
choose to ignore is the way to go, in my opinion.
Sounds good. However, which function should return
PROTECTED]
Sent: 04 December 2008 10:21
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; freetype-devel@nongnu.org
Subject: Re: [ft-devel] Force PMingLiU like font do HINTING
FreeType can't normally 'emit warning messages' because it is a
library, not an app - it's up to the caller how to deal
I'm not sure if unpatented hinting solves the broken shape of
MingLiU completely. I guess it's better than nothing but not fully,
and the introduction of the trick of conditional hinting cannot
close MingLiU issue.
Mhmm, *theoretically* it should be sufficient. Why do you think it
isn't?
On Thu, 04 Dec 2008 11:40:22 +0100 (CET)
Werner LEMBERG [EMAIL PROTECTED] wrote:
I'm not sure if unpatented hinting solves the broken shape of
MingLiU completely. I guess it's better than nothing but not fully,
and the introduction of the trick of conditional hinting cannot
close MingLiU
]
Cc: freetype-devel@nongnu.org
Subject: Re: [ft-devel] Force PMingLiU like font do HINTING
The tricky fonts like PMingLiU need unpatented hinting. Those
fonts are unusable at all when programmers accidently turns on
FT_LOAD_NO_HINTING. So I think freetype should force fonts like
those
How is it possible to decide from the font it is unusable with
FT_LOAD_NO_HINTING?
Unfortunately, it isn't. We have a hard-coded list of `tricky' fonts
for this purpose.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
On 2008-12-04, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I think MingLiU is a commercial font bundled to Microsoft
Windows, and Mozilla can use Microsoft's TrueType rasterizer
supporting patented hinting technology. If there is a case that
the tricky application of unpatented hinting of
Do those tricky fonts' gasp tables suggest not to use hinting even
though they look bad without it?
Good question. One old font which I have, mingli.ttf, doesn't have a
gasp table at all.
Or they look bad when a programmer asks to turn the hinting off
ignoring the gasp table suggestion?
So anyone who use freetype or libraries that use freetype (like
cairo) will have to be make awared of this problem. I'm not sure how
practical this will be.
Graham's suggestion of introducing a flag in FT_Face sounds good.
And I'm still seeing PDF files using those fonts often. Without
I feel it is not right to allow such a low-level API as freetype to
override programmer request for the hinting type unless we have
FT_LOAD_NO_HINTING FT_LOAD_NO_HINTING_AND_I_REALLY_MEAN_THAT
Hmm. This would be a change in the API which I won't implement. But
see Graham's suggestion.
The
On 2008-12-04, Werner LEMBERG [EMAIL PROTECTED] wrote:
So anyone who use freetype or libraries that use freetype (like
cairo) will have to be make awared of this problem. I'm not sure how
practical this will be.
Graham's suggestion of introducing a flag in FT_Face sounds good.
If I
The tricky font like PMingLiU need unpatented hinting. Those fonts are
unusable at all when programmers accidently turns on FT_LOAD_NO_HINTING.
So I think freetype should force fonts like those to ignore
FT_LOAD_NO_HINTING.
And detecting of tricky font should be outside of this defines:
23 matches
Mail list logo
