Missing fonts

["Alexander N. Sørnes"]

Hello,

I have found some font problems recently with Wine.  First of all, the 
text of most richedit objects started displaying as rectangles since 
around Wine 0.9.9, and now, with current CVS, no text is displayed in 
applications witht the standard Windows interface (like winecfg, 
wordpad, message boxes etc.) on some systems.
While the first issue occurs on all systems I have tested, the second 
one does not.  On a system with only the free corefonts installed, the 
text is missing; while on a system with all Windows/MS Office fonts, it 
is displayed fine.
What are the new default fonts?  Is the first system misconfigured, or 
does Wine only use non-downloadable Windows fonts now?

Regards,

Alexander N. Sørnes

[Vitaliy Margolen]

Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
> Hello,
> I have found some font problems recently with Wine.  First of all, the 
> text of most richedit objects started displaying as rectangles since 
> around Wine 0.9.9, and now, with current CVS, no text is displayed in 
> applications witht the standard Windows interface (like winecfg, 
> wordpad, message boxes etc.) on some systems.

[skip]

I'm sorry, but are you reading this mailing list at all? To sum it up:
1. You need fontforge.
2. You need _working_ fontforge.
3. You need Wine's fonts made with working fontforge.

Same thing for freetype.

Vitaliy

["Alexander N. Sørnes"]

Vitaliy Margolen skrev:
> Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
>
> I'm sorry, but are you reading this mailing list at all? To sum it up:
> - You need fontforge.
> - You need _working_ fontforge.
> - You need Wine's fonts made with working fontforge.
>
> Same thing for freetype.
>
> Vitaliy

First of all, I am very sorry if I sent a message in ignorance.  But 
wasn't the FontForge stuff introduced before 0.9.11?  Compiling and 
running 0.9.11 works fine, but doing the same for CVS does not.
>

["Alexander N. Sørnes"]

Vitaliy Margolen skrev:
> Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
>
> I'm sorry, but are you reading this mailing list at all? To sum it up:
> - You need fontforge.
> - You need _working_ fontforge.
> - You need Wine's fonts made with working fontforge.
>
> Same thing for freetype.
>
> Vitaliy

First of all, I am very sorry if I sent a message in ignorance.  But
wasn't the FontForge stuff introduced before 0.9.11?  Compiling and
running 0.9.11 works fine, but doing the same for CVS does not.
>

["Alexander N. Sørnes"]

Vitaliy Margolen skrev:
> Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
>
> I'm sorry, but are you reading this mailing list at all? To sum it up:
> - You need fontforge.
> - You need _working_ fontforge.
> - You need Wine's fonts made with working fontforge.
>
> Same thing for freetype.
>
> Vitaliy

First of all, I am very sorry if I sent a message in ignorance.  But
wasn't the FontForge stuff introduced before 0.9.11?  Compiling and
running 0.9.11 works fine, but doing the same for CVS does not.
>

[Alexander Nicolaysen Sørnes]

Vitaliy Margolen skrev:
> Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
>
> I'm sorry, but are you reading this mailing list at all? To sum it up:
> - You need fontforge.
> - You need _working_ fontforge.
> - You need Wine's fonts made with working fontforge.
>
> Same thing for freetype.
>
> Vitaliy

First of all, I am very sorry if I sent a message in ignorance.  But
wasn't the FontForge stuff introduced before 0.9.11?  Compiling and
running 0.9.11 works fine, but doing the same for CVS does not.
>

[Tomas Carnecky]

Alexander Nicolaysen Sørnes wrote:
> Vitaliy Margolen skrev:
> > Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
> >
> > I'm sorry, but are you reading this mailing list at all? To sum it up:
> > - You need fontforge.
> > - You need _working_ fontforge.
> > - You need Wine's fonts made with working fontforge.
> >
> > Same thing for freetype.
> >
> > Vitaliy
>
> First of all, I am very sorry if I sent a message in ignorance.  But
> wasn't the FontForge stuff introduced before 0.9.11?  Compiling and
> running 0.9.11 works fine, but doing the same for CVS does not.

I had the same problem. You need a newer fontforge, mine was from
2005???? (from the official gentoo portage tree) and updating to
200604?? solved the problem.

tom

[Tomas Carnecky]

Vitaliy Margolen wrote:
> Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
> > Hello,
> > I have found some font problems recently with Wine.  First of all, the 
> > text of most richedit objects started displaying as rectangles since 
> > around Wine 0.9.9, and now, with current CVS, no text is displayed in 
> > applications witht the standard Windows interface (like winecfg, 
> > wordpad, message boxes etc.) on some systems.
>
> [skip]
>
> I'm sorry, but are you reading this mailing list at all? To sum it up:
> - You need fontforge.
> - You need _working_ fontforge.

maybe the configure script should check the fontforge version, to be at
least from 2006.
My fontforge: "Executable based on sources from 20:17 6-Apr-2006-ML.".
Checking for "Executable based on sources from (.+) (.+)-(.+)-2006" in
`fontforge --version` should be enough.

tom

[Mike McCormack]

Tomas Carnecky wrote:
> maybe the configure script should check the fontforge version, to be at
> least from 2006.
> My fontforge: "Executable based on sources from 20:17 6-Apr-2006-ML.".
> Checking for "Executable based on sources from (.+) (.+)-(.+)-2006" in
> `fontforge --version` should be enough.

The configure tests should test the capability of FontForge to build 
fonts as Wine requires them, not for a specific version.

I think a better solution is sfd2ttd, but it might be a while before 
somebody gets around to implementing that.

Mike

[Kai Blin]

* Mike McCormack  [10/04/06, 21:23:21]:
> > maybe the configure script should check the fontforge version, to be at
> > least from 2006.
> > My fontforge: "Executable based on sources from 20:17 6-Apr-2006-ML.".
> > Checking for "Executable based on sources from (.+) (.+)-(.+)-2006" in
> > `fontforge --version` should be enough.
>
> The configure tests should test the capability of FontForge to build 
> fonts as Wine requires them, not for a specific version.

I agree here. Unlike Gentoo users, I don't get regular package version
updates in my distribution, so I still have a fontforge 20050803, which
seems to work just fine. This would fail the configure check proposed in
an earlier mail. Unless someone really wants to test at exactly which
day fontforge started doing the things wine needs, the configure check
has to check for capabilities. This has the upside of being extensible
should our requirements change.

Cheers,
Kai

[Tomas Carnecky]

Mike McCormack wrote:
> Tomas Carnecky wrote:
> > maybe the configure script should check the fontforge version, to be at
> > least from 2006.
> > My fontforge: "Executable based on sources from 20:17 6-Apr-2006-ML.".
> > Checking for "Executable based on sources from (.+) (.+)-(.+)-2006" in
> > `fontforge --version` should be enough.
>
> The configure tests should test the capability of FontForge to build
> fonts as Wine requires them, not for a specific version.
>
> I think a better solution is sfd2ttd, but it might be a while before
> somebody gets around to implementing that.

At least now this information is in the README file, I saw the patch
just after I've sent that email :)

tom

[Kai Blin]

* Tomas Carnecky  [10/04/06, 15:01:00]:
> At least now this information is in the README file, I saw the patch
> just after I've sent that email :)

It's not. Alexandre convinced me that the README file is the wrong place
for it. Configure warns you about a missing fontforge, that will be
enough. fontforge isn't a hard dependency.

Cheers,
Kai

[Tomas Carnecky]

Kai Blin wrote:
> - Tomas Carnecky  [10/04/06, 15:01:00]:
> > At least now this information is in the README file, I saw the patch
> > just after I've sent that email :)
>
> It's not. Alexandre convinced me that the README file is the wrong place
> for it. Configure warns you about a missing fontforge, that will be
> enough. fontforge isn't a hard dependency.

It's not the missing fontforge I'm worried about, it's the incompatible
fontforge that creates unusable fonts. In that case I'd rather see wine
skip the fonts/ directory and don't create/install any fonts.

A quick font test before 'make' installs the fonts would help here
(given that this would do 'make' itself before installing the fonts).

tom

[Vitaliy Margolen]

Monday, April 10, 2006, 6:13:24 AM, Tomas Carnecky wrote:
> Vitaliy Margolen wrote:
> > Sunday, April 9, 2006, 4:15:22 PM, Alexander N. Sørnes wrote:
> > > Hello,
> > > I have found some font problems recently with Wine.  First of all, the
> > > text of most richedit objects started displaying as rectangles since 
> > > around Wine 0.9.9, and now, with current CVS, no text is displayed in
> > > applications witht the standard Windows interface (like winecfg, 
> > > wordpad, message boxes etc.) on some systems.
> >
> > [skip]
> >
> > I'm sorry, but are you reading this mailing list at all? To sum it up:
> > - You need fontforge.
> > - You need _working_ fontforge.
> maybe the configure script should check the fontforge version, to be at
> least from 2006.
> My fontforge: "Executable based on sources from 20:17 6-Apr-2006-ML.".
> Checking for "Executable based on sources from (.+) (.+)-(.+)-2006" in
> `fontforge --version` should be enough.
> tom

$fontforge --version
Copyright (c) 2000-2005 by George Williams.
 Executable based on sources from 13:45 3-Aug-2005.
fontforge 20050803

Works fine here. So limiting to 2006 only will brake number of other
distros.

Vitaliy

[Dmitry Timoshkov]

"Vitaliy Margolen"  wrote:
> $fontforge --version
> Copyright (c) 2000-2005 by George Williams.
> Executable based on sources from 13:45 3-Aug-2005.
> fontforge 20050803
>
> Works fine here.

Does 'make test' in dlls/gdi pass as well?

[Vitaliy Margolen]

Monday, April 10, 2006, 6:57:13 AM, Dmitry Timoshkov wrote:
> "Vitaliy Margolen"  wrote:
> > $fontforge --version
> > Copyright (c) 2000-2005 by George Williams.
> > Executable based on sources from 13:45 3-Aug-2005.
> > fontforge 20050803
> >
> > Works fine here.
> Does 'make test' in dlls/gdi pass as well?

Hmm I guess it doesn't work then:
font.c:277: Test failed: Courier(13): tm.tmAscent 10 != 11
font.c:278: Test failed: Courier(13): tm.tmDescent 3 != 2

But at least I have fonts, broken but visible. Which is better then
err, none at all. <g>

Vitaliy

[Dmitry Timoshkov]

"Vitaliy Margolen"  wrote:
> > Does 'make test' in dlls/gdi pass as well?
>
> Hmm I guess it doesn't work then:
> font.c:277: Test failed: Courier(13): tm.tmAscent 10 != 11
> font.c:278: Test failed: Courier(13): tm.tmDescent 3 != 2
>
> But at least I have fonts, broken but visible. Which is better then
> err, none at all. <g>

Ok, let it be a hint then for anyone interested to detect broken
fontforge versions.

[Huw D M Davies]

On Mon, Apr 10, 2006 at 07:19:46AM -0600, Vitaliy Margolen wrote:
> Monday, April 10, 2006, 6:57:13 AM, Dmitry Timoshkov wrote:
> Hmm I guess it doesn't work then:
> font.c:277: Test failed: Courier(13): tm.tmAscent 10 != 11
> font.c:278: Test failed: Courier(13): tm.tmDescent 3 != 2

I think Courier should now be built correctly even for older versions
of fontforge.  Could you try make clean && make in fonts/ and also
check that you don't have coure.fon installed somewhere else on your
system.

Huw.

[Eric Pouech]

Dmitry Timoshkov wrote:
> "Vitaliy Margolen"  wrote:
> > $fontforge --version
> > Copyright (c) 2000-2005 by George Williams.
> > Executable based on sources from 13:45 3-Aug-2005.
> > fontforge 20050803
> >
> > Works fine here.
>
> Does 'make test' in dlls/gdi pass as well?

The test fails if you have some other fonts installed.
A+

[Dmitry Timoshkov]

"Eric Pouech"  wrote:
> > Does 'make test' in dlls/gdi pass as well?
>
> The test fails if you have some other fonts installed.

I think that's expected, running tests with native libraries (and the fonts
are the libraries) is not guaranteed to pass due to font substitution.

[Eric Pouech]

Dmitry Timoshkov wrote:
> "Eric Pouech"  wrote:
> > > Does 'make test' in dlls/gdi pass as well?
> >
> > The test fails if you have some other fonts installed.
>
> I think that's expected, running tests with native libraries (and the fonts
> are the libraries) is not guaranteed to pass due to font substitution.

the main question remains:
- should the wine's default fonts override any other fonts ?

the default for DLLs is: use builtin DLLs
the default for fonts is: use installed (native) fonts

I fail to see the logic here. If Wine ships its own fonts, then the 
default should be to use them. Period.

A+

[Huw D M Davies]

On Mon, Apr 10, 2006 at 04:01:55PM +0200, Eric Pouech wrote:
> Dmitry Timoshkov wrote:
> > Does 'make test' in dlls/gdi pass as well?
>
> The test fails if you have some other fonts installed.

It shouldn't.  Could you debug what's going on?  We should only be
running the tests if EnumFonts finds these specific fonts.

Huw.

[Eric Pouech]

Huw D M Davies wrote:
> On Mon, Apr 10, 2006 at 04:01:55PM +0200, Eric Pouech wrote:
> > Dmitry Timoshkov wrote:
> > > Does 'make test' in dlls/gdi pass as well?
> >
> > The test fails if you have some other fonts installed.
>
> It shouldn't.  Could you debug what's going on?  We should only be
> running the tests if EnumFonts finds these specific fonts.

basically, what happens:
- if I remove every font related entry from the registry, the test
runs fine
- but it only runs once fine, the second time it fails

what happens is that I have (in c:\windows\fonts) installed the fonts 
from an existing windows setup, and those fonts get priority over the 
ones coming from wine

IMO, this is a wrong behavior. Wine's own font should get priority over 
any other ones.

A+

[Huw D M Davies]

On Mon, Apr 10, 2006 at 04:33:10PM +0200, Eric Pouech wrote:
> Huw D M Davies wrote:
> > On Mon, Apr 10, 2006 at 04:01:55PM +0200, Eric Pouech wrote:
> > > Dmitry Timoshkov wrote:
> > > > Does 'make test' in dlls/gdi pass as well?
> > >
> > > The test fails if you have some other fonts installed.
> >
> > It shouldn't.  Could you debug what's going on?  We should only be
> > running the tests if EnumFonts finds these specific fonts.
>
> basically, what happens:
> - if I remove every font related entry from the registry, the test
>
> runs fine
> - but it only runs once fine, the second time it fails
>
> what happens is that I have (in c:\windows\fonts) installed the fonts 
> from an existing windows setup, and those fonts get priority over the 
> ones coming from wine
>
> IMO, this is a wrong behavior. Wine's own font should get priority over 
> any other ones.

Ah, the Windows fonts are failing because when Dmitry wrote the test
he was using a Russian locale and the metrics are slightly different
from a latin-1 set.  We do indeed need to fix this.

Having Windows fonts take priority is actually a feature - they have
more strikes and better glyph coverage.

Huw.

[Segin]

Alexander N. Sørnes wrote:
> Hello,
>
> I have found some font problems recently with Wine.  First of all, the 
> text of most richedit objects started displaying as rectangles since 
> around Wine 0.9.9, and now, with current CVS, no text is displayed in 
> applications witht the standard Windows interface (like winecfg, 
> wordpad, message boxes etc.) on some systems.
> While the first issue occurs on all systems I have tested, the second 
> one does not.  On a system with only the free corefonts installed, the 
> text is missing; while on a system with all Windows/MS Office fonts, 
> it is displayed fine.
> What are the new default fonts?  Is the first system misconfigured, or 
> does Wine only use non-downloadable Windows fonts now?
>
> Regards,
>
> Alexander N. Sørnes

I found a solution, not very good but it works:

open regedit
Delete HKEY_CURRENT_CONFIG\Fonts\
Delete HKEY_USERS\S-1-5-4\Software\Wine\Fonts\External Fonts\

An indication that it works is that the following doesn't come up as all 
blocks:
wineconsole --backend=user wcmd

[Felix Möller]

Hi,
> I have found some font problems recently with Wine.  First of all, the 
> text of most richedit objects started displaying as rectangles since 
> around Wine 0.9.9, and now, with current CVS, no text is displayed in 
> applications witht the standard Windows interface (like winecfg, 
> wordpad, message boxes etc.) on some systems.
> While the first issue occurs on all systems I have tested, the second 
> one does not.  On a system with only the free corefonts installed, the 
> text is missing; while on a system with all Windows/MS Office fonts, it 
> is displayed fine.
> What are the new default fonts?  Is the first system misconfigured, or 
> does Wine only use non-downloadable Windows fonts now?

I think I have the same problem since arround wine 0.9.9.  I am trying 
to use Derive 6.10.

The text in the input field is not displayed correctly any more.  But in 
the textarea it gets displayed correct again.

I uploaded a screenshot at http://hebbelabi06.de/derive.png.

Sadly I do not have the time to investigate this at the moment.

I do have fontforge installed:
# rpm -qa | grep fontforge
fontforge-20050803-2

HTH

Felix Möller