Created attachment 2205 [details]
Complete make output for font compile issues

Here is the make output captured during creation of fonts. Are these errors
significant, and if so, can they be resolved?

Updated to fontforge 20060114 and cvs wine, but same results. The program
../tools/sfnt2fnt continues to complain about missing glyphs and seems to be
unable to generate a proper, usable font.

Created attachment 2210 [details]
courier.ttf sample

Missing glyphs don't seem to be the problem unless you use those characters. See
bug 4662 for some recent history on font problems.
Also see #14 that the fontconfig may have a bug.
and then #30 to #34

upgraded fontconfig to cvs. Still no usable system fonts in notepad. Truetype
fonts OK. FONts are not. Is there a version of wine I could regress to that
would work. 

The fontforge warnings are normal.  You can submit patches to add the missing
glyphs if you feel the need, but it should generate a valid .ttf and .fon files
anyway.

You seem to have some other problem... which system are you building Wine on? 
Are you sure you don't have the wrong version of Wine installed?

Can you describe how to make the problem appear in Notepad?  Is it as simple as
just loading a random text file?

Yes. It is as simple as loading notepad and starting to type. I also updated to
fontconfig 2.3.94 cvs bc there was a note somewhere that it caused a bug in
wine. But same result. See the screenshots on bug #4701
http://bugs.winehq.com/attachment.cgi?id=2203&action=view  which you also nicely
replied to, Mike. Any fon file is unreadable. I compiled on Gentoo using kernel
2.6.15. This is a recent problem, and I'm afraid I can't remember in which
version this problem began, but it was very recent. I first noticed it in a data
entry box which used the System font. I am going to start going backwards with
wine and see if I can trace it down to a specific version. I will report back
when I can find the version it last worked in.

> I compiled on Gentoo

I have short patience with Gentoo.  It seems Gentoo users seem to be able to get
themselves into lots of trouble.

I suggest you try it on a binary only distribution.  If it works, you'll know
that you've messed up the compilation somehow.

I'll keep you advised! And, I do understand your comment! Many moving parts --
although this is a new one, even to me.

Notepad works on 0.9.7. Programs that use dialog with System font show
correctly. Default font is Andale Mono, but Wine System font also works with a
font of 12 or larger. No characters with under 12 point.

Created attachment 2212 [details]
Notepad Font Selection 1 (0.9.7)

Created attachment 2213 [details]
Notepad Font Selection 2 (0.9.7)

0.9.9 OK

Problem occurs with 0.9.10. First default font is System. System.fon has no
usable characters init. Prior versions had a different font first AD Mono.

Created attachment 2215 [details]
Notepad Font Selection 3 (0.9.10)

Could you please do regression testing and find what patch broke it?
Also make sure that you _install_ Wine. Or copy all of the Wine's *fon files
into ~/.wine/drive_c/windows/fonts dir (NOT *ttf files!)

Ah. I did not copy .fon files, nor did I use wineinstall. I will try that and
review the results and report. Thank you.

OK. As I noted, the problem begins with wine 0.9.10. Copying the
/usr/share/wine/fonts/*fon files to ...../windows/fonts had exactly the same
effect as when they were in their original installed directory. Furthermore,
after I regressed again to 0.9.9, leaving the fonts alone, the same error
occured. So, it appears that the font generation process is what is going wrong
for me, not wine's ability to locate a font.
fontconfig 2.3.2
fontforge 20050502

Anything else I can try?

Created attachment 2218 [details]
svgasys.fon file created by wine 0.9.11

the only font files that have what look like usable data (per fontforge) are:
ssee*fon
sserif*fon
The rest are all unreadable little squres.

It appears wine requires a newer version of fontforge. However, in configure.ac
there is no test for a particular version. Thus, if fontforge 20050502 is
installed, configure will not complain, but wine > 0.9.9 will not create usable
fonts. Therefore, it appears the resolution is to add a test to configure.ac so
that the output of fontforge --version contains 2006. This bug is resolved when
wine > 0.9.9 is built with fontforge 20060114 installed.

A simple test like this works:

# if fontforge --version | grep 2006; then echo "OK"; fi

Not sure of the best way to accomplish this in configure.ac. However, some kind
of test must be done.

*** Bug 5244 has been marked as a duplicate of this bug. ***

*** Bug 5316 has been marked as a duplicate of this bug. ***

Unreadable font selected by default after installation.

This bug occurs in PAF 5.2 running in Wine 0.9.14. If a developer discovers that these are different 
bugs, I won't mind if they are separated.

There is a jackpot available to whomever fixes this bug so that a readable font is selected in PAF 5.2 by 
default after installation.

http://www.eagargospelstudy.org/paf/

Ubuntu 6.06 RC with all updates as of May 29, 2006 running Wine 0.9.14.

1. Download PAF 5.2 from http://www.familysearch.org/eng/home/welcome/pafDownload.asp
2. Install PAF by running 'wine PAF5EnglishSetup.exe'
3. During installation keep default settings except:
 - Uncheck 'View 'Getting Started' document now.' 
 - Uncheck 'Place a shortcut to PAF on your desktop.'
 - Select 'No, I will restart my computer later.'
4. If the installation crashes while copying files, repeatedly rerun the installation until it finishes. It took 
me four times to get it installed. See bug 5251.
5. Run 'wine ~/.wine/drive_c/Program\ Files/FamilySearch/Paf5/paf5.exe'.
6. Notice that the fonts are not readable.
7. Close the welcome window by clicking the X in the title bar.
8. Click the menu item Tools. In windows it is the sixth out of ???? menu items. In wine it is the third out 
of four menu items.
9. Click the last menu sub item, 'Preferences'.
10. Close the popup window by clicking the X in the title bar.
11. Click the fourth tab 'Fonts'. In Windows XP it is the sixth tab.
12. Click each of the four buttons on the right 'Change'.
13. Notice that the font 'TAMu_Kalyani' is selected.
14. In Windows, the default fonts are as follows.
 - Main Screen - Microsoft Sans Serif Normal 11pt
 - Dialogs - Microsoft Sans Serif SemiBold 8pt
 - Notes Edit Screen - Microsoft Sans Serif Normal 9pt
 - Microsoft Sans Serif Normal 9pt
15. Select FreeSans.
16. Click the the top button on the right 'OK'.
17. Click the left button on the bottom 'OK'.

When the font 'Microsoft Sans Serif' is not available, it should default to something like 'FreeSans'.

Just discovered this error during make time of Wine 0.9.16 on Ubuntu 6.06. 
Guess it is the problem when some Chinese text displayed with system fonts are
shown with ||||.  Seriously looking forward to a solution.

Just discovered this error during make time of Wine 0.9.16 on Ubuntu 6.06. 
Guess it is the problem when some Chinese text displayed with system fonts are
shown with ||||.  Seriously looking forward to a solution.

This commit introduced this behaviour with earlier versions of fontforge:

commit 593665b6b9ecd7e149fe8e33f84f732d3c20914a
Author: Huw Davies <huw@codeweavers.com>
Date:   Tue Apr 4 20:46:55 2006 +0100

    fonts: Add a few missing glyphs.

:100644 100644 86c34f4... 9d7011f... M  fonts/ms_sans_serif.sfd

As fontforge support pkg-config, detecting the required version in configure.ac
should be trivial.  "$PKG_CONFIG --atleast-version=20060703 fontforge" should be
adequate after checks that pkg-config is present and sufficiently recent.  (The
version used here is the version I upgraded to after regression testing and
seems to work perfectly.  The tests were performed with 20050502.)

Could someone please verify whether the behavior described in comment #23 is a result of this bug? If the 
behavior is not a result of this bug, could you either log a new bug or just let me know so that I can log a 
bug on it?

In the first place the messages like "Missing glyph for char 0020" are not
the bugs unless you have an application that attempts to use a character
that is missing in the font. In that case you have to specify what exactly
the missing character is.

Some points:
1. bitmap font generation in Wine does depend on fontforge being installed,
and fontforge version should be recent enough to be able generate correct
Windows format bitmap fonts.
2. FreeType versions prior 2.1.9 have broken/incomplete support for Windows
format bitmap fonts, Wine disables bitmap font support if it detects an older
FreeType version.

I'm going to close this bug, if you have a real problem that is not caused
by the reasons listed above please open a new bug.

Thank you for your clarification. I suspected that this might not be the bug that I encountered in PAF. I will 
search for the correct bug and if I don't find anything I will submit a new bug.

Closing