property to set voiced-rest positions; issue 3902 (issue 188580043 by k-ohara5...@oco.net)
https://codereview.appspot.com/188580043/diff/1/lily/rest.cc File lily/rest.cc (right): https://codereview.appspot.com/188580043/diff/1/lily/rest.cc#newcode75 lily/rest.cc:75: Real vpos = dir * robust_scm2int (me-get_property (voiced-position), 0); Shouldn't the fallback remain 4 rather than 0? https://codereview.appspot.com/188580043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Clarified how to use clip-systems option (issue 186640043 by pkx1...@gmail.com)
Thanks
https://codereview.appspot.com/186640043/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
https://codereview.appspot.com/186640043/diff/1/Documentation/notation/input.itely#newcode2541
Documentation/notation/input.itely:2541: This will extract a single
fragment of the input file @code{starting}
On 2015/01/02 13:53:59, thomasmorley651 wrote:
Should @code{starting} be @emph{starting} ?
Done.
https://codereview.appspot.com/186640043/diff/1/Documentation/notation/input.itely#newcode2559
Documentation/notation/input.itely:2559: @ref{The layout block,,The
@code{@bs{}layout} block}.
On 2015/01/02 14:29:17, Jean-Charles wrote:
No need for a third argument:
@ref{The layout block} references the @node but will be rendered like
the
corresponding @sectioning argument (The @code{@bs{}layout} block)
Done.
https://codereview.appspot.com/186640043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Edit Kievan documentation (issue 193890043 by aleksandr.andr...@gmail.com)
1. I cannot find a tracker for this issue (is that important for translations?). 2 I cannot find an equivalent set of entries in the English documentation. It looks like these translations are now out of sync with the English one. Can someone please check? https://codereview.appspot.com/193890043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Edit Kievan documentation (issue 193890043 by aleksandr.andr...@gmail.com)
On 2015/01/04 12:13:31, J_lowe wrote: 1. I cannot find a tracker for this issue (is that important for translations?). The tracker is here: https://code.google.com/p/lilypond/issues/detail?id=4241 2 I cannot find an equivalent set of entries in the English documentation. It looks like these translations are now out of sync with the English one. Can someone please check? It's in the English documentation here: http://lilypond.org/doc/v2.18/Documentation/notation/typesetting-kievan-square-notation There is some old code in the French and German documentation, which is what is being fixed with this patch. The German documentation is missing the subsection Kievan melismata, but I did not work on this. Best if whoever is supporting the German doc looks at that. Is there any way to update the doc on the website now, or do we have to wait for the release cycle? https://codereview.appspot.com/193890043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Edit Kievan documentation (issue 193890043 by aleksandr.andr...@gmail.com)
On 2015/01/04 13:17:15, aleksandr.andreev wrote: On 2015/01/04 12:13:31, J_lowe wrote: 1. I cannot find a tracker for this issue (is that important for translations?). The tracker is here: https://code.google.com/p/lilypond/issues/detail?id=4241 2 I cannot find an equivalent set of entries in the English documentation. It looks like these translations are now out of sync with the English one. Can someone please check? It's in the English documentation here: http://lilypond.org/doc/v2.18/Documentation/notation/typesetting-kievan-square-notation Thank you. But remember we are on 2.19 now. http://lilypond.org/doc/v2.19/Documentation/notation/typesetting-kievan-square-notation That still all looks the same though. There is some old code in the French and German documentation, which is what is being fixed with this patch. The German documentation is missing the subsection Kievan melismata, but I did not work on this. Best if whoever is supporting the German doc looks at that. Can you create a tracker for that or make sure that there is an email to the translation lists for this specific thing? Is there any way to update the doc on the website now, or do we have to wait for the release cycle? http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#release-work As long as you have permissions, anyone can update the website. But it is done (as far as I am aware) when we have a new release (minor or otherwise). James https://codereview.appspot.com/193890043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Doc: Clarified how to use clip-systems option (issue 186640043 by pkx1...@gmail.com)
LGTM https://codereview.appspot.com/186640043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ly:line-interface::print should read ly:line-spanner::print in NR (issue 186650043 by thomasmorle...@gmail.com)
To get used to the workflow again, a two-liner. Please review https://codereview.appspot.com/186650043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Possible tweaks to the appearance of the website
Greetings LilyPond developers, Over the last few weeks I had some time and found myself experimenting with the appearance of the LilyPond website, especially the main navigation bars/menus at the top of each page. You can see a sketch of what I've come up with at the following URL: (Take out the two spaces, inserted here to help prevent web crawlers from finding and indexing these temporary pages. A robots.txt file is also in place to prevent this.) http://clairnote.org / lilypond-web-demo/ No big redesign, just some fairly subtle tweaks to the current one. If those who make such decisions like what they see, I can submit the changes through the proper channels. Let me know what you think. Some notes follow. Cheers, -Paul Notes: - Almost all the changes are CSS changes (presentation rather than content). - I've used CSS gradients instead of background images wherever possible. This eliminates the need to download 23 background image files, providing some small benefit to page load times and server load. CSS gradients are now well supported by browsers, except for IE9 and earlier (which should just display a solid color fallback). See: http://caniuse.com/#feat=css-gradients https://developer.mozilla.org/en-US/docs/Web/CSS/linear-gradient - The gradients of the main nav bar are more subtle, like the gradients in other places. - Active headings are a darker shade rather than being a reversed gradient. - The second nav bar is simplified to one consistent color, making it clearer which is the active heading. - The home page link/heading is LilyPond rather than the lily icon. Since LilyPond is not a big-budget commercial brand with a well known logo, having LilyPond here seemed like a good idea. Also the icon is a bit too tall to fit comfortably in the space, and if shrunk for a better fit it would be less clear what it is. The width of this link/heading now matches the others instead of being smaller. - The search box is slightly smaller and light green to give the main nav bar a more smooth and solid look. - The light-green-to-white fade in the background is in both top left and top right corners of the page. Since the site is a centered design this is more symmetrical. The white on green diagonal staff is removed for a simpler and less distracting look. (This is done with CSS gradients, but ultimately images may provide better results in some browsers (e.g. Chrome)). - The CSS file needs some clean up, since previous code has mostly been commented out for now. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Possible-tweaks-to-the-appearance-of-the-website-tp170094.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Google blocks git-cl-upload
Hi all, I had some difficulties uplaoding my recent patch (via: git-cl upload), because google blocked me. I had to lower security settings in my google-account. Others with that experience? Other way to make it work than lowering security? Cheers, Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
GUB update
A restatement of what is happening with GUB builds, and therefore an appeal for help. The current aim is to update gcc so it will compile more up to date template syntax, and my target has been gcc 4.8.2. The previous version was 4.1.1. I'm working with a new virtual machine running Ubuntu 14.04. The principle with GUB is that it has details of all the packages it uses, and by issuing the 'make bootstrap' command, it goes and gets all the packages it needs, and all their dependencies, and builds them all from scratch. The problem I believe I now have is that gcc 4.8 has a new dependency: GMP, the multi-precision library. I believe this is a dependency from the newer version of MPFR that gcc 4.8 requires. As it stands, GUB is unaware of this dependency, and so makes no attempt to download or install MPC. This meant that the gcc build stopped with the following error: checking for the correct version of gmp.h... buggy but acceptable checking for the correct version of mpfr.h... yes checking for the correct version of mpc.h... no Following the guidance here, I downloaded and installed mpc manually. This overcame that problem, but I now get: checking for the correct version of gmp.h... buggy but acceptable checking for the correct version of mpfr.h... yes checking for the correct version of mpc.h... yes checking for the correct version of the gmp/mpfr/mpc libraries... no I assume what is happening here is that the manual install places the mpc libraries where the gcc configur can't find them. In any case, doing this manually defeats the object of a self-building package builder. So what would be really helpful would be for someone who understands all the python stuff that GUB does could point me to how to add the new dependency to GUB for MPC. Thanks. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Possible tweaks to the appearance of the website
Thanks for your thoughts Phil. More below... Phil Holmes-2 wrote I would say that some of the changes are a matter of personal aesthetics, and so it's not possible to say which is better: it's just taste. And if you say that much of this is tidying and improving, then I wouldn't object. However, there are some proposals that I don't think are goers. I've attached 3 screenshots as illustration: 2 from Chrome (before and after) and one from IE9 (after). The major issue is that the nav bar is not present in IE. I understand IE9 is out of date, but many people use and prefer it over later versions, and for some applications you can't upgrade and have them still work. So we do need a web site that works in IE9. I totally agree. I just hadn't seen this, as I hadn't tested it on IE yet. (I have to make a trip to the library to access a windows machine for this.) So definitely, this would need to be fixed, which shouldn't be difficult (knock on wood). Phil Holmes-2 wrote In chrome, I prefer the little Lily icon, and we seem to have lost the music image in the background, which I also quite liked. I mentioned my take on these things in my previous message, but as you say, much of this stuff comes down to personal aesthetics, so if the decision is to keep one or both of the lily icon and background music image, then so be it. Cheers, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Possible-tweaks-to-the-appearance-of-the-website-tp170094p170098.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Possible tweaks to the appearance of the website
Phil Holmes wrote Sunday, January 04, 2015 4:10 PM The major issue is that the nav bar is not present in IE. I understand IE9 is out of date, but many people use and prefer it over later versions, and for some applications you can't upgrade and have them still work. So we do need a web site that works in IE9. In chrome, I prefer the little Lily icon, and we seem to have lost the music image in the background, which I also quite liked. I agree with Phil on all these points. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB fail with smob templates
The changes from Masamichi to librestrict look safe, and the later floating-point-endless-loop-eating-all-memory should be gone now that I've re-worked the skyline merge code. If gcc 4.8.2 still looks difficult, I'll look into problem with the templates. Now, in this branch, https://github.com/trueroad/gub/tree/gcc-4.8 The following commands have been succeed by gcc-4.8.2. bin/gub mingw::lilypond-installer bin/gub linux-x86::lilypond-installer bin/gub linux-64::lilypond-installer bin/gub freebsd-x86::lilypond-installer bin/gub freebsd-64::lilypond-insatller They work fine in my environments. mingw: bad_alloc don't occur. freebsd-x86: SIGSEGV don't occur. Correct PDFs are generated. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ly:line-interface::print should read ly:line-spanner::print in NR (issue 186650043 by thomasmorle...@gmail.com)
LGTM. https://codereview.appspot.com/186650043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Possible tweaks to the appearance of the website
Hi Paul, thanks for sticking your head into this. Some comments from my side below. Am 04.01.2015 um 16:32 schrieb Paul Morris: Greetings LilyPond developers, Over the last few weeks I had some time and found myself experimenting with the appearance of the LilyPond website, especially the main navigation bars/menus at the top of each page. You can see a sketch of what I've come up with at the following URL: (Take out the two spaces, inserted here to help prevent web crawlers from finding and indexing these temporary pages. A robots.txt file is also in place to prevent this.) http://clairnote.org / lilypond-web-demo/ No big redesign, just some fairly subtle tweaks to the current one. If those who make such decisions like what they see, I can submit the changes through the proper channels. I think there is no official entity who makes such decisions. It's rather like someone uploading a patch and others objecting against it or not. As I experienced changes to the website are expected to raise more objections than obscure changes to the code, simply because anybody can have an opinion about the topic. Let me know what you think. Some notes follow. Cheers, -Paul Notes: - Almost all the changes are CSS changes (presentation rather than content). - I've used CSS gradients instead of background images wherever possible. Sounds like a good idea. This eliminates the need to download 23 background image files, providing some small benefit to page load times and server load. CSS gradients are now well supported by browsers, except for IE9 and earlier (which should just display a solid color fallback). See: http://caniuse.com/#feat=css-gradients https://developer.mozilla.org/en-US/docs/Web/CSS/linear-gradient - The gradients of the main nav bar are more subtle, like the gradients in other places. I think this is an improvement. Looks more even and slightly more modern. However, when IE = 9 doesn't support that it's clearly not an option. But I think I'd prefere a browser switch over discarding the idea altogether. - Active headings are a darker shade rather than being a reversed gradient. This is definitely an improvement. I found that reversed gradient always annoying. - The second nav bar is simplified to one consistent color, making it clearer which is the active heading. I prefer that too, but the contrast between active and non-active item should be more. Probably I'd make the non-active backgrounds a little bit lighter. - The home page link/heading is LilyPond rather than the lily icon. Since LilyPond is not a big-budget commercial brand with a well known logo, having LilyPond here seemed like a good idea. Also the icon is a bit too tall to fit comfortably in the space, and if shrunk for a better fit it would be less clear what it is. The width of this link/heading now matches the others instead of being smaller. I'm undecided about that. I wouldn't miss that image too much, but OTOH it gives some liveliness to the page header. Apart from that I'm not sure that LilyPond is the right term here. LilyPond - Introduction - Download doesn't seem like a natural sequence. Actually it's Home, isn't it? - The search box is slightly smaller and light green to give the main nav bar a more smooth and solid look. LGTM. - The light-green-to-white fade in the background is in both top left and top right corners of the page. Since the site is a centered design this is more symmetrical. The white on green diagonal staff is removed for a simpler and less distracting look. (This is done with CSS gradients, but ultimately images may provide better results in some browsers (e.g. Chrome)). I think I'd miss the background score here. The symmetry is a good idea, so maybe we could have some kind of continuation on the right hand side, either the end of the same system or an example of a different kind of notation. On my system (Chrome on Linux) the gradients don't look good and show quite annoying stripes. So maybe an image would be indeed better here. Best Urs - The CSS file needs some clean up, since previous code has mostly been commented out for now. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Possible-tweaks-to-the-appearance-of-the-website-tp170094.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES: Countdown for January 7th. 2014
Hello, Here is the current patch countdown list. The next countdown will be on January 7th. You can always view the most current countdown list here: http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaitingcolspec=Patch%20Owner%20ID%20Summarysort=patch PUSH: David Kastrup: Patch: lilypond-what-beat.el: make No | before point a message rather than an error http://code.google.com/p/lilypond/issues/detail?id=4237 David Kastrup: Patch: lilypond-what-beat.el: heed stand-alone durations in music lengths http://code.google.com/p/lilypond/issues/detail?id=4234 Dan Eble: Patch: Improve partcombine multi-measure rest handling. http://code.google.com/p/lilypond/issues/detail?id=4233 David Kastrup: Patch: lilypond-what-beat.el: Allow \tuplet to work like \times http://code.google.com/p/lilypond/issues/detail?id=4232 Keith OHara: inefficient code in auto-beaming http://code.google.com/p/lilypond/issues/detail?id=4231 Keith OHara: trying to freeze in time from unusual time signatures http://code.google.com/p/lilypond/issues/detail?id=4180 COUNTDOWN: James Lowe: Doc: Contributor Guide - be more explicit for Guile Version 1.8.2 http://code.google.com/p/lilypond/issues/detail?id=4228 Dan Eble: Breathing_sign: possible use of uninitialized data http://code.google.com/p/lilypond/issues/detail?id=4212 Dan Eble: Remove single-C time signature style http://code.google.com/p/lilypond/issues/detail?id=4186 REVIEW: Thomas Morley: ly:line-interface::print should read ly:line-spanner::print in NR http://code.google.com/p/lilypond/issues/detail?id=4244 James Lowe: Patch: Doc: remove unneeded subheading on GSoC page http://code.google.com/p/lilypond/issues/detail?id=4243 Keith OHara: make \shiftOff useful http://code.google.com/p/lilypond/issues/detail?id=4242 Aleksandr Andreev: Patch: Edit Kievan documentation http://code.google.com/p/lilypond/issues/detail?id=4241 James Lowe: Usage: Added note about having to use clip-regions with dclip-systems in *.ly file http://code.google.com/p/lilypond/issues/detail?id=4219 Keith OHara: Patch: Add regtests for numbered and single-digit time signature styles http://code.google.com/p/lilypond/issues/detail?id=4176 Keith OHara: the position of the initial \voiceOne rest is suboptimal http://code.google.com/p/lilypond/issues/detail?id=3902 WAITING: Urs Liska: Patch: Add original-breaks.ly commands http://code.google.com/p/lilypond/issues/detail?id=4155 Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures http://code.google.com/p/lilypond/issues/detail?id=3918 Mike Solomon: Patch: Prevents vertical axis groups with empty skylines http://code.google.com/p/lilypond/issues/detail?id=3156 Mike Solomon: Patch: Removes the translate_axis call from axis-group-interface outside-staff positioning. http://code.google.com/p/lilypond/issues/detail?id=3134 David Kastrup: Patch: Implement music functions in Scheme rather than C++ http://code.google.com/p/lilypond/issues/detail?id=2716 Thank you, James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Google blocks git-cl-upload
On 04/01/15 15:36, Thomas Morley wrote: Hi all, I had some difficulties uplaoding my recent patch (via: git-cl upload), because google blocked me. I had to lower security settings in my google-account. Others with that experience? Yep. Other way to make it work than lowering security? I've not been able to find anything. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \articulate problem
Patrick == Patrick or Cynthia Karl pck...@me.com writes:
Patrick [1 text/plain; utf-8 (quoted-printable)]
On Dec 28, 2014, at 1:15 AM, Peter Chubb
lily.u...@chubb.wattle.id.au wrote:
Patrick == Patrick or Cynthia Karl pck...@me.com writes:
Interesting.
The problem is in the Prall rendition:
It comes out as:
{ d'' 32 c'' d'' c'' 1*-1/32 }
This is generated from a ly:music-compress function applied to {
d''32 c'' d'' c'' } to squash it to the same length as the
original semiquaver.
I have no idea where that 1*-1/32 comes from , but that's where the
`backwards in midi time' message originates, I think.
Patrick I’m replying directly to you rather than to the list as I
Patrick suspect few if any would be interested.
Patrick I would suggest that the 1/32 comes from the following line
Patrick in articulate.ly http://articulate.ly/ at version 2.19.15:
Patrick (line 691) (newlen (ly:moment-sub totallength (ly:make-moment
Patrick 3/32)))
Yup that's bogus. I've finally made time to look at it.
I've refactored the code, and used compress-music to make the
ornaments fit. Try the attached, please.
articulate.ly
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Possible tweaks to the appearance of the website
Thanks Urs and Trevor for chiming in. I've made another version that can be seen here: http://clairnote.org / lilypond-web-demo2/ (just remove the spaces as before...) The background image is restored and I managed to get the Lily icon with LilyPond appearing next to it in the main nav bar. The secondary nav bar has its own color (from the site's current color scheme) for greater visual contrast with the main nav bar. Those are the main differences. Let me know what you think. Also, I made it to the library and IE8 and IE9 should be in good shape. Let me know if not. Instead of gradients these browsers will fall back to solid colors giving the site a flatter look. (It would be possible to achieve the gradients with these browsers too by creating an image for each gradient. A separate CSS file could be loaded only for these browsers using conditional comments, that would use these images.) (Urs, sorry I'm not getting to your comments right now since I need to get some sleep.) Cheers, -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Possible-tweaks-to-the-appearance-of-the-website-tp170094p170119.html Sent from the Dev mailing list archive at Nabble.com. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB update
On Sun, Jan 04, 2015 at 04:33:05PM +, Phil Holmes wrote: I assume what is happening here is that the manual install places the mpc libraries where the gcc configur can't find them. In any case, doing this manually defeats the object of a self-building package builder. So what would be really helpful would be for someone who understands all the python stuff that GUB does could point me to how to add the new dependency to GUB for MPC. Wouldn't it be here? https://github.com/gperciva/gub/blob/master/gub/specs/gcc.py#L16 However, first you need to add a mpc.py in that directory. The contents of that file should start of being something like https://github.com/gperciva/gub/blob/master/gub/specs/tar.py (picked fairly randomly) Note the toolsAutoBuild part -- if MPC is autotools, then the configure should be relatively straightforward. Maybe even something like https://github.com/gperciva/gub/blob/master/gub/specs/faac.py (again chosen randomly) I'm sure that right now you're wondering why some (most?) of the spec files are much much nastier than faac.py. The answer is that pretty much all of that nastiness is working around bugs in the original package's build systems. After you add mpc.py, test that in isolation before trying make bootstrap. It's entirely plausible (or even likely!) that you'll be able to build mpc with the default ubuntu, but it'll fail on some cross-compilation step. But check the native build first. :) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Chord pipelines
On 11/22/14 9:35 AM, David Kastrup d...@gnu.org wrote: Hi together, I am currently contemplating our chord support and it appears rather badly modularized to me. SNIP This is one area where the existing possibilities for customization (like the chord naming functions in context properties) are of such limited usefulness that I would consider incompatibility with code using these hooks an acceptable price to pay for a sane and versatile redesign. I totally agree that a sane and versatile redesign of LilyPond's Chords system would be helpful. Code incompatibility would be fine if the resulting system were cleaner, less complicated, and more extensible. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
