FAQ change wrt FontForge

[Francois Gouget]

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?

[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.

[James McKenzie]

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. 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.

Vitally:

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.

James McKenzie

[Dmitry Timoshkov]

"James McKenzie"  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?
> >
> > Yes, you right. I totally forgot that we added .ttf fonts to git. I'll fix
> > the required packages page.
>
> Vitally:
>
> 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.

Then you need to fix that on the Darwine side.

[Francois Gouget]

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 TTF fonts?
Can you point to a Wine build issue caused by missing FontForge on 
the Mac?

[James McKenzie]

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?

Fracois:

FontForge is required to build Darwine.  MacOSX does not come with the
necessary parts to support TrueType fonts.

James McKenzie