Word Includes--Pros and Cons?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I never insert material from Word directly into FrontPage because of all the
bloated code. I convert it to html and/or plain text first.
However, recently I tried using a Word document (with a lengthy table, no
less) as an include, and the result loads very fast. Why is this?
I ask not just out of curiosity but for future use. If I can use Word
materials as includes without sacrificing speed, I'll do it more often.
What should I know about this phenomenon?
 
Do you mean the source code within the include? It's a mess! (All that "mso"
stuff.) Should that concern me, if the containing page is clean?
 
yes that should concern you, it might not appear properly in some browsers.
The code is there there, no matter how it is included
 
Thanks. I'll have to be more careful.

Corey Bryant said:
yes that should concern you, it might not appear properly in some browsers.
The code is there there, no matter how it is included
 
Mir said:
I never insert material from Word directly into FrontPage because of all
the
bloated code. I convert it to html and/or plain text first.
However, recently I tried using a Word document (with a lengthy table, no
less) as an include, and the result loads very fast. Why is this?
I ask not just out of curiosity but for future use. If I can use Word
materials as includes without sacrificing speed, I'll do it more often.
What should I know about this phenomenon?

I can't think of any reason why the same code would load more quickly. By
the time the page gets to the browser, the browser has no way of "knowing"
that the included code is any different than the rest of the code on the
page. It's identical. If anything, making the code an include could
conceivably slow down the load time slightly, since the web server has to
perform an extra task (getting the include file and inserting it into the
page).

Having said that, aside from the Word code issue, server-side includes are a
great tool and can make your work much easier.

Re. the Word code: I would suggest this: if you can possibly avoid using
Word-generated HTML, avoid it. It's almost always very bad code - not just a
bit non-standards-compliant, but *much* longer and more convoluted than is
necessary.

If you really can't avoid it, it will probably work pretty well in the major
browsers, and no one will die from it. But it should be a last resort.
 
Back
Top