Technical Writing Using OpenOffice.org Writer (O'ReillyNet)

Technical Writing Using OpenOffice.org Writer (O'ReillyNet)

Posted Aug 27, 2004 19:21 UTC (Fri) by cpm (subscriber, #3554)
In reply to: Technical Writing Using OpenOffice.org Writer (O'ReillyNet) by horen
Parent article: Technical Writing Using OpenOffice.org Writer (O'ReillyNet)

I do not agree at all.

Being able to outline the page, insert the graphics/illustrations/figures and
captions, see how the footnotes are going to land have a HUGE
impact on being able to generate a treatment that the
intended audience is going to actually READ.

Big problem with so-called Technical Writing, is that it is
often put together for those who HAVE to read it, rather
than inticing others to read it for personal edification, etc.

I hardly ever read included docs beyond any notes about
building and config switches, and go straight to the store
for the O'Reilly manual. The books that come with prop
software, go right in a ziplock, and go into the file
cabinet with the distro media.

Why? Because I find the overall presentation of the O'Reilly
books to be just my cup-o-tea. I can read them on the couch
and not feel like I /have/ to read it. It's almost like
reading for fun.

For this purpose, I much prefer a very basic text editor/spell
checker, like Abiword, or something, sometimes emacs for
the content generation, and Scribus for the doc prep.

I flip between the screens, see what is lacking, fix it, move
on to the next section.

I live it, I love it.

--

---

(Log in to post comments)