any control settings in word for conversion to html

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ellen - 22 Feb 2005 22:21 GMT

I've had the question below asked of our area as we support microsoft office
xp. Is there information on what saving to html is supposed to be used for,
i.e. what the purpose is. It doesn't seem to be designed to use as a web
authoring tool.

In using send to html in word, word creates a whole bunch of styles in a
head tag. Our web site strips off the styles in head and body tags and loses
all formatting. Can word control how the coversion to html is done so the
formatting is retained?

I have found the save as filtered html and the options under tools, options,
general, web options but I'm not sure if any of these will address the issue.

Any clarafication would be appreciated.

Reply to this Message

lostinspace - 23 Feb 2005 11:26 GMT

Ellen,
You have multiple inquires here.
I've separated your inquires with a uppercase "REPLY" preceeding response.

----- Original Message -----
From: "Ellen" <Ellen@discussions.microsoft.com>
Newsgroups: microsoft.public.word.web.authoring
Sent: Tuesday, February 22, 2005 5:21 PM
Subject: any control settings in word for conversion to html

> I've had the question below asked of our area as we support microsoft
> office
> xp. Is there information on what saving to html is supposed to be used
> for,
> i.e. what the purpose is. It doesn't seem to be designed to use as a web
> authoring tool.

REPLY: The entire purpose of intent by MS in offfering html for Word was in
providing a transport medium to return web pages back into their original
Word format.
The good folks at MS have included some "depreciated" html in Word created
web pages for some time. (the bold font settings are one example; being
depreciated after versions 3.0 of both IE and Netscape. [note; even MS-Front
Page includes the use of same depreciated html.])

> In using send to html in word, word creates a whole bunch of styles in a
> head tag.

REPLY: One reason for excess in styles is that your are using too many font
variations.

>Our web site strips off the styles in head and body tags and loses
> all formatting.

REPLY: This FAULT is the choice of whoever configured the software on your
host/server. A website (or its software) should NOT remove anything from
html pages.
(that is "IF" you have full access and are not restricted to a configured
CMS portion?)

>Can word control how the coversion to html is done so the formatting is
>retained?

REPLY: Word cannot control anything outside it's boundaries. There are "Web
options" which does offer some effective settings changes to reduce the
standard Word "Bloat" in creating html.

> I have found the save as filtered html and the options under tools,
> options,
> general, web options but I'm not sure if any of these will address the
> issue.

REPLY: The Web Options will reduce some bloat. The only "pure" solution for
proper html is to NOT use Word to create web pages.

> Any clarafication would be appreciated.

REPLY: Clarification requests should be sent directly to Mr. Gates or the
the other guy in charge (Steve something.)
MS has done it's best to provide and HIDE the very minimum of explanation
for html pages in Word, when all-along the option should NEVER have been
included.

Most Word users have full faith in that, they believe Word has the ability
to do everything from changing diapers to reshingling the roof and anything
in between. These same users fall short in comprehending simple path
statements which are a necessity for creation of web pages.

The most effective policy statement MS made was when they separated the
Front Page module from the Office Suite.

Reply to this Message

Ellen - 23 Feb 2005 15:45 GMT

Thank you for the reply. That's what I thought but was unable to find the
information on Microsoft's site. I've found that they tend to hide it or
make it very difficult to find information.

> Ellen,
> You have multiple inquires here.
[quoted text clipped - 66 lines]
> The most effective policy statement MS made was when they separated the
> Front Page module from the Office Suite.

Reply to this Message

Rate this thread: