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.
>
I
> "Werner" == Werner LEMBERG <[EMAIL PROTECTED]> writes:
>> And I'm still seeing PDF files using those fonts often.
>> Without hinting.
Werner> Why is there no hinting?
Poppler (and probably xpdf before it) forces no hinting because it is
rendering paper documents and is likely trying to mai
> 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.
>
> 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
> > 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 ta
> 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?
I see now. Thank you.
Do those tricky fonts' gasp tables suggest not to use hinting even
though they look bad without it?
Or they look bad when a programmer asks to turn the hinting off ignoring
the gasp table suggestion?
Thanks,
Sergey Tolstov
> -Original Message-
> From: Werner LEMBERG
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 o
> 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
http:
Hello,
How is it possible to decide from the font it is unusable with
FT_LOAD_NO_HINTING?
Thank you,
Sergey Tolstov
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Werner LEMBERG
> Sent: Thursday, December 04, 2008 12:06 AM
> To: [EMAIL PROTECTE
With current cvs I get no-"ink" rendering of cff fonts when using the
light autofitter. Type1 and glyf fonts work correctly.
I can reproduce the bug with ftdiff and ftview.
Interestingly, ftview does show the subscript and superscript glyphs;
with ftview the glyphs also disappear when using ft's
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 Mi
> 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?
Actually here is a better design: at the point of discovery, set a flag in
the FT_Face structure. That way, there is no interference between a non-zero
error code and the opportunity for the caller to ignore the problem.
Graham
-Original Message-
From: Werner LEMBERG [mailto:[EMAIL PROTEC
> 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
Hi,
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.
I think MingLiU is a commercial font bundled to Microsoft
Windows, and Mozilla
It is dependent with how the ligature is specified.
If the ligature is specified by the Adobe Glyph Name
and the font resource is PostScript (Type1 or CFF),
FreeType2 supports it.
If the ligature glyph is specified by OpenType
technology, and it is expected that automatic substitution
from a serie
Does the Freetype support the ligature of the Opentype ?
If not, how can I display the ligature?
For example “fi”、”ff” and so on.
Thanks very munch!
Bigpin
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailma
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.
Graham
-Original Message-
From: [EMAIL PROTECTED]
[
> 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
20 matches
Mail list logo
