154123 - My mozilUlead Photo Express hijacks font settings

Status: RESOLVED INVALID

(Core :: Layout: Text and Fonts, defect)

Description

[Steven Neil Groginsky]

I am running Callwave while on-line.  Callwave has installed a bunch of fonts. 
I think I'm picking up one of them in form entry boxes.

I moved the fonts to another folder, but Callwave reinstalled them in the Fonts
folder.

Win 98se, Build 2002061104, mem 256MB

Comment 1

[R.K.Aa.]

Which font might that be? And which font is set in "Windows and Prefs"?

Comment 2

[Steven Neil Groginsky]

The font that is coming up (even right here in Additinal Comments) is some kind
of cursive - I don't know specifically what it is because I havent set it
anywhere.  This same thing happenned last month with Chris Pirillo font, and
resolved when I deleted the font.  Now I suspect Callwave, and I suspect
Callwave put the fonts back in the fonts folder after I moved them to another
folder.  I had an involuntary software update of Callwave recently while I was
online.

I have identified the font.  It is Surfer Normal, a True-Type font, sligtly
cursive, Version Altsys Fontographer 4.1, 1/10/95, copyright 1994 Bay Animation Inc.

Fonts Set in Preferences
Fonts for Western:
Proportional: Sans Serif
Serif: Times New Roman
Sans Serif: MS Sans Serif
Cursive: no fonts available for...
Fantasy: no fonts available for...
Monospace: Elronet Monospace (Hebrew/English font)

Comment 3

[Boris Zbarsky [:bzbarsky]]

sounds like a system fonts problem...

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

Or a problem in the Windows system fonts code, perhaps?

Comment 5

[Steven Neil Groginsky]

I have to come to the conclusion then that some program that I run is holding
the fonts in some container file (I can't find them by name), keeping them in
the fonts folder and telling the operating system to use them.  I don't see
anything in the Callwave folder except maybe the executable.  Callwave on-line
help doesn't mention fonts.  However, the Callwave box title uses one of the fonts.

I will cntinue to try to isolate the problem on my system.  I hope it isn't
Callwave, because I would guess it's a pretty popular program.

Comment 6

[Steven Neil Groginsky]

I found the culprit.  Ulead Photo Express installed a startup item that
apparently manages the fonts.  So I'm disabling it.  That takes care of this bug.

- eventualy when someone has some time to blow they might think of using their
own code to do forms insead of Microsoft code -

Sorry for the mistaken bug.
Steve

Comment 7

[Boris Zbarsky [:bzbarsky]]

From bug 155055:

Sorry I couldn't find the original bug.
This was not an OS problem.  The reason I was getting weird fonts in text entry
boxes was because somehow the user-defined font setup in prefs got set to weird
fonts installed during an involuntary online update by Callwave which installed
about 20 different fonts.

When I set user-defined to something I wanted, it was set and has stayed set.
build 2002061104 on win98se.

I seriously doubt that callwave has targeted or programmed for Mozilla for this
stuff and I don't understand how user-defined got set.

Comment 8

[Boris Zbarsky [:bzbarsky]]

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

Comment 9

[Steven Neil Groginsky]

As you see, I forgot that it is Ulead Photo Express that installed all the fonts
in the first place, not Callwave at all.

I still am absolutely certain that the Ulead installer did not do anything to
the Moz prefs.

I would hazard a guess that it has something to do with the Moz user-defined
font defaults in Prefs as set up by Moz when installed.

Let me be absolutely clear that these fonts were installed by Ulead, I'm not
sure before or after I installed Moz 1.1.  Maybe it does have something to do
with the OS AND how installed Moz Prefs user-defined fonts works.

Comment 10

[Kai Lahmann (is there, where MNG is)]

Reporter: Can you reproduce this bug with a recent build of Mozilla (for
example, 1.4 RC1)? If so, then please comment again with details. If not, then
please resolve this bug as WORKSFORME. Thanks.

Comment 11

[Christopher Hoess (gone)]

Resummarizing, although I doubt this is really our bug.

Comment 12

[Asa Dotzler [:asa]]

Without specific steps to reproduce this problem and confirmation that it is
indeed a Mozilla problem (and not some other application at fault) this bug
isn't particularly useful. Please reopen if you can provide specific steps to
reproduce the problem. Thanks.