Re: [ft-devel] Force PMingLiU like font do HINTING

[mpsuzuki]

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 can use Microsoft's TrueType rasterizer
supporting patented hinting technology. If there is a case that
the tricky application of unpatented hinting of FreeType2 to
MingLiU, please let me know.

Regards,
mpsuzuki


On Thu, 4 Dec 2008 09:04:18 -0000
"Graham Asher" <address@hidden> wrote:

>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: address@hidden
>[mailto:address@hidden On
>Behalf Of Werner LEMBERG
>Sent: 04 December 2008 08:06
>To: address@hidden
>Cc: address@hidden
>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 to ignore FT_LOAD_NO_HINTING.
>
>This is a fundamental question.  My opinion is that shifting of glyph
>elements using TrueType instructions clearly is (a kind of) hinting.
>In other words, I don't like to change the current behaviour of
>FreeType without good reasons.
>
>However, it might be helpful if FreeType emits a warning message that
>the font is probably unusable.  Hmm.
>
>Opinions, please.  Maybe most of you disagree, so please chime in.
>
>
>> And detecting of tricky font should be outside of this defines:
>>
>>     #if defined( TT_CONFIG_OPTION_UNPATENTED_HINTING    ) && \
>>         !defined( TT_CONFIG_OPTION_BYTECODE_INTERPRETER )
>>
>> otherwise, the fonts are not detected on my debian box.
>
>This is probably fixed already in the CVS:
>
>  2008-11-05  Werner Lemberg  <address@hidden>
>
>    * devel/ftoption.h, include/freetype/config/ftoption.h
>      [TT_CONFIG_OPTION_BYTECODE_INTERPRETER]: Undefine
>      TT_CONFIG_OPTION_UNPATENTED_HINTING.  This fixes the return
>      value of `FT_Get_TrueType_Engine_Type' (and makes it work as
>      documented).  Reported in bug #441638 of bugzilla.novell.com.
>
>Please test.  Otherwise, please report the vales of those two macros
>on your box.
>
>
>    Werner
>
>
>_______________________________________________
>Freetype-devel mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/freetype-devel
>
>
>
>_______________________________________________
>Freetype-devel mailing list
>address@hidden
>http://lists.nongnu.org/mailman/listinfo/freetype-devel