Re: Website: Provide LilyPond source together with the example output
2011/8/24 Štěpán Němec step...@gmail.com: It's great there are various examples at http://lilypond.org/examples.html but the fact that there are _only_ the outputs without the corresponding LilyPond source is somewhat anticlimactic. I sure am not the only one who naturally goes Wow, how was _this_ done? when looking at (some of) the examples. I asked about these examples some time ago and the answer was that the source code is hidden on purpose. You should be able to find something about that in e-mail archives. Of course you can find source files in git http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/web/ly-examples;hb=HEAD cheers, Janek PS i guess that http://code.google.com/p/lilypond/issues/detail?id=1834 might be invalid then. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
Janek Warchoł janek.lilyp...@gmail.com writes: 2011/8/24 Štěpán Němec step...@gmail.com: It's great there are various examples at http://lilypond.org/examples.html but the fact that there are _only_ the outputs without the corresponding LilyPond source is somewhat anticlimactic. I sure am not the only one who naturally goes Wow, how was _this_ done? when looking at (some of) the examples. I asked about these examples some time ago and the answer was that the source code is hidden on purpose. You should be able to find something about that in e-mail archives. Of course you can find source files in git http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree;f=Documentation/web/ly-examples;hb=HEAD I agree that this is anticlimactic. Personally, what I would like to see is having a small source code extract displayed on mouse-over corresponding to the displayed element. We have this information available inside of Lilypond (and use it in PDF for source navigation), the question would be how to get it out to image maps. Showing the whole humongous source is likely to be a turn-off. Seeing a small source window for individual constructs on demand may be quite more educating, entertaining and reassuring. http://code.google.com/p/lilypond/issues/detail?id=1834 might be invalid then. Hm. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
On Wed, 24 Aug 2011 09:59:31 +0200 David Kastrup wrote: I agree that this is anticlimactic. Personally, what I would like to see is having a small source code extract displayed on mouse-over corresponding to the displayed element. We have this information available inside of Lilypond (and use it in PDF for source navigation), the question would be how to get it out to image maps. Showing the whole humongous source is likely to be a turn-off. Seeing a small source window for individual constructs on demand may be quite more educating, entertaining and reassuring. That'd be one way. Another way would be to make the images behave just the same as in the tutorial -- link to the text file with the source (where the relevant portion is delimited with % begin ly-snippet or something like that, which would take care of the turn-off issue). Also, I'm not sure some of the examples could reasonably fit into a mouse-over bubble. -- Štěpán ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
2011/8/24 Štěpán Němec step...@gmail.com: On Wed, 24 Aug 2011 09:59:31 +0200 David Kastrup wrote: I agree that this is anticlimactic. Personally, what I would like to see is having a small source code extract displayed on mouse-over corresponding to the displayed element. We have this information available inside of Lilypond (and use it in PDF for source navigation), the question would be how to get it out to image maps. Showing the whole humongous source is likely to be a turn-off. Seeing a small source window for individual constructs on demand may be quite more educating, entertaining and reassuring. That'd be one way. Another way would be to make the images behave just the same as in the tutorial -- link to the text file with the source (where the relevant portion is delimited with % begin ly-snippet or something like that, which would take care of the turn-off issue). Also, I'm not sure some of the examples could reasonably fit into a mouse-over bubble. I think that David's point was that the scores are too big and complex to be shown in their entirety, because they'll scare beginners. I think he suggests that the mouse-over bubble would show only a small part of the code, directly relevant the the object pointed to. cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
Am Mittwoch, 24. August 2011, 13:43:43 schrieb Janek Warchoł: 2011/8/24 Štěpán Němec step...@gmail.com: I think that David's point was that the scores are too big and complex to be shown in their entirety, because they'll scare beginners. I think he suggests that the mouse-over bubble would show only a small part of the code, directly relevant the the object pointed to. What's the point of showing some code that you can't copy and compile in its entirety? That's even more pointless. We shouldn't show the code by default, that's what we all agree, I think. But we should make it possible for the users to easily download the whole code for each example to that they can start playing with it. A click on the image shows an enlarged image (which we shouldn't change to showing the code), but we can add a Download LilyPond code linke next to the image. That would be the best solution, IMO. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org signature.asc Description: This is a digitally signed message part. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
Janek Warchoł janek.lilyp...@gmail.com writes: 2011/8/24 Štěpán Němec step...@gmail.com: On Wed, 24 Aug 2011 09:59:31 +0200 David Kastrup wrote: I agree that this is anticlimactic. Personally, what I would like to see is having a small source code extract displayed on mouse-over corresponding to the displayed element. We have this information available inside of Lilypond (and use it in PDF for source navigation), the question would be how to get it out to image maps. Showing the whole humongous source is likely to be a turn-off. Seeing a small source window for individual constructs on demand may be quite more educating, entertaining and reassuring. That'd be one way. Another way would be to make the images behave just the same as in the tutorial -- link to the text file with the source (where the relevant portion is delimited with % begin ly-snippet or something like that, which would take care of the turn-off issue). Also, I'm not sure some of the examples could reasonably fit into a mouse-over bubble. I think that David's point was that the scores are too big and complex to be shown in their entirety, because they'll scare beginners. I think he suggests that the mouse-over bubble would show only a small part of the code, directly relevant the the object pointed to. That sounds likely to have been his intent, though I am not sure he thought this through completely. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
Reinhold Kainhofer reinh...@kainhofer.com writes: Am Mittwoch, 24. August 2011, 13:43:43 schrieb Janek Warchoł: 2011/8/24 Štěpán Němec step...@gmail.com: I think that David's point was that the scores are too big and complex to be shown in their entirety, because they'll scare beginners. I think he suggests that the mouse-over bubble would show only a small part of the code, directly relevant the the object pointed to. What's the point of showing some code that you can't copy and compile in its entirety? That's even more pointless. A user looking for information about Lilypond will not be able to copy and compile code in its entirety, period. Because he does not even have Lilypond installed. The point is to not just show what you can achieve with Lilypond (Lilypond can't produce any score that would be of a higher quality than a score produced by Inkscape, if you work long enough on the latter), but also what kind of effort it takes, and what kind of input, and how you can learn about it. For me if you create the following 20-letter input on a keyboard with an editor of your liking, the following construct will fall out is much more compelling than if you click 50 menu items in a hierarchy usually hidden 3 layers deep in the right manner and fine-adjust the results by pushing the material around manually (we have a video to show you the sequence done by a master, as one can't reliably describe something like that in text), you'll get the following result.. Like a musician usually prefers if you like to play this music, I can sell you a score over if you like to play this music, I can sell you lessons until you know it by heart. Which is the point of notation in the first place. We shouldn't show the code by default, that's what we all agree, I think. But we should make it possible for the users to easily download the whole code for each example to that they can start playing with it. Red herring, different purpose. Nobody has proposed withholding the source code on principle. The question was what to turn into a part of the presentation. And the source code as a whole is just not suitable for that. A click on the image shows an enlarged image (which we shouldn't change to showing the code), but we can add a Download LilyPond code linke next to the image. That would be the best solution, IMO. People won't be able to make the connection between picture and source, since the source is just one humongous block. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 665 in lilypond: Request: MusicXML backend
Comment #18 on issue 665 by fedel...@gmail.com: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 A recent discussion about this feature request: http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00435.html I offer 50 euro ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Comment #2 on issue 1834 by colinpkc...@gmail.com: Website: provide link to .ly for examples http://code.google.com/p/lilypond/issues/detail?id=1834 Summarising comments on bug-lilypond: The examples are often too complex and lengthy to be really useful to beginners. As above, they wouldn't work in mouse-over bubbles. The source of the examples has value, both as a snippet, and as a teaching tool. Reinhold suggests clickable download links next to the images. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Website: Provide LilyPond source together with the example output
Štěpán Němec step...@gmail.com wrote in message news:87y5yjiruj@gmail.com... It's great there are various examples at http://lilypond.org/examples.html but the fact that there are _only_ the outputs without the corresponding LilyPond source is somewhat anticlimactic. I sure am not the only one who naturally goes Wow, how was _this_ done? when looking at (some of) the examples. There are 2 practical problems with doing this. The first is that these examples are all small extracts of much bigger pieces - they are reduced to a single line simply to illustrate what's possible and are displayed on the examples page as png files which have been manipulated by an image processor to get them to the size they are. To provide a link to lilypond code that produces the examples as they are would require quite a bit of work in cutting down the much larger scores. The second is that, as examples of the complexity of score that can be produced, then I have no doubt that some of them have quite complex tweaks (albeit I've not read them to check). Showing this to a beginner would likely scare them off even bothering to download the source. In contrast, starting at http://lilypond.org/doc/v2.14/Documentation/learning/index.html is designed to lead beginners in gently. I would also make the point that if a beginner browses a little further, they will get to http://lilypond.org/text-input.html which is even simpler. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Comment #3 on issue 1834 by philehol...@googlemail.com: Website: provide link to .ly for examples http://code.google.com/p/lilypond/issues/detail?id=1834 My comments in response to the debate on -bugs: (I'd also add that the .ly files don't appear to be in the build tree and so a system for adding them to the built website would need to be added to the build system, plus a way of fixing up the links to them. Volunteers please form a queue.) There are 2 practical problems with doing this. The first is that these examples are all small extracts of much bigger pieces - they are reduced to a single line simply to illustrate what's possible and are displayed on the examples page as png files which have been manipulated by an image processor to get them to the size they are. To provide a link to lilypond code that produces the examples as they are would require quite a bit of work in cutting down the much larger scores. The second is that, as examples of the complexity of score that can be produced, then I have no doubt that some of them have quite complex tweaks (albeit I've not read them to check). Showing this to a beginner would likely scare them off even bothering to download the source. In contrast, starting at http://lilypond.org/doc/v2.14/Documentation/learning/index.html is designed to lead beginners in gently. I would also make the point that if a beginner browses a little further, they will get to http://lilypond.org/text-input.html which is even simpler. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
lilyp...@googlecode.com writes: Comment #2 on issue 1834 by colinpkc...@gmail.com: Website: provide link to .ly for examples http://code.google.com/p/lilypond/issues/detail?id=1834 Summarising comments on bug-lilypond: The examples are often too complex and lengthy to be really useful to beginners. As above, they wouldn't work in mouse-over bubbles. The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. If that is feasible, it would show the text from the corresponding point in the source up to (but not including) the next point in the source corresponding to a different graphical element. The disadvantage of this particular mechanical way might be that tweaks and overrides would likely end up in the bubble of the graphical element before the element they actually affect. One would need to try this out in order to see how one would create best extracts. I am not convinced that this would be worthless. The source of the examples has value, both as a snippet, and as a teaching tool. It would not meet the label snippet usually. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
On Aug 24, 2011, at 3:19 PM, David Kastrup wrote: lilyp...@googlecode.com writes: Comment #2 on issue 1834 by colinpkc...@gmail.com: Website: provide link to .ly for examples http://code.google.com/p/lilypond/issues/detail?id=1834 Summarising comments on bug-lilypond: The examples are often too complex and lengthy to be really useful to beginners. As above, they wouldn't work in mouse-over bubbles. The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. If that is feasible, it would show the text from the corresponding point in the source up to (but not including) the next point in the source corresponding to a different graphical element. The disadvantage of this particular mechanical way might be that tweaks and overrides would likely end up in the bubble of the graphical element before the element they actually affect. One would need to try this out in order to see how one would create best extracts. I am not convinced that this would be worthless. The source of the examples has value, both as a snippet, and as a teaching tool. It would not meet the label snippet usually. I think it'd be great to have a How does one make that? link that shows step by step, exactly like Urs's tutorial, how to get from a blank LilyPond document to the final result with ample description and many links to the relevant docs. That way, people's curiosity can be satiated without feeling overwhelmed. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Am Mittwoch, 24. August 2011, 15:19:57 schrieb David Kastrup: lilyp...@googlecode.com writes: The examples are often too complex and lengthy to be really useful to beginners. As above, they wouldn't work in mouse-over bubbles. The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. In my eyes, this would defeat the purpose of the examples page. Our message to newcomers there is Look, how beautiful LilyPond scores can be. If we force a mouse-over bubble with lilypond code on every visitor, then the message becomes You can do pretty scores, but just look how terribly complicated and uncomprehensible it is to write a score with lilypond. Will that incite any non-programmer to use lilypond? The main purpose of the examples page is to show off beautiful engravings with LilyPond. It is aimed at people who have never seen or used lilypond. We really don't want to show code there -- that what the LM / NR is for. However, IF some lilypond user wants to see the code for the examples, it should be easier to get it than using git to check it out from the source code. Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs can make dynamics and articulations overlap
Am 23.08.2011 15:00, schrieb Mike Solomon:
On Aug 23, 2011, at 2:52 PM, Colin Campbell wrote:
On 11-08-23 02:49 AM, Urs Liska wrote:
Hi list,
in some situations slurs can squeeze dynamics and articulaions causing a
collision.
\version 2.15.8
\score {
\new PianoStaff
\new Staff = upper {
\voiceTwo
f''2-\ff(
\change Staff = lower
c'')
}
\new Staff = lower {
s1
}
}
produces the attached output.
I'm not sure whether the two staves are necessary to reproduce it. The relevant
aspects seem to be:
* accent and dynamics are both below the note (through \voiceTwo)
* The slur starts below them.
I didn't find a relevant issue report. Sorry if I didn't look close enough.
Best
Urs
I believe Mike Solomon is doing a lot of work with collisions, and particularly
with slurs, Urs. He has a couple of patches in the review process which may
fix your problem.
Cheers,
Colin
Hey Urs,
I'll try to test this out on my patch later today or tomorrow and will let you
know if it fixes the problem.
Cheers,
MS
Thanks a lot.
If not please tell me and I submit an issue report.
Best
Urs
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Reinhold Kainhofer reinh...@kainhofer.com writes: Am Mittwoch, 24. August 2011, 15:19:57 schrieb David Kastrup: lilyp...@googlecode.com writes: The examples are often too complex and lengthy to be really useful to beginners. As above, they wouldn't work in mouse-over bubbles. The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. In my eyes, this would defeat the purpose of the examples page. Our message to newcomers there is Look, how beautiful LilyPond scores can be. If we force a mouse-over bubble with lilypond code on every visitor, No force here. He can move the mouse away. then the message becomes You can do pretty scores, but just look how terribly complicated and uncomprehensible it is to write a score with lilypond. Will that incite any non-programmer to use lilypond? You won't get them to use Lilypond without using Lilypond. You can't hide that. It is pointless. One can do pretty scores with Inkscape. Probably prettier than you can ever hope to do with Lilypond. But you hopefully won't convince anybody to do his scores with Inkscape. Because then he needs to become an excellent engraver as well as an excellent graphics master. With Lilypond, all the information is in the source. Write that source, no matter with what tool or editor, and the score will fall out. The effort that a typical score has per note or graphical element is not terribly complicated and uncomprehensible but rather startingly short and comprehensible. For me, that is a selling point. There is no point in hiding that from somebody who we wish to start using Lilypond. It is not even possible. If he is adverse to writing and reading plain text source, there is no way he is going to use Lilypond without noticing. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
On Wed, Aug 24, 2011 at 03:35:18PM +0200, Reinhold Kainhofer wrote: Am Mittwoch, 24. August 2011, 15:19:57 schrieb David Kastrup: The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. A mouse-over bubble, or clickable png with a separate frame for text, would be awesome for the Learning manual. That's an old (5+ years) request. In my eyes, this would defeat the purpose of the examples page. Yes. However, IF some lilypond user wants to see the code for the examples, it should be easier to get it than using git to check it out from the source code. They can use webgit instead? Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Graham Percival gra...@percival-music.ca wrote in message news:20110824161038.GA2459@bluespark... On Wed, Aug 24, 2011 at 03:35:18PM +0200, Reinhold Kainhofer wrote: Am Mittwoch, 24. August 2011, 15:19:57 schrieb David Kastrup: The mouse-over bubble would show a looking-glass view into the source, centered at the corresponding view. A mouse-over bubble, or clickable png with a separate frame for text, would be awesome for the Learning manual. That's an old (5+ years) request. In my eyes, this would defeat the purpose of the examples page. Yes. However, IF some lilypond user wants to see the code for the examples, it should be easier to get it than using git to check it out from the source code. They can use webgit instead? Cheers, - Graham If this is really wanted, it strikes me that the best way to do it would be a new page (examples-detail.xxx) with all the examples and output from them in full. Still not convinced it won't scare more off than if encourages, though. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
On Wed, 24 Aug 2011 18:10:38 +0200 Graham Percival wrote: On Wed, Aug 24, 2011 at 03:35:18PM +0200, Reinhold Kainhofer wrote: However, IF some lilypond user wants to see the code for the examples, it should be easier to get it than using git to check it out from the source code. They can use webgit instead? Fine (if this is the most we can agree upon, that is; I still tend to think a more friendly presentation of the sources would be in order), but in that case could there at least be links right next to the images? -- Štěpán ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests.
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1833 by pkx1...@gmail.com: Deprecate \fermataMarkup for full-bar rests. http://code.google.com/p/lilypond/issues/detail?id=1833 Passes Make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 1529 by pkx1...@gmail.com: filename changing should not
trigger a regtests comparison
http://code.google.com/p/lilypond/issues/detail?id=1529
passes make but reg test check fails
--snip--
reading input/regression/midi/out-test-baseline/key-option-midi.profile
reading input/regression/midi/out-test/key-option-midi.profile
reading input/regression/midi/out-test-baseline/tree.gittxt
reading input/regression/midi/out-test/tree.gittxt
no source for __main__.GitFileCompareLink instance at 0xd85d80c
Traceback (most recent call last):
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 1278, in module
main ()
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 1275, in main
compare_tree_pairs (zip (args[0::2], args[1::2]), out,
options.threshold)
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 990, in compare_tree_pairs
data.print_results (threshold)
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 982, in print_results
self.write_text_result_page ('', threshold)
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 926, in write_text_result_page
(changed, below, unchanged) = self.thresholded_results (threshold)
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 908, in thresholded_results
for link in self.file_links.values ()]
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 365, in distance
self._distance = self.calc_distance ()
File /home/jlowe/lilypond-git/build/scripts/build/out/output-distance,
line 487, in calc_distance
diff = difflib.unified_diff (cont0.split ('\n'),
NameError: global name 'difflib' is not defined
make: *** [local-check] Error 1
jlowe@jlowe-lilybuntu2:~/lilypond-git/build$
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1834 in lilypond: Website: provide link to .ly for examples
Comment #4 on issue 1834 by percival.music.ca: Website: provide link to .ly for examples http://code.google.com/p/lilypond/issues/detail?id=1834 Well, nobody found my previous thoughts on the matter, but a lot of people voiced the same concerns. Bottom line: if you want to work on this, it'll probably take 3-6 drafts. You'll need to work with texinfo, possibly javascript, and possibly the build system. Most of your work (in producing drafts) will be rejected because I don't like the way it looks or feels. ETA: 10 hours, assuming previous familiarity with html+css (+javascript if you want to investigate that option). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1822 in lilypond: New short and long lyric ties.
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1822 by pkx1...@gmail.com: New short and long lyric ties. http://code.google.com/p/lilypond/issues/detail?id=1822 i can't test this. So someone else needs to review this properly. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars
Updates: Labels: -Patch-new Patch-review Comment #2 on issue 905 by pkx1...@gmail.com: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars http://code.google.com/p/lilypond/issues/detail?id=905 passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1494 in lilypond: including alternate fonts
Updates: Labels: -Patch-needs_work Patch-abandoned Comment #5 on issue 1494 by colinpkc...@gmail.com: including alternate fonts http://code.google.com/p/lilypond/issues/detail?id=1494 Is this still active? There is no comment on the tracker since July 13 and the Rietveld issue is unchanged in 6 months. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1582 in lilypond: flag variants patch
Updates: Labels: -Patch-needs_work Patch-abandoned Comment #4 on issue 1582 by colinpkc...@gmail.com: flag variants patch http://code.google.com/p/lilypond/issues/detail?id=1582 No updates since April. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1143 in lilypond: [PATCH]New patch for waveforms
Updates: Labels: -Patch-needs_work Patch-abandoned Comment #4 on issue 1143 by colinpkc...@gmail.com: [PATCH]New patch for waveforms http://code.google.com/p/lilypond/issues/detail?id=1143 Not on Rietveld, and no changes in a year. May have been related to R 1720046. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
