Re: Cheat sheets and LilyPond documentation
> Am 2020-02-11 um 23:11 schrieb David Kastrup : > > It _is_ the source format if I understand you correctly. Yes, Inkscape’s SVG is "rich" but completely valid and displayable in browsers. Inkscape can import/export other formats, but SVG is its native format. It can also use SVGZ (compressed SVG) to save some disk space, but with a text (XML) format like SVG we’re on the save side. There are already tools to e.g. replace text in SVG (might become handy for translations), but I guess manual intervention would be necessary to keep the layout. > At any rate, it seems I apparently need to add some redundancy or I'll > never get anywhere without losing all company on the way. There, there. David, your input is valuable and appreciated. (And I’m sorry you couldn’t survive on working for LilyPond!) In nerd & geek zones like this we are (or at least should be) used to and often can’t survive without autistic characters and their not always cordial interactions. (Being on the spectrum myself.) All the best, Hraban --- fiëé visuëlle Henning Hraban Ramm https://www.fiee.net
Re: Cheat sheets and LilyPond documentation [was Re: Clef "treble_8"]
Noeck writes: > Hi David, > >> Is SVG the file format Inkscape saves in? > > Yes, SVG is the Inkscape file format. Inkscape adds some Inkscape > specific name spaces but within the spec of SVG. To quote the website¹: > > Perfectly compliant SVG format file generation and editing > > >> Or is it only an export format for it? > > No. > >> Either way it does not sound like the "provide the >> source" vibe should be hard to meet in order to inspire followup work. > > I am not sure I understand. You mean it is close to what you want as a > source format? It _is_ the source format if I understand you correctly. Not merely close. So the principal question is how to get it into our documentation in a useful manner. The text-editing thing might provide some pointers. >> At some point of time I have to reread the collected devastating >> dissings of dreadlord David. This is not the first helpful project >> these days that has mentioned getting discouraged by the initial >> reaction. > > I’ve read a lot of mails the last days. That’s why I wanted to give > some positive feedback. I honestly appreciate it. Thanks. It turns out that speaking up only when you have some improvement to suggest amounts to the maxim "if you cannot say anything bad, don't say anything at all" which somewhat surprisingly does not result in overwhelming popularity. Though it appears to work for becoming president. At any rate, it seems I apparently need to add some redundancy or I'll never get anywhere without losing all company on the way. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
Re: Cheat sheets and LilyPond documentation [was Re: Clef "treble_8"]
Hi David, > Is SVG the file format Inkscape saves in? Yes, SVG is the Inkscape file format. Inkscape adds some Inkscape specific name spaces but within the spec of SVG. To quote the website¹: Perfectly compliant SVG format file generation and editing > Or is it only an export format for it? No. > Either way it does not sound like the "provide the > source" vibe should be hard to meet in order to inspire followup work. I am not sure I understand. You mean it is close to what you want as a source format? > At some point of time I have to reread the collected devastating > dissings of dreadlord David. This is not the first helpful project > these days that has mentioned getting discouraged by the initial > reaction. I’ve read a lot of mails the last days. That’s why I wanted to give some positive feedback. I honestly appreciate it. Best, Joram ¹: https://inkscape.org/about/features
Re: Cheat sheets and LilyPond documentation [was Re: Clef "treble_8"]
Noeck writes: > Hi David, > >> Is there a source? Or is it hand-written SVG? If we are trying to >> follow the spirit of the GPL, source is defined as "preferred form for >> modification". For a cobbled-together version, that is tricky to >> define, but we would not want to make it harder than necessary to come >> up with updated versions. > > The SVG is the source in the sense "preferred form of modification" – at > least preferred by me :). It is created with Inkscape. I guess it could > be done in LilyPond or TeX or sth else but probably with a similar > amount of complexity (except some text replacement perhaps). > Personally, I would update it via Inkscape (and export to PDF > additionally). The cheat sheet is 8000 lines as SVG (with the line > breaks Inkscape introduces, but you get a feeling). The spacing sheet > 3600 lines. Is SVG the file format Inkscape saves in? Or is it only an export format for it? Either way it does not sound like the "provide the source" vibe should be hard to meet in order to inspire followup work. >>> Maybe this can be re-evaluated... An alternative is to add links to >>> to the documentation. >> >> Or from the web page, but then people might have a harder time finding >> it. We have some diagrams with arrows in our web presence if I am not >> mistaken. They must have been created in some kind of manner. Of >> course something fitting well into the Texinfo creation process would be >> nice since we have a lot of output formats for our documentation. > > You mean this? http://lilypond.org/text-input.html Well, yes, there > seems to be a place for that. I don’t know the Texinfo stuff enough to > tell if there is a way. For the ly code of the visual index perhaps. > > Btw, I appreciate your friendly reaction very much. At some point of time I have to reread the collected devastating dissings of dreadlord David. This is not the first helpful project these days that has mentioned getting discouraged by the initial reaction. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
Cheat sheets and LilyPond documentation [was Re: Clef "treble_8"]
Hi David, > Is there a source? Or is it hand-written SVG? If we are trying to > follow the spirit of the GPL, source is defined as "preferred form for > modification". For a cobbled-together version, that is tricky to > define, but we would not want to make it harder than necessary to come > up with updated versions. The SVG is the source in the sense "preferred form of modification" – at least preferred by me :). It is created with Inkscape. I guess it could be done in LilyPond or TeX or sth else but probably with a similar amount of complexity (except some text replacement perhaps). Personally, I would update it via Inkscape (and export to PDF additionally). The cheat sheet is 8000 lines as SVG (with the line breaks Inkscape introduces, but you get a feeling). The spacing sheet 3600 lines. >> Maybe this can be re-evaluated... An alternative is to add links to >> to the documentation. > > Or from the web page, but then people might have a harder time finding > it. We have some diagrams with arrows in our web presence if I am not > mistaken. They must have been created in some kind of manner. Of > course something fitting well into the Texinfo creation process would be > nice since we have a lot of output formats for our documentation. You mean this? http://lilypond.org/text-input.html Well, yes, there seems to be a place for that. I don’t know the Texinfo stuff enough to tell if there is a way. For the ly code of the visual index perhaps. Btw, I appreciate your friendly reaction very much. Best, Joram ¹: Inkscape: free vector graphics editor https://inkscape.org
