[Bug 106] freetype-2.1.3

Bruce Dubbs bdubbs at swbell.net
Wed Jan 8 07:25:56 PST 2003


Jeroen Coumans wrote:

>On Tuesday 07 January 2003 23:43, Bruce Dubbs wrote:
>  
>
>>It makes the BLFS instructions mor clear, but makes the ftoption.h
>>file much less clear.  There are many comments describing the options
>>in the file and this moves definitions to a different place.  I did
>>consider an append, but decided against it for that reason.
>>    
>>
>
>Yes I see your point. 
>
>  
>
>>As far as the BYTECODE option goes, there seems to be a difference of
>>opinion.  I think I'll leave it in for now.  I may consider putting
>>in a note that some people will find leaving it out to give better
>>rendering. Any suggestions for wording?
>>    
>>
>
>"Please note that as of version 2.1.3, the freetype project recommends 
>not to enable the bytecode interpetrer. Not only does it violate 
>pattents but most fonts are actually better rendered with freetype's 
>native auto-hinter." Or use the text as it appears in 
>http://www.freetype.org/hinting/smooth-hinting.html#bytecode
>

Reading the above link has persuaded me that the book should not set the 
BTYECODE option.  I will remove it and put in a note why some users may 
want to use it.

  --- Bruce

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-dev' in the subject header of the message



More information about the blfs-dev mailing list