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.
Subject:Re: Management disagreement RE: HTML From:Stephanie Holland <SLHOLLAND -at- MICRON -dot- COM> Date:Fri, 10 Jan 1997 09:09:30 -0700
<snip from John Posada>
In general, try to create the final version in the application that will
display that final version. Only get other applications involved if
there is a
need.
---------
Yes -- I agree with your thoughts. What you said (above) is the point
I've been trying to make here at work. I'll keep trying ...
Thanks for your help,
Stephanie
Stephanie Holland
Micron Electronics
slholland -at- micron -dot- com
>----------
>From: John Posada[SMTP:jposada -at- notes -dot- cc -dot- bellcore -dot- com]
>Sent: Friday, January 10, 1997 7:05 AM
>To: Stephanie Holland
>Cc: TECHWR-L
>Subject: Re: Management disagreement RE: HTML
>
>in our Information Technology Department. This manager's background is
>in sales. He is not familiar with technical communication or the new
>changes taking place in the field.
>
>My background is 15 years of sales, and I have no problem with
>technical
>communications...he wrote proposals, no?
>
>Anytime you convert from one format to another, there will be tweeking.
> If
>both formats were the same, then you wouldn't need more than one
>application.
>
>Anyway...I write proposals for very large systems..between 500k to 100
>milion
>or more. We write those documents in either Word or Frame. Sometimes,
>the
>customer will want the hardcopy and also in electronic form. Sometimes
>this
>electronic form is the native format (*.doc) and sometimes it is a
>markup
>(html, sgml).
>
>If you don't care that the html document contains that same information
>but
>isn't formatted the same (as if you are looking at two different
>documents),
>then yes..you could do it in two steps. However, if you need the
>markup
>version to look like it is the same document, just in two different
>mediums,
>then yes, the converted document ALWAYS needs rework.
>
>In general, try to create the final version in the application that
>will
>display that final version. Only get other applications involved if
>there is a
>need. The reason we write in Word or Frame instead of directly in html
>is that
>for hardcopy otput, a word processor just has more tools than an html
>editor,
>and our documents are too complex to rely on html capabilities.
>
>John Posada
>- Central New Jersey Employment Manager
>Society for Technical Communication
>http://stc.org/region2/njc/
>
>- Technical Proposal Writer
>Bell Communications Research
>(908) 699-5839 (W)
>jposada -at- notes -dot- cc -dot- bellcore -dot- com
>
>"Its wonderful to be here in the great state of Chicago"
> - Vice President Dan Quayle, 4/30/91
>--------------------------------------------------------------------
>I don't speak for my employer and they return the favor
>--------------------------------------------------------------------
>
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
