Converting .doc files to Single File Web Pages

[Guest]

I know to click "File," "Save As", and select File Type="Single FileWeb Page"
and this saves a mime format version of the file. The problem is that this
method keeps the original .doc format document and saves a second file in the
..nhtm?format.

Trouble is I'm converting existing .doc files in an existing website because
I want faster speed, and I don't want to have to relink every hyperlink in
every document.

Thanks for your help.

STeve

Ps - I'm using Word 2003, FrontPage 2003 and Windows XP

 

[Helpful person]

I know to click "File," "Save As", and select File Type="Single FileWeb Page"
and this saves a mime format version of the file. The problem is that this
method keeps the original .doc format document and saves a second file in the
.nhtm?format.

Trouble is I'm converting existing .doc files in an existing website because
I want faster speed, and I don't want to have to relink every hyperlink in
every document.

Thanks for your help.

STeve

Ps - I'm using Word 2003, FrontPage 2003 and Windows XP

Try converting them to PDF files.

www.richardfisher.com

 

[Thomas A. Rowe]

If you replace a file with another of a different name, then you will have to redo all hyperlinks
that point to this file.

If you rename the current file, then FP will update all hyperlinks.

Your best option is to make sure you have a copy of all of the .doc file in a folder outside of FP,
then rename each file from within FP from having a .doc to having a .htm extension. In the folder
outside of FP use Word to save each document as HTML, then when finish import the .htm documents
into FP overwriting the once you renamed.

However as someone pointed out, you would be best to convert the document to PDF files, instead of
converting from .doc to .htm

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage

http://www.Ecom-Data.com
==============================================

 

[Mark Fitzpatrick]

Single file web pages aren't exactly meant for the web. Usually they are
meant to be saved locally as an archive and viewed in IE (and only IE). Have
it saved as HTML and it should also save the images seperated. You can't
have a normal web page with embedded imaged since that's not the way a
normal web page works.

 

[Mike Mueller]

I would create a new web in FP and then import all of the html files you
already have done. You will want FP to do the site management for this one

Then I would do your Word exports to htm, as I agree with the other posters
who have suggested that you don't go the single page website.

Next, import the thickets (filename.htm and the filename_files folder) that
Word produced into FrontPage
- make sure any images in the folders are truly the same if they have the
same name. There are going to be other common named items, such as
filelist.xml. They will need to be renamed. FP will manage the html pages to
keep the references to the support files correct

Then you can consolidate all of the thicket folders into one folder.

Last thing would be to open up any one of the pages, and do a Find & Replace
for all pages, having FP replace ' .doc" ' with '.htm" '. Then you would not
need to redo all of the links contained in the site

Mike

 

[Guest]

Thanks very much for the replies.

I can see that I need to stop for a minute and reflect on the various file
types, the purpose for converting the files, and the nature of my site.

I have developed an intranet site at work. The site resides on the main
server and is accessed by remote locations over our company network by
high-speed internet connections. The site is getting fairly large at nearly
1,000 pages. The html pages are pretty simple with very few graphics or
pictures. The linked documents are a combination of .html, .doc, and .pdf
files. I have found that alot of the .doc format documents are quite slow
downloading compared to .pdf or .html files.

The .pdf files are comparatively fast, but our staff are not able to
manipulate the documents. The .html files are also fast, but there's the
difficulty keeping the site organized with the thicket files. I thought the
Single File Web Page was the answer - quick downloads, no extra thicket
files/folders, and staff can manipulate the documents. Now I see things
aren't quite so simple.

A few questions.........

1. Why are the .pdf format files better?
2. Will the Single File Web Pages work Ok so long as there are no graphics
and all the users have IE?
3. Are there any other options?

Thanks again,
Steve