Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


On 02/16/2013 01:21 PM, Jean-Baptiste Faure wrote:
Hi,

As LibreOffice uses more and more the Python language, TDF may be
interested by this call for help:
http://pyfound.blogspot.ca/2013/02/python-trademark-at-risk-in-europe-we.html

Best regards
JBF


I wonder if the Python "people" should contact all the Python book writers and publishers. Well, if that company get there way, all of those books and such will be violating the copyright, even though the books have been in print much longer than the company's copyright attempt, by a decade or two. All of their books will be required to do a "stop sales or else" type of thing. So it is more than the companies that use Python language, but the book writers and sellers who need to get in the act and protect their income for writing/selling books about the Python language.

Maybe, since O'Reilly uses a "python" image [trademarked or copyrighted] for their Python language books they publish, that might help the "copyright" cause.

--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.