Re: Git problem
Graham Percival gra...@percival-music.ca writes:
On Thu, Mar 08, 2012 at 05:24:51PM -, Phil Holmes wrote:
One thought. Some issues are best verified by checking lily output
- http://code.google.com/p/lilypond/issues/detail?id=2246 for
example. Can we break a normal rule and check these against a newly
made binary? What we'd then be doing is saying it was in the GUB
binary and is still in master, so I'm going to verify.
I can make a binary despite the existing issues to verify in this
case.
Ok, let's check the diff:
git diff --stat release/2.15.3{2,3}-1
Documentation/de/notation/spacing.itely|2 +-
Documentation/de/search-box.ihtml | 15 +-
Documentation/de/usage.tely|2 +-
Documentation/de/usage/external.itely | 104 ++-
Documentation/de/usage/lilypond-book.itely | 217 ++-
Documentation/de/usage/running.itely | 242 ++--
Documentation/de/usage/updating.itely | 12 +-
Documentation/fr/extending.tely| 78 +
.../fr/extending/programming-interface.itely | 345 +++--
Documentation/fr/extending/scheme-tutorial.itely | 1649
Documentation/ja/learning.tely |2 +-
Documentation/ja/learning/templates.itely |3 +-
Documentation/ja/learning/tweaks.itely | 294 ++--
Documentation/ja/notation.tely |4 +-
Documentation/ja/notation/percussion.itely |2 +-
Documentation/ja/notation/pitches.itely| 82 +-
Documentation/ja/notation/rhythms.itely| 414 --
Documentation/ja/notation/wind.itely |2 +-
Documentation/lilypond-texi2html.init |2 +-
.../snippets/alternative-bar-numbering.ly |2 +-
Documentation/snippets/alternative-breve-note.ly |2 +-
.../snippets/formatting-lyrics-syllables.ly|8 -
Documentation/snippets/glissandi-can-skip-grobs.ly |2 +-
.../snippets/lyrics-old-spacing-settings.ly|2 +-
Documentation/snippets/strict-beat-beaming.ly |2 +-
Documentation/translations.itexi |3 +-
Documentation/web/community.itexi | 199 +++
Documentation/web/news-front.itexi | 33 +-
Documentation/web/news.itexi |2 +-
VERSION|4 +-
lily/book-scheme.cc| 13 +
lily/span-bar-stub-engraver.cc | 77 +-
ly/gregorian.ly| 34 +-
scripts/build/extract_texi_filenames.py|3 +-
So all issues that were fixed and verified in 2.15.32 and that did _not_
touch any of the given files are fine.
Let's take a list at the concerned commits:
git log --oneline release/2.15.30-1..release/2.15.33-1 `git diff --name-only
release/2.15.3{2,3}-1`
4276123 Release: update news.
2944a83 Merge branch 'fixedtranslation' into HEAD
5697144 Merge branch 'fixedmerge' into HEAD
46d2580 Release: bump version.
a5ff05c Release: update news.
abf0836 web: typo fix
f235881 LSR updates
c2c6d15 Local update of LSR
706417f Implement ly:book? and ly:context-def? predicates
8841948 WebCG: remove projects from HelpUs
32b9cd0 Fix issue 2359: example code in German and English docs should be the sa
9d1520b Merge branch 'lilypond/translation' into staging
744709d add ly:book-set-header!
2ccfd5a Prevents segfault in Span_bar_stub_engraver through derived_mark.
cc5223a Web: add GSoC ideas list
ab45be2 Doc-fr: enable Extending * master file * Scheme tutorial (first deli
2bba3b6 Fix Issue 2380: formatting of lyrics, \versus and \respondum
308c694 Web: Announcement update for the new LilyPond Report
fe2e679 Make extract-texi-filenames ignore comments
418adb3 Release: bump version.
3c62ac1 Doc-ja: update LM and NR
273e6b7 Merge remote branch 'origin' into release/unstable
7186f20 Release: update news.
acb4ce2 Web: encourage users to comment on existing bugs
d1141b3 web: rephrase bugreports section
dadabdf Doc-de: updates to usage manual
17bce3f Doc-de: update search-box
3597c42 Doc: update translation status.
e885a8c Merge branch 'lilypond/translation' into staging
55d9ad3 Release: bump version.
ea270d9 Release: update news.
be3a3ba web: typo fix
85274e7 LSR updates
650f0c7 Local update of LSR
09814b5 Implement ly:book? and ly:context-def? predicates
ee5f21d WebCG: remove projects from HelpUs
7092c5b Doc: add translation status for German.
67e5286 Merge branch 'lilypond/translation' of ssh://git.sv.gnu.org/srv/git/lily
37b502a Doc-de: update bad commitishes
7c28d92 Merge branch 'master' into lilypond/translation
e29d5fc Doc: update translation status.
e7d1bb7 Doc: update snippets and run makelsr.
12cfe6b Doc-de: update the noation manual, adding snippet translations
4dbf906 Doc: update translation status.
9ce85aa Doc: update snippets and run makelsr.
Re: since when LilyPond supports unicode?
Janek, 2012/3/9 Janek Warchoł janek.lilyp...@gmail.com: Hi. i'd like to give precise information on how long Lily supports Unicode. I've searched changes on website, mailing lists and git history, but didn't find the date - can you help? cd $LILYPOND_GIT git grep unicode Just a quick glance shows me we mention 'stuff' in Changes around 2.10.x -- -- James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: since when LilyPond supports unicode?
On Fri, Mar 9, 2012 at 6:36 PM, James pkx1...@gmail.com wrote: Janek, 2012/3/9 Janek Warchoł janek.lilyp...@gmail.com: Hi. i'd like to give precise information on how long Lily supports Unicode. I've searched changes on website, mailing lists and git history, but didn't find the date - can you help? cd $LILYPOND_GIT git grep unicode Just a quick glance shows me we mention 'stuff' in Changes around 2.10.x They look like enhancements only in my opinion, and there's no entry in changes that would describe them: http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html - ? thanks, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: since when LilyPond supports unicode?
Le 09/03/2012 18:59, Janek Warchoł disait : On Fri, Mar 9, 2012 at 6:36 PM, Jamespkx1...@gmail.com wrote: Janek, 2012/3/9 Janek Warchołjanek.lilyp...@gmail.com: Hi. i'd like to give precise information on how long Lily supports Unicode. I've searched changes on website, mailing lists and git history, but didn't find the date - can you help? cd $LILYPOND_GIT git grep unicode Just a quick glance shows me we mention 'stuff' in Changes around 2.10.x November 2004 for the first appearance of utf-8/unicode They look like enhancements only in my opinion, and there's no entry in changes that would describe them: http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html - ? Is this what you mean? LilyPond 2.6 released - June 27, 2005 Version 2.6 is the latest stable release of LilyPond. It now installs in a snap on Windows, MacOS X, and any version of Linux (x86). Get up and running in minutes! Pango text formatting lets you print Unicode lyrics in your favorite script and font. Create SVG files, and edit them in Inkscape. /and/ January 02, 2005 LilyPond 2.5.6 was released. This is a technology preview release, which means that it has all kinds of nifty features, but is not actually usable for producing nicely printed scores. For this reason, an RPM of this release was not produced. The PS backend is now completely switched over to Pango/FontConfig: for -f ps, LilyPond only accepts UTF8 input, all text fonts are loaded through Pango, the TeX backend now offloads all metric computations to LaTeX, the SVG and GNOME backends are broken, most probably. Cheers, Jean-Charles ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Floating markup / Markup takes too much space
- Original Message - From: Frank Steinmetzger war...@gmx.de To: Phil Holmes m...@philholmes.net Sent: Friday, March 09, 2012 5:52 PM Subject: Re: Floating markup / Markup takes too much space On Fri, Mar 09, 2012 at 01:37:50PM -, Phil Holmes wrote: Dear list I am trying something new; I want to include a logo in my copyright line. I have here a one-page sheet consisting of a score and a markup block which contains the text for verses 2 to 4. Now according to annotate-spacing, I have 11.13pt of space left. The image in the screenshot was included with the command \epsfile #Y #6 #inc/filename.eps But even if I increase the image's height from 6 to a mere 7, the markup above is pushed to a second page. [...] There have been a _lot_ of changes in the spacing calculations between the version you're using and current stable, which is 2.14.2. I suggest trying with 2.14 and letting us know if the problems remain. Thanks for your answers. I was beginning to fear my questions became either too specific, too mundane or were dealt with many a time before, so you just didn't bother. :) Well, actually I was working and then singing. Other people were probably doing something similar. We answer as fast as we can, but it's better that you ask questions in plenty of time. Anyway, The canon of your answers is to upgrade -- and I agree. A version push request has been in the Gentoo bug tracker for ages now. I added a comment there that 2.16 is about to come out (as I recently read here). Back to topic: I built 2.14 from source which was easy thanks to Gentoo's infrastructure. Indeed I can enlarge the logo nicely with it, because it is a simple one-page piece. Bigger pieces, however, use a template with a modified variant of the titlepage snippet, which doesn't work properly with 2.14. This kind of migration work is what I dread most about the switch. Have you run convert-ly on the files in your project? Most of the time, this will fix upgrade issues automatically. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: since when LilyPond supports unicode?
On Fri, Mar 9, 2012 at 7:12 PM, Jean-Charles Malahieude lily...@orange.fr wrote: Le 09/03/2012 18:59, Janek Warchoł disait : On Fri, Mar 9, 2012 at 6:36 PM, Jamespkx1...@gmail.com wrote: Janek, 2012/3/9 Janek Warchołjanek.lilyp...@gmail.com: Hi. i'd like to give precise information on how long Lily supports Unicode. I've searched changes on website, mailing lists and git history, but didn't find the date - can you help? cd $LILYPOND_GIT git grep unicode Just a quick glance shows me we mention 'stuff' in Changes around 2.10.x November 2004 for the first appearance of utf-8/unicode They look like enhancements only in my opinion, and there's no entry in changes that would describe them: http://lilypond.org/doc/v2.12/Documentation/topdocs/NEWS.html http://lilypond.org/doc/v2.10/Documentation/topdocs/NEWS.html - ? Is this what you mean? LilyPond 2.6 released - June 27, 2005 Version 2.6 is the latest stable release of LilyPond. It now installs in a snap on Windows, MacOS X, and any version of Linux (x86). Get up and running in minutes! Pango text formatting lets you print Unicode lyrics in your favorite script and font. Create SVG files, and edit them in Inkscape. /and/ January 02, 2005 LilyPond 2.5.6 was released. This is a technology preview release, which means that it has all kinds of nifty features, but is not actually usable for producing nicely printed scores. For this reason, an RPM of this release was not produced. The PS backend is now completely switched over to Pango/FontConfig: for -f ps, LilyPond only accepts UTF8 input, all text fonts are loaded through Pango, the TeX backend now offloads all metric computations to LaTeX, the SVG and GNOME backends are broken, most probably. Yes, that's what i need. Thanks! Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond 2.15.33 kind-of a release candidate
LilyPond 2.15.30 is out; this is not a actual release candidate but it can be considered as an unofficial candidate. All users are invited to experiment with this version. New features since 2.14.2 are listed in the “Changes” manual on the website section about Development. http://lilypond.org/development.html There are no known Critical issues with this release. There will be an official release candidate, with a release countdown, in a few days. If you discover any problems, please send us Bug reports. http://lilypond.org/bug-reports.html - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
dropping support for osx 10.4 x86
lilypad will not work on osx 10.4 x86. It works on 10.4 ppc. I do not consider bugs in osx-10.4 x86 to be release-critical; they should be filed as normal type-build bugs. Somebody may want to update the download page accordingly to avoid giving users the wrong impression. If somebody can make 10.4-x86 work, then it would be great to officially support it again in the future. However, I think that's too far away; delaying 2.16.0 for that doesn't make sense. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dropping support for osx 10.4 x86
On Fri, Mar 09, 2012 at 07:51:20PM +, Graham Percival wrote: If somebody can make 10.4-x86 work, then it would be great to officially support it again in the future. However, I think that's too far away; delaying 2.16.0 for that doesn't make sense. oops, I should delay all emails by 5 minutes or something. In case anybody thinks I'm being unfair to osx users: one of the strongest reasons to move forward with 2.16 right now is so that we can get a stable lilypond in the hands of 10.7 users. Or, to put it in my terms, to make those annoying 'why doesn't lilypond run on 10.7?' people shut up. This decision is a balance between 10.7 users vs. 10.4-x86 users; the sanity of main developers vs. other stuff, etc. I think that moving forward with 2.16 is the right thing to do. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dropping support for osx 10.4 x86
On 3/9/12 12:57 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 09, 2012 at 07:51:20PM +, Graham Percival wrote: If somebody can make 10.4-x86 work, then it would be great to officially support it again in the future. However, I think that's too far away; delaying 2.16.0 for that doesn't make sense. oops, I should delay all emails by 5 minutes or something. In case anybody thinks I'm being unfair to osx users: one of the strongest reasons to move forward with 2.16 right now is so that we can get a stable lilypond in the hands of 10.7 users. Or, to put it in my terms, to make those annoying 'why doesn't lilypond run on 10.7?' people shut up. This decision is a balance between 10.7 users vs. 10.4-x86 users; the sanity of main developers vs. other stuff, etc. I think that moving forward with 2.16 is the right thing to do. I totally agree. There is no reason to add a separate download for lilypad on 10.4-x86. Users of 10.4-x86 can upgrade software, or they can use any other text editor to do lilypond work. The only thing not working is the GUI app, which isn't really necessary. I was going to propose this exact solution. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Cross-staff stem engraver (was: New frog in an empty pond?)
Quoting Carl Sorensen c_soren...@byu.edu: Ordinarily something like this would go in the regression tests: input/regression/cross-staff-stem-engraver.ly And then you would add it to your git repository, and post it on Rietveld for a review. OK, I'll do it. -- Regards, Pavel Roskin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond 2.15.33 kind-of a release candidate
On Fri, Mar 9, 2012 at 8:47 PM, Graham Percival gra...@percival-music.ca wrote: LilyPond 2.15.30 is out; this is not a actual release candidate Graham surely meant 2.15.33. I'm crossing fingers for the release! Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dropping support for osx 10.4 x86
On Fri, Mar 9, 2012 at 9:02 PM, Carl Sorensen c_soren...@byu.edu wrote: On 3/9/12 12:57 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 09, 2012 at 07:51:20PM +, Graham Percival wrote: If somebody can make 10.4-x86 work, then it would be great to officially support it again in the future. However, I think that's too far away; delaying 2.16.0 for that doesn't make sense. oops, I should delay all emails by 5 minutes or something. In case anybody thinks I'm being unfair to osx users: one of the strongest reasons to move forward with 2.16 right now is so that we can get a stable lilypond in the hands of 10.7 users. Or, to put it in my terms, to make those annoying 'why doesn't lilypond run on 10.7?' people shut up. This decision is a balance between 10.7 users vs. 10.4-x86 users; the sanity of main developers vs. other stuff, etc. I think that moving forward with 2.16 is the right thing to do. I totally agree. There is no reason to add a separate download for lilypad on 10.4-x86. Users of 10.4-x86 can upgrade software, or they can use any other text editor to do lilypond work. The only thing not working is the GUI app, which isn't really necessary. +1 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: dropping support for osx 10.4 x86
On Fri, Mar 09, 2012 at 10:07:55PM +0100, Janek Warcho wrote: On Fri, Mar 9, 2012 at 9:02 PM, Carl Sorensen c_soren...@byu.edu wrote: On 3/9/12 12:57 PM, Graham Percival gra...@percival-music.ca wrote: On Fri, Mar 09, 2012 at 07:51:20PM +, Graham Percival wrote: If somebody can make 10.4-x86 work, then it would be great to officially support it again in the future. However, I think that's too far away; delaying 2.16.0 for that doesn't make sense. oops, I should delay all emails by 5 minutes or something. In case anybody thinks I'm being unfair to osx users: one of the strongest reasons to move forward with 2.16 right now is so that we can get a stable lilypond in the hands of 10.7 users. Or, to put it in my terms, to make those annoying 'why doesn't lilypond run on 10.7?' people shut up. This decision is a balance between 10.7 users vs. 10.4-x86 users; the sanity of main developers vs. other stuff, etc. I think that moving forward with 2.16 is the right thing to do. I totally agree. There is no reason to add a separate download for lilypad on 10.4-x86. Users of 10.4-x86 can upgrade software, or they can use any other text editor to do lilypond work. The only thing not working is the GUI app, which isn't really necessary. +1 Agreed. -- Colin Hall ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fixes to auxiliar/doc-section.sh
I've just pushed some fixes to auxiliar/doc-section.sh to staging, as several things seemed to have gone wrong with it since I last used it. The script is intended to be used for quickly checking changes made to the English docs. It compiles a section of the docs to html in a minute or so and displays that section in a browser. Far better than waiting an hour or so (that's how long it seems to take on my laptop) for make doc to finish, if all you want to do is check that the texinfo and the cross-refs are valid. It now works fine on my laptop under Ubuntu. I'd be grateful if one or two of the doc editors could check it out too, once it moves into master. Thanks. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
