FAQ change wrt FontForge

[Vitaliy Margolen]

Francois Gouget wrote:
> On Thu, 13 Nov 2008, Wine Wiki  wrote:
> [...]
>> - Unless you plan to work on the TrueType fonts you don't need 
>> FontForge. If you do, then be aware that the FontForge packages from 
>> Breezy and Dapper are a bit out of date. The fonts generated by most 
>> versions of FontForge will not pass the gdi32/tests/fonts.c tests.
>> + Be aware that the FontForge packages from Breezy and Dapper are a 
>> bit out of date. The fonts generated by most versions of FontForge 
>> will not pass the gdi32/tests/fonts.c tests.
> [...]
>> - Note that, unless you are tracking Git and know what you are doing, 
>> you SHOULDN'T have valgrind. Also, unless you plan to work on the 
>> TrueType fonts you don't need FontForge.
>> + Note that, unless you are tracking Git and know what you are doing, 
>> you SHOULDN'T have valgrind.
> [...]
>> - Unless you plan to work on the TrueType fonts you don't need FontForge.
> [...]
>> - * The following, but ''only'' if you plan to work on the TrueType 
>> fonts, and can install them from ''testing'' - '''do not''' install 
>> these from ''Sarge'':
>> +  * '''Do not''' install these from ''Sarge'':
>>     * fontforge/testing
> 
> I think these changes are wrong. As far as I know the TrueType fonts are 
> checked into Git so one does not need to have FontForge to build Wine. 
> Or has this changed? Or is FontForge needed to build another type of 
> fonts?
> 

Yes, you right. I totally forgot that we added .ttf fonts to git. I'll fix
the required packages page.

Vitaliy.