Minor typos and the QA guy/scrummaster

[David Creamer]

As suggested....

Using a PDF review cycle, either by email or server-based, should work. All
the proof-readers need to do is use the free Adobe Reader to use the insert,
delete, and replace text tools for 90% of edits (certainly for typos).
Review comments in Acrobat Pro and then import the comments back into the
Frame document (with track changes turned). One last review of track changes
in Frame and you are (mostly) done. 

If you content is supplied in Word from the SMEs, use the Word review cycle
in either native Word format or as PDF (same basic process as Frame) before
it is ever placed in Frame. Rinse and repeat as many times as necessary
before placing in Frame. Incoming text should be reasonably clean at that
point. Anyone asking for major rewrites _after_ it is in Frame is not doing
their proofing job when t is supposed to  e done, and should be called on it
during committee meetings*.

*This workflow is something that should be set in policy beforehand--that
way it is easy for everyone to agree to it in principle. Make sure the worst
offenders of major rewrites agree to the policy in front of everyone; that
makes it harder for them to ignore the policy later one. 


David Creamer
IDEAS Training
http://www.ideastraining.com
Adobe Authorized Instructor & Certified Expert since 1995
Authorized QuarkXPress Instructor and Certified Expert since 1988




**********
My QA guy has a problem with chasing minor typos in our docs: it takes
longer to document the typo than it does to fix it. He wants a solution that
bypasses the need for FrameMaker, and has read an article that says Word
2013 will allow editing of PDFs in native format. He wants the developers to
be able to do this to my docs. 

I?ve explained all the many problems with using Word, but he is still
searching for an answer, which means I am too. 

What is your solution to the problem he sees? To me, it should be a
non-problem, i.e., typos should not exist anyway, and the developers should
not be allowed anywhere near my ?source?, but the reality is that he has
more say in it than I (he is also scrummaster).