Re: Copyright infringement
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 clear
copyright on all your topics.
On 3/2/2023 6:51 PM, Tony Chung wrote:
Isnât that the whole use case behind DITA?
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 - from
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.â
â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 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
- Re: Copyright infringement, Carolyn Palo
Search our Technical Writing Archives & Magazine