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:Reviewing docs [Was: Re: "New Media"] From:Brian Gordon <elasticsoul2003 -at- yahoo -dot- ca> To:"TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 14 Oct 2005 13:34:33 -0400 (EDT)
--- Walter Campbell <atypicaluser -at- gmail -dot- com> wrote:
> I can think of two problems: specifying the section
> in the reviewed
> document to which the blog comment applies, and
> identifying blog
> threads
The first problem you mention is the concern I had
about longer docs.
> Might a newsgroup-like forum be a better mechanism
> for threaded discussions?
I use AuthorIT, which works in small topics (anywhere
from a word to several paragraphs/tables, typically);
I could see posting these topics, or small groups of,
each with its own blog/forum. Reviewers could be
directed only to the topics/blogs of relevance.
>
> Where I work, I'm trying to persuade reviewers to
> annotate documents
> with the commenting and markup tools now available
> in Adobe Reader. My
> grand plan was to then take everyone's annotations
> and consolidate
> them into a single document, so that everyone could
> see what was said.
> Unfortunately, so few reviewers are annotating the
> PDF files that I've
> not yet been able to do that.
>
>
I know your pain. I have had this problem throughout
my TW career. Best solution (from the writer's POV)
was with a manager at X who pulled in all the relevant
people to a meeting and went over each doc
LINE-BY-LINE.
I currently work in an extreme programming shop, so
thought it might be easier to get developers to go to
a blog, which they do regularly anyway.
Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here: http://www.webworks.com/techwr-l
Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit http://www.techwr-l.com/techwhirl/ for more resources and info.
