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.
Some WIKIs do not implement the entire HTML tag set, for one thing.
That said, why in the world would you use Word for the basic doc in
this case, then converting it to HTML? Admittedly, I haven't created
Word docs and output them as HTML in some time--perhaps their
conversion has improved substantially in the interim, for it could
hardly have been worse.
There are *many* HTML creation tools that would be a superior method
if the wiki in question supports HTML import. For example, the free
app Kompozer is a WYSIWYG HTML creation and editing tool that would
work quite well for this, and provide cleaner HTML to boot.
> On Jan 6, 2010 3:27 PM, "Spectrum Writing" <info -at- spectrumwritingllc -dot- com>
> I have a potential client who (that for reasons aren't pertinent here) is
> insistent that the User Manual be in a Wiki. I am working through a
> professional and carefully worded response to this demand, including pros
> and cons based on what their requirements are, what they want to do with the
> manual, the skills level of their SMEs, etc. That said, I want to
> thoroughly investigate the following option as I formulate my response -
> Have you ever developed content in Word (based on a Word template), saved
> the Word document as an HTML file, and then uploaded the file into a Wiki?
> Or have you done something similar outside of a Wiki using a different
> approach with other tools? Basically, a way to develop outside of a Wiki and
> then convert the content to HTML files and then upload the content to the
> Wiki. There are a lot of reasons that I am asking this question and please,
> I am NOT looking to be told to develop only in the Wiki and ask me why I
> want to do something else. Like I said, there are a lot of mitigating
> factors that necessitate looking into an approach that will not require
> direct development in the Wiki.
> Tammy Van Boening
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-