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.
I'm retired now. When we wrote manuals we did not just copy from other offices. Of course we were a team, so we worked together and copied from each other when necessary.
We had a style guide to make it consistent. I cannot write more about the processes.Â
BerndÂ Am Freitag, 28. April 2023 um 21:33:34 MESZ hat Carolyn Palo <carolynpalo -at- gmail -dot- com> Folgendes geschrieben:
I wanted to share the outcome of the potential copyright problem with
copying and/or rebranding one company's software user manual to another.
The Legal Department told the Product Manager (who thought this was "no big
deal") that they (software devs, product management for the most part here
in the US) needed to get permission
from the software company (Finland), to copy the manual.
On Fri, Mar 3, 2023 at 10:30âAM Carolyn Palo <carolynpalo -at- gmail -dot- com> wrote:
> Thank you everyone.Â Your responses solidify my stance on the matter.Â I'm
> dealing with a mix of naivete, ignorance and cavalier attitudes.
> I deflected to the legal department as a matter of education, in the
> least, and exposure to some thinking.Â The software engineer is from India,
> the product manager is from here in the states, the manual is from
> My conscience -don't do it.Â It is a big legal risk, and to add some
> color, I once managed the book distribution of an "elite software
> company."Â My background is book publishing.Â Some of their technical books
> went OP (out-of-print) and were sitting in the warehouse.Â They are
> typically destroyed unless the author wants them or authorizes a remainder
> sale. It's illegal to sell them as the rights have expired.Â The "elite
> software company" didn't want to pay to have the OP books destroyed, "We
> can sell them!" they said.Â We said, "No."Â "Yes, we can!" they said
> (sales).Â I explained
> to my liaison there, "Nope, legal problems will happen and you will be
> sued."Â They insisted.Â We sold them on their behalf with a big warning.
> They thought they
> made a lot of money and were "disrupting the system."
> Then they were sued multiple times by the authors who wrote the books.
> *Carolyn Palo*
> *Professional Writer *
> Phone:Â 617-491-0551
> Email:Â carolynpalo -at- gmail -dot- com
> On Fri, Mar 3, 2023 at 6:39 AM Peter Neilson <neilson -at- windstream -dot- net>
>> I can believe it. There are several possible motives:
>> - Lazy or sloppy management.
>> - Naive - "The information wants to be free."
>> - Scary deadline, no time to make it right.
>> - Underhanded. There is a hidden agenda.
>> It usually comes down to money. Cui bono?
>> On 3/3/23 04:44, Keith Hood wrote:
>> >Â I can't believe anyone could be so cavalier about what could be such
>> a horrendous legal risk. I've worked in this field for more than 30 years
>> and I've never heard of something like this. I think the people you are
>> working for are not solidly in this world.
>> >Â Â Â Â Â Keith Hood
>> >Â Â Â On Thursday, March 2, 2023 at 11:15:12 PM CST, Gene Kim-Eng<
>> techwr -at- genek -dot- com>Â wrote:
>> >Â Structurally, perhaps, but it does not relieve you of the need for
>> > copyright on all your topics.
>> > Gene Kim-Eng
>> > On 3/2/2023 6:51 PM, Tony Chung wrote:
>> >> Isnât that the whole use case behind DITA?
>> >> -T
>> >> On Thu, Mar 2, 2023 at 14:05 Carolyn<carolynpalo -at- gmail -dot- com>Â wrote:
>> >>> Hello - wondering what experience anyone has with copying manuals?
>> >>> Specifically, taking an existing manual and changing the name only -
>> >>> one company to another?
>> >>> My stance is it is plainly copyright infringement.Â Iâm told âyeah
>> but no
>> >>> one cares we do it all the time in the software world.â
>> >>> Really?Â Anyone?
>> >>> Carolyn Palo
>> >>> 617 491-0551
>> >>> âDonât find fault, find a remedy.â - Henry ForD
>> Visit TechWhirl for the latest on content technology, content strategy
>> and content development | https://techwhirl.com
>> You are currently subscribed to TECHWR-L as carolynpalo -at- gmail -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
>> 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
Visit TechWhirl for the latest on content technology, content strategy and content development | https://techwhirl.com