Word 2003 fails when opening html containing font with face Fixeds

V

vej

I have fresh Windows XP(prof) with Office 2003. I try to open html file with
following contents:

<html><body><font FACE="Fixedsys">Hello</font></body></html>

Word fails because of problems with font Fixedsys. When i use other font
(for example Arial), then all is OK. It looks as if word tries a sytem call
(e.g. CreateFont) which returns unsuccessfull return (NULL), but word does
not check it and uses it as handle. But when I tried
CreateFont(..."Fixedsys"...) from my own program it succeeded. Therefore it
is probably other font function that fails. In any case it looks like Word
2003 problem, because Word 2000 worked ok.

The question is whether we must wait for word patch or whether is possible
to do some system workaround (e. g. font substitution or something like that)
that will help word cope with this situation.
 
B

Bob Buckland ?:-\)

Hi Vej,

Using the small HTML file sample in your message as
a separate .htm file I didn't have a problem opening
it in Word 2003.

Do you have a printer selected in File=>Print in Word?

The Fixedsys font is a non truetype, screen display font, not supported
by MS Word with the possible exception of when the
Generic/Text printer choice is selected in File=>Print.
http://support.microsoft.com/default.aspx?scid=kb;en-us;291354&FR=1

Tools=>Options=>Compatability should show that as substituted
by Times New Roman for display purposes in Word.

========
I have fresh Windows XP(prof) with Office 2003. I try to open html file with
following contents:

<html><body><font FACE="Fixedsys">Hello</font></body></html>

Word fails because of problems with font Fixedsys. When i use other font
(for example Arial), then all is OK. It looks as if word tries a sytem call
(e.g. CreateFont) which returns unsuccessfull return (NULL), but word does
not check it and uses it as handle. But when I tried
CreateFont(..."Fixedsys"...) from my own program it succeeded. Therefore it
is probably other font function that fails. In any case it looks like Word
2003 problem, because Word 2000 worked ok.

The question is whether we must wait for word patch or whether is possible
to do some system workaround (e. g. font substitution or something like that)
that will help word cope with this situation. >>
--
Let us know if this helped you,

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top