Re: License of files in Documentation/pictures and ability to distribute them unclear
On Sun, 05 Jan 2014, Carl Peterson wrote: However, an alternative would be to somehow build the SVG to PNG at the expected size(s) as part of make. Not sure what that would take, though, or if it would add yet another dependency to the list. For Debian, I'd be happy if the PNG was there so long as the SVG was also distributed, ideally with a make rule to build the PNG. [Inkscape is usually the easiest way to do this; I have a bunch of: %.png: %.svg inkscape --without-gui --export-dpi=72 --export-png=$@ $ or variants thereof in some of my projects.] But the most important thing for me is just the licenses of those files; source I can figure out in most cases. -- Don Armstrong http://www.donarmstrong.com [On a trip back from collecting grass seeds in tropical bird stomachs and being thought by the customs agents to be transporting Marijuana.] Anyone so square as to tell you they are transporting grass seeds is bound to be OK -- Peter K. Klopfer _Seeds of Doubt_ Science 134:177 10 April 2009 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: License of files in Documentation/pictures and ability to distribute them unclear
Hello, On 05/01/14 03:51, Graham Percival wrote: On Fri, Jan 03, 2014 at 03:28:22PM -0800, Don Armstrong wrote: There are a lot of files in Documentation/pictures which have no clear license, and unfortunately, the git log for them isn't clear at all either. Indeed; those should be clarified. Some of them cannot be distributed by lilypond either, for example, logo-debian.png is the Debian Restricted Use Logo.[1] Oops. Yes, we should replace it with the open use logo. http://www.debian.org/logos/index.en.html http://code.google.com/p/lilypond/issues/detail?id=3779 James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: License of files in Documentation/pictures and ability to distribute them unclear
On Fri, Jan 03, 2014 at 03:28:22PM -0800, Don Armstrong wrote: There are a lot of files in Documentation/pictures which have no clear license, and unfortunately, the git log for them isn't clear at all either. Indeed; those should be clarified. Some of them cannot be distributed by lilypond either, for example, logo-debian.png is the Debian Restricted Use Logo.[1] Oops. Yes, we should replace it with the open use logo. http://www.debian.org/logos/index.en.html It's great that a lot of them have the source which they were built from present, but there are some which are still missing the source. [For example, logo-debian.png can (and probably should) be built directly from the SVG[2] at the appropriate size (or just the SVG used).] Due to our website hosting situation, it would be awkward to build it directly. As for SVG, I'm not familiar with browser and texinfo support. We still have something like 50% users on windows; can IE display SVGs yet? Also, can texinfo 4.13a handle SVGs? - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: License of files in Documentation/pictures and ability to distribute them unclear
On Sat, Jan 4, 2014 at 10:51 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, Jan 03, 2014 at 03:28:22PM -0800, Don Armstrong wrote: It's great that a lot of them have the source which they were built from present, but there are some which are still missing the source. [For example, logo-debian.png can (and probably should) be built directly from the SVG[2] at the appropriate size (or just the SVG used).] Due to our website hosting situation, it would be awkward to build it directly. As for SVG, I'm not familiar with browser and texinfo support. We still have something like 50% users on windows; can IE display SVGs yet? Also, can texinfo 4.13a handle SVGs? SVG support in browsers is still incomplete, last I checked. IE9 has partial support, according to Wikipedia's article on SVG. Regardless, it's not ideal. Nor is live building practical, for the reason Graham mentioned (it would require running a server-side script with every image request to see if the image is available, build the image if necessary, then serve the image). However, an alternative would be to somehow build the SVG to PNG at the expected size(s) as part of make. Not sure what that would take, though, or if it would add yet another dependency to the list. Carl P. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
License of files in Documentation/pictures and ability to distribute them unclear
There are a lot of files in Documentation/pictures which have no clear license, and unfortunately, the git log for them isn't clear at all either. Some of them cannot be distributed by lilypond either, for example, logo-debian.png is the Debian Restricted Use Logo.[1] It's great that a lot of them have the source which they were built from present, but there are some which are still missing the source. [For example, logo-debian.png can (and probably should) be built directly from the SVG[2] at the appropriate size (or just the SVG used).] 1: http://www.debian.org/logos/index.en.html#restricted-use 2: http://www.debian.org/logos/openlogo-nd.svg -- Don Armstrong http://www.donarmstrong.com We have to face the fact that either all of us are going to die together or we are going to learn to live together and if we are to live together we have to talk. -- Eleanor Roosevelt ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
