On Sun, 23 Nov 2008, James McKenzie wrote:
[...]
> I think that FontForge is still needed for the Darwine Build. Some of
> the problems related to Vanilla Wine builds on the Mac Intel platform
> may be related to the lack of FontForge on the Mac.
What is it used for? Do you have Darwine-specific
"James McKenzie" <[EMAIL PROTECTED]> wrote:
>>> 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?
>>>
>>>
>>
Vitaliy Margolen wrote:
> 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.
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
>> versio
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
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 gd
