Re: [cl-debian] cl-rfc2109: requesting comments
Scribit Luca Capello dies 25/11/2007 hora 19:33: Back in October 2006, Pierre Thierry asked if these parts could be allowed even if not-free [4], but no one answered him. Since I'm not a license nor an RFC expert, here I am :-) Now that I think of it, quoting a copyrighted material doesn't give you free material: you're not allowed to modify this quoted part, or you would denature the original work, which is in utter violation of the copyright, AFAIK. So it would still be better to remove those parts of the RFC. Quickly, Pierre -- [EMAIL PROTECTED] OpenPGP 0xD9D50D8A signature.asc Description: Digital signature
Re: Bug#451799: new evince cannot display Japanese characters correctly
clone 451799 -1 retitle 451799 evince should depend on poppler-data reassign -1 wnpp retitle -1 RFP: poppler-data -- Encoding data for the poppler PDF rendering library block 451799 by -1 thanks * Package name: poppler-data Version : 0.1.1 Upstream Author : Adobe, Red Hat * URL : http://poppler.freedesktop.org/ * License : non-free, see below Programming Lang: None Description : Encoding data for the poppler PDF rendering library This package contains the encoding data needed to view some PDF documents with libpoppler. The copyright is the following: Copyright 1990-1998 Adobe Systems Incorporated. All Rights Reserved. Patents Pending NOTICE: All information contained herein is the property of Adobe Systems Incorporated. Permission is granted for redistribution of this file provided this copyright notice is maintained intact and that the contents of this file are not altered in any way from its original form. PostScript and Display PostScript are trademarks of Adobe Systems Incorporated which may be registered in certain jurisdictions. However I don't think there is anything copyrightable in these files; they only contain series of numbers that describe the mappings. Do you people think it could be suitable for main? (Please follow-up on -legal only for licensing discussions.) Ondrej, are you willing - if the legal problems are settled out - to package it? Otherwise I guess me or any of the co-maintainers could do it, the packaging is absolutely trivial. Le lundi 19 novembre 2007 à 02:25 +0900, Hideki Yamane a écrit : New evince package displays Japanese characters wrong. Broken. Please see attached image file, one is opened CP-06.pdf with evince (Screenshot-CP-06.pdf.png), and another is with Adobe Reader (shows fine). I heard same problem from other people on IRC. The new poppler version needs some specific files that contain some mappings between Unicode and other encodings, which are in a separate package. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Re: [cl-debian] cl-rfc2109: requesting comments
On Tue, Nov 27, 2007 at 06:58:14PM +0100, Pierre THIERRY wrote: Now that I think of it, quoting a copyrighted material doesn't give you free material: you're not allowed to modify this quoted part, or you would denature the original work, which is in utter violation of the copyright, AFAIK. So it would still be better to remove those parts of the RFC. I'm still not sure that quoting such small parts of the RFC would infringe copyright, even if they are modified. Infringement of copyright requires either the whole or a substantial part of the copyright work to be copied, and I'm not convinced the headings would constitute a substantial part. But that's the issue, rather than whether they are modified or not. (Incidentally, I suspect the question of modifying the quoted sections would become relevant when assessing fair use, but I assume the policy is not to rely on fair use given that it is a US-centric concept.) However, as I said before the safest approach (while still retaining some usefulness) is to remove the text of the headings while retaining the paragraph numbering. So it sounds like we're agreed on the practical action (unless you think the paragraph numbers should be removed as well, which I think would be over-cautious). John (TINLA) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
