https://bugs.documentfoundation.org/show_bug.cgi?id=129101
--- Comment #24 from rol...@logikalsolutions.com ---
(In reply to Luke from comment #22)
> (In reply to roland from comment #20)
> If you document contains confidential text, you can strip out
> > > all content by following these steps:
> > > https://wiki.documentfoundation.org/QA/BugReport/Attachments
> > Sadly, there is no way to do that. I cannot release the source file for a
> > book going into production
>
> Why can't you use the macro for Confidential Attachments?
There is absolutely nothing secure on the Internet. Anything uploaded for
testing would need to be passed around volunteer to volunteer for testing. This
is a book for commercial release that I've put roughly a year into and am now
at the stage of putting around $10K in editing services into.
Yes, with every book there is always the chance it will sell just 10 copies,
but with an electronic version out there anywhere, that chance is 10,000%.
According to the Indian technical recruiters who call me via VOIP from India,
this book,
https://theminimumyouneedtoknow.com/app_book.html
is one of the most pirated books in India.
How did that happen? It was the book which was going to fund my retirement.
Written so well it got onto the Dr. Dobb's list of recommended reading for all
developers on all platforms. It was selling well. Every year a new batch of
Interns brought a new batch of orders.
A situation much like this happened and I shared an electronic copy via
"secure" channels for "testing." A few weeks later sales went to zero and I
started hearing from recruiters how it was being printed in India and sold for
$5.
I _have_ a book I'm willing to risk. It was the second edition of that book
which I chose to never release after the piracy issue. What I don't have right
now is the time to load images to duplicate the issue. The Holidays are here
and I have 3 books to finish writing before the end of January. I can write the
other two with OnlyOffice.https://www.onlyoffice.com/
Indeed I started them with OnlyOffice when I was waiting entire minutes between
keystrokes for LO to stop flailing around like a gut shot animal.
When I have time I will attempt to replicate the problem with a work I can
risk. I will not risk a new book which has consumed more than a year of my
"free" time.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
