Can I ask you for more detail on the "Word doesn't even get that far"
comment? I can open every single one of these pages with Word97, and they
display properly. The only exception is the UTF-8 page, where Word's
default fonts are used for display since there is no font tag to switch the
fonts in the HTML. Since the English version of Word97 has no default font
set for Asian languages, and none is set in the HTML, you have to apply the
appropriate font by hand.

One other thing that Word does not do is determine of some text is
Traditional or Simplified Chinese, or Japanese. These are unified ranges,
so without a font tag, it cannot pick a font that is appropriate for that
text.

More information on your system configuration and what language packs if
any you have installed would be appreciated.

(Note that I am using Japanese Word97, so its default configuration is
better suited to viewing Asian languages than US Word97, which may explain
some differences in your experience)

These work excellently, for the most part, with MSIE 3.0. After
loading them, I could view the separate announcements in Simplified
and Traditional Chinese, Japanese, and Romanian. However, the Russian
page didn't work at all, and I'm not sure why. The Central European
service pack includes several Cyrillic fonts, which I believe are
encoded as ISO 8859-5, but MSIE 3.0 doesn't appear to recognize that
encoding declaration. It also can't deal with the all-language pages
in either UTF-8 or NCRs.

Does anyone have an explanation of how MSIE is able to convince the OS
to deal with these encodings, especially the non-8859 ones? WordPad
can differentiate between the differently encoded fonts, but Word
doesn't even get that far. I'd like to be able to take advantage of
this capability, but I can't figure out what it's doing. More
monopolistic practices, I suspect...