TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
RE: Headers and footers in HTML documents - Or a lesson in banging yourhead against the wall
Subject:RE: Headers and footers in HTML documents - Or a lesson in banging yourhead against the wall From:"Diana Ost" <Diana -dot- Ost -at- msmcorp -dot- com> To:"Puffer, Paula \(Paula\)" <Paula -dot- Puffer -at- ElPaso -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 24 May 2006 11:35:31 -0400
Hi:
Currently, I am building a doc library with Robohelp, which is not the
best thing to use to convert Word docs over to HTML (leaves all that
Word junk in there).
So, I am using Microsoft Frontpage and saving the .doc files as
"Webpage, Filtered," which strips out all the Word junk! The only
problem I have so far is that the HTML file "bonds" a style sheet (css)
to the HTML that retains the Word "look" as far as fonts, etc. goes. So,
this may be a perfect solution for you: Cleaner HTML, but still looks
like the Word doc (except no page breaks). It's much easier to edit in
FrontPage and then import it to RoboHelp.
(All I need to do is figure out how to make the new HTML file adhere to
the Robohelp css file :-)
One more thing: if you do decide to use FrontPage, when you convert the
document to HTML, click Tools -> Recalculate hyperlinks to get the new
HTML file to show in the folder list. For some reason, it doesn't show
up until I do that...
I hope this helps.
Cordially,
Diana Ost
Technical Writer/Reporting Analyst
Production Administration
Market Street Mortgage Corporation
diana -dot- ost -at- msmcorp -dot- com
Phone (727) 431-7209
Fax (727) 724-9096
2650 McCormick Drive, Suite 200
Clearwater, Florida 33759
This message and any attachments may contain confidential or privileged
information and are only for the intended recipient of this message. If
you are not the intended recipient, please notify the sender by return
email or phone, and delete or destroy this and all copies of this
message and all attachments. Any unauthorized disclosure, use,
distribution, or reproduction of this message or any attachments is
prohibited and may be unlawful.
-----Original Message-----
From: techwr-l-bounces+diana -dot- ost=msmcorp -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+diana -dot- ost=msmcorp -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf Of Puffer, Paula (Paula)
Sent: Wednesday, May 24, 2006 10:08 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Headers and footers in HTML documents - Or a lesson in banging
yourhead against the wall
I've been given the task of improving our process for moving manuals
from Word Documents to HTML and PDF. The current process was put in
place before I got here. It was not tested to see how it actually
worked. It blows up on a regular basis and it blows up differently each
and every time.
The process as it stands now is make corrections in Word, merge the word
files using a program called Twins File Merger and then convert the
merged file using another program called Click to Convert. They picked
Click to Convert because the PDF and HTML generated files looks EXACTLY
like the Word documents (including the headers and footers), which is
what my bosses want. The PDF is no big deal, but the HTML generated by
Click to Convert is awful. Every line is assigned a class id and if you
open it up in an editor like Frontpage or Dreamweaver, it's a nightmare
to look at.
I'd like to see the process be something like make corrections in Word
and generate PDFs and HTML using Framemaker, ePublisher Pro, or some
equivalent program. At this point the PDF is not an issue with them,
it's the HTML. Anyone know of any programs that will convert word docs
exactly as they appear into HTML? I'm working on persuading my bosses
that really in the HTML documents the Header information is not needed
because they want any printing that happens to come from the PDF and not
the HTML and that HTML is about making the information accessible and
not the presentation.
My bosses have no problem spending the money on the tools, they just
want to make sure the process we come up with works better than what we
have in place now.
Thanks
Paula Puffer, Technical Writer
E-mail: paula -dot- puffer -at- elpaso -dot- com
Phone: 713-420-4787
Cell: 832-545-2003
******************************************************************
This email and any files transmitted with it from the ElPaso Corporation
are confidential and intended solely for the use of the individual or
entity to whom they are addressed.
If you have received this email in error please notify the sender.
******************************************************************
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
