R
RoyMassie
Posting this here because I could not find a succinct solution to
this
problem anywhere else and it took me a while to sort out.
Problem:
If you create / publish web content using the MS Office suite, you
may
get download prompts to add ietag.dll when you browse to the page
using IE. This creates an undesirable experience for page visitors
since downloading DLLs is always suspect. This can occur even is the
page visitor (browser PC) already has the DLL. I believe this occurs
because the version on the browsing PC does not match the one in the
namespace given near the top of the compiled HTML pages (from MS-Word
for example). Apparently Office inserts its own tags in the
generated
HTML so it can reload the pages and render them with underlines and
other tagging having special meaning for the Internt (e.g. e-mail
addresses get a dashed purple underline in Word).
Solution:
Use the "Filtered HTML" Save As option in the Office application so
the generated HTML does not have the reload tags and the HTML will
not
need the ietag.dll leading to the download prompt. You will not be
able to reload your compiled HTML back into the Office app for
editing
but this should not be an issue if you just treat them as output for
the web site (files) and use the original Office doc as the master
copy to be revised. Also, the filtered HTML does not support all the
possible layout options/features in the various Office apps, so be
sure your filtered HTML matches what you intend to show.
this
problem anywhere else and it took me a while to sort out.
Problem:
If you create / publish web content using the MS Office suite, you
may
get download prompts to add ietag.dll when you browse to the page
using IE. This creates an undesirable experience for page visitors
since downloading DLLs is always suspect. This can occur even is the
page visitor (browser PC) already has the DLL. I believe this occurs
because the version on the browsing PC does not match the one in the
namespace given near the top of the compiled HTML pages (from MS-Word
for example). Apparently Office inserts its own tags in the
generated
HTML so it can reload the pages and render them with underlines and
other tagging having special meaning for the Internt (e.g. e-mail
addresses get a dashed purple underline in Word).
Solution:
Use the "Filtered HTML" Save As option in the Office application so
the generated HTML does not have the reload tags and the HTML will
not
need the ietag.dll leading to the download prompt. You will not be
able to reload your compiled HTML back into the Office app for
editing
but this should not be an issue if you just treat them as output for
the web site (files) and use the original Office doc as the master
copy to be revised. Also, the filtered HTML does not support all the
possible layout options/features in the various Office apps, so be
sure your filtered HTML matches what you intend to show.