Publisher - repeated images have different file names, why?

[gregm]

In creating a website, with the same logo on each web-page, when it is
published each page uses a different image file, e.g. image112.gif on page 1,
and image143.gif on page 2. This means the browser cannot used the cached
image from page 1 when displaying page 2, and therefore has to download more
content than neceesary.

The images are identical - in size, file, position on the page, and are
included on the master page.

How can I make eacg page link to just one image file, e.g. logo.gif?

 

[DavidF]

Assuming that you upload your logo image file to a folder on your website
called "Images", then using the insert HTML code fragment tool, modify and
insert the following code where you want the logo to appear on the page:

<IMG SRC="http://yoursite.com/Images/yourlogo.gif">

DavidF

 

[gregm]

David,

I can see how that would work - and that may be the final solution I use.

Unfortunately it would mean however that within publisher (2007beta) I
wouldn't see the image, even in preview mode and so don't get the benefit of
WYSIWYG. I'm using publisher as a friend wants to use it for their website
and whilst I'm comfortable with a naked HTML fragment it will be all greek to
them.

I'm surprised that Publisher duplicates images this way and hence
unnecessarily increases download times?

 

[gregm]

Solved.
Publisher creates two versions of images - even if they occur just once.
One image is used by browsers that support vml, one image is used by
browsers that don't support vml.

So if an identical image appears on three pages, there should be only two
images published.

G.

 

[DavidF]

Actually if you write the link as I proposed, and have your computer
connected to the internet, and the logo image uploaded, then you will see it
in preview mode.

When Publisher was adopted into the Office family, starting in version 2002,
Microsoft started using VML and such with the goal of providing the best
image for any particular browser, and that was when the coding engine
started producing multiple copies of the images, and bloated the file.
However, even with Pub 2000 and before, the coding engine would produce a
copy of each image on each page...just the way it is. That's why I think
importing logos and other images that you might use on each page makes
sense, but I do understand how your friend might have problems with this
approach.

One thing you can do, and should do, is to compress the images before
uploading, especially if you aren't using an image editing program to
optimize the images for the web prior to embedding them in the Publisher
document. Reference: ""Compress graphics file sizes to create smaller
Publisher Web
pages":
http://office.microsoft.com/en-us/assistance/HA011266301033.aspx
You will get much faster loading images...

DavidF

 

[DavidF]

You figured out what it does, but be careful about deleting any of the
"extra" images. It is likely to create problems. Read what I said in the
other post about compressing the images to at least mitigate the file size
bloat and loading time...

DavidF

 

[DavidF]

And one more thought... You should go into Tools > Options > Web tab, and
untick "rely on vml..." and "allow png...", as this will further reduce file
bloat...

DavidF

 

[gregm]

DavidF,

Thanks, I'll adopt your suggestions!

G.