[Author Prev][Author Next][Thread Prev][Thread Next]
[Author Index (this month)][Thread Index (this month)][Top of Archive]

Re: Tips to convert Google Docs into clean HTML?

Subject: Re: Tips to convert Google Docs into clean HTML?
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Sun, 19 Apr 2020 20:36:57 -0400

That "review every page" is hard to push through. Reviewers seem nearly always to want to review only the changes.

Do they do their code that way as well? "We didn't change anything in module B, so the problem caused by the changes in Module A is not my fault, even though I could have caught the incompatible data arrangement if I'd bothered to look at both modules."

Then of course there are the non-SME reviewers who either try to fix the grammar, or else mark the whole thing as "LOOKS GREAT!!"

I'll bet that the requests for error penalties arose from a tendency to hire the cheapest writers available, even if their English-language skills or technical comprehension were beneath sub-optimal.

On Sun, 19 Apr 2020 18:56:24 -0400, Lin Sims <ljsims -dot- ml -at- gmail -dot- com> wrote:

Oh, that sounds like a _truly_ ugly thing to find in a contract. Do you get
to add language like, "experts are required to review every page and sign
off on the accuracy before I submit this project"?

On Fri, Apr 17, 2020 at 6:28 PM Lin Laurie <linlaurie1 -at- hotmail -dot- com> wrote:


I guess that point of view cost them a lot of money. I am just fortunate
that they didn't try to make me pay for their mistake. There is a new trend
out here in Seattle where they want tech writers to sign contracts that
include language regarding having them redo mistakes or pay for them. But I
was very vocal about how their plan wasn't going to work or if they had
someone do it, it might take about 2 1/2-3 months to do just the conversion
work. And it wasn't going to be me doing it.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives

Follow-Ups:

References:
Re: Tips to convert Google Docs into clean HTML?: From: Geoff Mann
RE: Tips to convert Google Docs into clean HTML?: From: Lin Laurie
Re: Tips to convert Google Docs into clean HTML?: From: Chris Morton
RE: Tips to convert Google Docs into clean HTML?: From: Lin Laurie
Re: Tips to convert Google Docs into clean HTML?: From: Lin Sims

Previous by Author: Re: What do you call policy/process/procedure structure?
Next by Author: Re: What do you call policy/process/procedure structure?
Previous by Thread: Re: Tips to convert Google Docs into clean HTML?
Next by Thread: RE: Tips to convert Google Docs into clean HTML?

[Top of Archive] | [Author Index (this month)] | [Thread Index (this month)]

What this post helpful? Share it with friends and colleagues:

Sponsored Ads