Converting Publisher Files to standard html

[Ralph Lambert]

I hope I am explaining what I am trying to do clearly. Anyway, I inherited
a website that was produced in Publisher (version unknown). I have been
asked to clean up the site so that the user can make simple updates without
having to republish the entire site. For example they have different hours
in the winter and summer, product news, specials.

- My limited experience with Publisher has been that whenever I add text I
blow out the cells in the tables.
- Images and files are named with numbers and are not even close to having
any sort any naming convention in a meaningful way.

My goal is rebuild the site giving files simple names like aboutus.html,
info.html instead of 22234.htm or xyz.htm

* My question: (Finally) Can I do this in publisher or do I have to bite the
bullet and use a speadsheet and go through the site file by file and rebuild
it using NotePad or Front Page or some other editor? *

Ralph

 

[DavidF]

If you are try to edit the code directly, then you will have nothing but
problems. Changes need to be made in the original Publisher document, and
then produce the new code. Publisher's coding engine produces its own
"filtered" code, that is unique to Publisher. While you might be able to
make some minor coding edits, if you start changing the names of the *.*htm
files and image files, the site will be hosed. Reference: "Using Publisher
for web sites":
http://msmvps.com/blogs/dbartosik/archive/2006/01/08/80566.aspx

And...you will not be able to satisfactorily import the site files into
FrontPage...

The version of Publisher makes a big difference as Pub 2003 introduces what
MS has coined "Incremental Uploading". What that means in English is that
the whole site no longer has to be uploaded after modifying the web
publication file. This feature when turned on keeps track of which pages are
modified in the publication file and only uploads those files. Make your
minor changes, and upload those. If you are using Pub 2000, then it uses an
entirely different coding engine...

If you aren't using Pub 2003, then perhaps consider breaking the site up and
using multiple Publisher files to produce the site if there are only a few
pages or sections that need to be updated on a regular basis. Read this
reference to be introduced to the concept: "Building a web site with
multiple Publisher web publication files":
http://msmvps.com/blogs/dbartosik/archive/2006/01/16/81264.aspx

DavidF

 

[Ralph Lambert]

David:

Thank you very much for taking to the time to not only answer my query, but
I see that you answer many others as well. It is very much appreciated.

What you wrote matches my experience (reality check confirmed) The person
(kid) was taught in a local college to use Publisher as tool for building
and designing web pages. <opinion>The use of Front Page or even note pad
would have been far better choices.</opinion>

I understand how Publisher repaginates the document, and how it names its
pages. What I am not clear on (although I have my suspicions) is the way
the image files were named. Did Publisher rename those files or did the
previous maintainer use a poor naming convention? i.e. Instead of naming
them bigdog.jpg and littledog.jpg. They are named 1001.jpg and 24113.jpg I
am not in front of my other computer so I may not have the exact names, but
this the jist of it.

Ralph


FYI: based on your previous email it was probably Publisher 2000

 

[DavidF]

Ralph,

Publisher can be the right tool for some people, some times, but it is first
and foremost a DTP with limited web building capability and is intended for
relatively simple, small, static websites. I agree with your opinion that
FrontPage and other more specialized web building programs are better
choices in general, but that doesn't change your situation.

All versions of Publisher renames the images in the process of producing the
HTML code. Starting in version 2002, and the switch to that coding engine
and the use of VML, etc., Publisher now not only renames the images, it also
produces several copies of most of the images in PNG and other formats with
the goal of providing the best image depending on which browser is used.
Unfortunately this has actually resulted in lower quality and slower loading
images being rendered in many cases. You can mitigate this by changing some
settings in Publisher, and depending on the version by compressing the
images before they are converted. You can also workaround the image renaming
and quality issues by importing them into the document instead of embedding
them. But as I said, the version is important in giving you specifics.

Once again the easiest way to edit the website is to work from the original
Publisher document, and I wouldn't waste too much time trying to edit the
code directly. I am guessing that your site is not that complex and could
easily be edited and reposted. Just let me know which version of Publisher
you are going to use, and I can provide some more help. Good luck.

DavidF

 

[Ralph Lambert]

Ralph,

Publisher can be the right tool for some people, some times, but it is
first and foremost a DTP with limited web building capability and is
intended for relatively simple, small, static websites. I agree with your
opinion that FrontPage and other more specialized web building programs
are better choices in general, but that doesn't change your situation.

Exactly!!!

This has been an education for me. Sorry to say but I never gave Publisher
much thought before, I had always put it in the category of Print Artist or
Print Shop (Not that PA or PS are bad programs, but, there is Adobe, The
Gimp, or Paint.net) the choices are endless.

All versions of Publisher renames the images in the process of producing
the HTML code. Starting in version 2002, and the switch to that coding
engine and the use of VML, etc., Publisher now not only renames the
images, it also produces several copies of most of the images in PNG and
other formats with the goal of providing the best image depending on which
browser is used. Unfortunately this has actually resulted in lower quality
and slower loading images being rendered in many cases. You can mitigate
this by changing some settings in Publisher, and depending on the version
by compressing the images before they are converted. You can also
workaround the image renaming and quality issues by importing them into
the document instead of embedding them. But as I said, the version is
important in giving you specifics.

To late, I don't have access to the original image names and I may not have
access to the version information. Ugh...

Once again the easiest way to edit the website is to work from the
original Publisher document, and I wouldn't waste too much time trying to
edit the code directly. I am guessing that your site is not that complex
and could easily be edited and reposted. Just let me know which version of
Publisher you are going to use, and I can provide some more help. Good
luck.

Your right about size. But as far as simplicity is concerned, again I say
Ugh... Would I be better off redoing the site from scratch? There are
several hundreds of images with slight variations of the same image. Nested
tables. Oh well... I hope the client doesn't want an exact match.

I guess it is like any building project. It takes less time and money to
create a new building than it does to remodle (sp?).

Your imput as always is greatly apreciated.

Ralph

 

[DavidF]

Ralph,

You are welcome...

If you don't have access to the original Publisher file, and are using Pub
2003 yourself, there is a shortcut to rebuilding from scratch. Pub 2003 will
open *.*htm files, so you can download the site files, and piece together
the site. Here is an article that talks both about the need for backups, but
also at the end of the article gives you an approach for rebuilding: "Common
Sense Computing 101 aka "Why in the world would you lose your publisher
file?":
http://msmvps.com/blogs/dbartosik/archive/2006/01/19/81461.aspx

Also assuming that your are using Pub 2003, then before you Publish to the
Web, be sure to go to Tools > Options > Web tab and untick "Rely on VML..."
and "Allow PNG...". Also you should use the Compress images option:
"Compress graphics file sizes to create smaller Publisher Web pages":
http://office.microsoft.com/en-us/assistance/HA011266301033.aspx

And if you can use Pub 2000, then it is the best version for web building...

Have fun...

DavidF