Re: Issue 2366: THANKS needs updating or deleting (issue 6478050)
Reviewers: colinpkcampbell_gmail.com, http://codereview.appspot.com/6478050/diff/1/THANKS File THANKS (right): http://codereview.appspot.com/6478050/diff/1/THANKS#newcode15 THANKS:15: Benkő Pál On 2012/08/24 04:11:53, Colin Campbell wrote: I believe that Pál is his given name and Benkő his surname. This is basically the outcome of git shortlog, see issue 2528 for the discussion then. If it keeps upsetting people, Pál would not apparently mind if we change this around, but I'll keep this for now, even though the alphabetic sorting is, indeed, off. But that is not better for Łukasz. Description: Issue 2366: THANKS needs updating or deleting This is a superficial update of THANKS. It is a temporary measure for the sake of a stable release with minimally invasive changes. Please review this at http://codereview.appspot.com/6478050/ Affected files: M THANKS Index: THANKS diff --git a/THANKS b/THANKS index 64e2a1f97c395281e8abcb658322a8f9c7133321..783d75f8a59df607a5cc4a329dc64235f2a54a36 100644 --- a/THANKS +++ b/THANKS @@ -1,3 +1,73 @@ +Release 2.16 + + +For information about the various official or semi-official positions, +check out URL:http://lilypond.org/authors.html + +The following are registered as having authored changes to the +repository of LilyPond since 2.14.2: + +Adam Spiers +Alberto Simoes +Aleksandr Andreev +Anthony Fok +Arnold Theresius +Benkő Pál +Bertrand Bordage +Carl D. Sorensen +Choan Gálvez +Colin Campbell +Daisuke Yamashita +David Kastrup +David Nalesnik +Dénes Harmath +Federico Bruni +Francisco Vila +Frédéric Bron +Graham Breed +Graham Percival +Han-Wen Nienhuys +Heikki Tauriainen +Ian Hulin +James Lowe +Jan Nieuwenhuizen +Jan-Peter Voigt +Janek Warchoł +Jean-Charles Malahieude +Joe Neeman +John Mandereau +Joseph Wakeling +Julien Rioux +Karin Hoethker +Keith OHara +Marc Hohl +Markus Oehme +Matthias Kilian +Michael Welsh Duggan +Mike Solomon +Neil Puttock +Nicolas Sceaux +Patrick McCarty +Patrick Schmidt +Pavel Roskin +Peter Chubb +Phil Holmes +Piers Titus van der Torren +Reinhold Kainhofer +Rodolfo Zitellini +Seafire +Stefan Weil +Sven Axelsson +Thomas Morley +Till Rettig +Trevor Daniels +Valentin Villenave +Werner Lemberg +Wol +Yoshiki Sawada +Łukasz Czerwiński + + Release 2.13 ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 2706 in lilypond: add link to enc2ly
- Original Message - From: Frédéric Bron frederic.b...@m4x.org To: lilypond-devel@gnu.org Sent: Friday, August 24, 2012 5:04 AM Subject: Re: Issue 2706 in lilypond: add link to enc2ly issue 2706: test passed, who can apply the patch? Or can I do something myself as I was added to the list of commiters (on rietveld, is it the same for git?). Frédéric Git push permission is not the same as the ability to add issues to Rietveld and Google. The normal criterion for pushing a patch is that it has passed a patch countdown. I see the patch-meister has now set your patch back to patch-new. Not quite sure why, but that implies a retest and review before it's ready to push. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 2706 in lilypond: add link to enc2ly
On 12-08-24 02:05 AM, Phil Holmes wrote: - Original Message - From: Frédéric Bron frederic.b...@m4x.org To: lilypond-devel@gnu.org Sent: Friday, August 24, 2012 5:04 AM Subject: Re: Issue 2706 in lilypond: add link to enc2ly issue 2706: test passed, who can apply the patch? Or can I do something myself as I was added to the list of commiters (on rietveld, is it the same for git?). Frédéric Git push permission is not the same as the ability to add issues to Rietveld and Google. The normal criterion for pushing a patch is that it has passed a patch countdown. I see the patch-meister has now set your patch back to patch-new. Not quite sure why, but that implies a retest and review before it's ready to push. -- My misunderstanding: from Frédéric's comment, I thought he was posting a changed patch, which should have a Patchy test. It was late last night after wrestling a recalcitrant trial balance at the office, so perhaps the synapses weren't firing in sequence. At any rate, I see Graham has pushed it for Frédéric. Cheers, Colin -- I've learned that you shouldn't go through life with a catcher's mitt on both hands. You need to be able to throw something back. -Maya Angelou, poet (1928- ) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fix 2732: Extract the full page geometry in lilypond-book (issue 6454139)
Reviewers: dak,
http://codereview.appspot.com/6454139/diff/1/python/book_latex.py
File python/book_latex.py (right):
http://codereview.appspot.com/6454139/diff/1/python/book_latex.py#newcode262
python/book_latex.py:262: textwidth = (textwidth + columnsep) / columns
- columnsep
On 2012/08/12 13:24:37, dak wrote:
Why not use the value of \columnwidth in the first place here?
Good idea, I wasn't aware that this length existed. You are right, this
is much better.
Note that this
does not help with full-width figures:
\begin{figure*}
...
\end{figure*}
For those you'll have to specify an explicit line-width parameter to the
snippet anyway.
http://codereview.appspot.com/6454139/diff/1/python/book_snippets.py
File python/book_snippets.py (right):
http://codereview.appspot.com/6454139/diff/1/python/book_snippets.py#newcode128
python/book_snippets.py:128: MARGIN_LEFT: r'''left-margin =
%(left-margin)s''',
On 2012/08/12 13:24:37, dak wrote:
I have a hard time imagining the margins to make any sense since TeX
applies
them to the included material anyway.
Neither do I. I just figured it might not be wrong if the lilypond
snippet uses the exact same position on the paper as the latex document
(i.e. don't center the line-width on the paper, but use the latex
left-/right margins). But then, I can't think of a situation where
lilypond would give a different cropped result for different margins,
but same line-width...
The top-/bottom-margins might have an influence for vertical
stretching/compressing of multi-staff systems in a snippet. If the latex
margins are quite large, without top-/bottom margins lilypond would
create a snippet image that is too high for the latex textheight.
However, I don't think that these margin settings should be documented.
They are not meant to be used as snippet options manually, only for the
auto-extracted page geometry.
Description:
Fix 2732: Extract the full page geometry in lilypond-book
So far, lilypond-book tried to extract the line-width from the latex
settings,
but not the full page geometry (height, width, margins). Instead, it
simply used
the extracted line-with with the default paper size.
If the latex paper size is larger than the lilypond default paper size,
then the
line-width will be larger than the page. Lilypond detects this and
ignores the
wrong line-width.
The proper solution is to extract the full page geometry from the latex
document
and use that for the lilypond snippet, too (unless an explicit papersize
or
line-width was given, of course...)
As a side-effect, we now have some more snippet options:
-) paper-width
-) left-margin
-) paper-height
-) top-margin
-) bottom-margin
The latter options only have an effect on vertical stretching of
multi-staff groups.
This patch also fixes a small mis-calculation of the text-width for
multi-column
texts (the columnsep was subtracted only once rather than once per
separation...)
Please review this at http://codereview.appspot.com/6454139/
Affected files:
A input/regression/lilypond-book/tex-papersize-detection.lytex
M python/book_base.py
M python/book_latex.py
M python/book_snippets.py
M python/book_texinfo.py
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Problem with snippet 654 after 2.15.28
Up until 2.15.27 http://lsr.dsi.unimi.it/LSR/Item?id=654 runs OK. Afterwards it seems to loop infinitely. I've tried convert-ly and it left the snippet unchanged. Could someone who understands what it's doing check whether a lily syntax change is needed, or is it revealing a bug? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with snippet 654 after 2.15.28
Phil Holmes em...@philholmes.net writes: Up until 2.15.27 http://lsr.dsi.unimi.it/LSR/Item?id=654 runs OK. Afterwards it seems to loop infinitely. I've tried convert-ly and it left the snippet unchanged. Could someone who understands what it's doing check whether a lily syntax change is needed, or is it revealing a bug? It is quite certainly issue 2240 Don't wrap EventChord around rhythmic events by default, with Fixed_2_15_28 label. The snippet relies on a rigid organisation of Music expressions that is no longer the same. The snippet does a wagonload of programming and convenience shortcuts that are not as much part of the snippet than of the writer's comfort space. My own impulse would be on rewriting it in a way depending less on the exact Music structure organisation. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
New Esperanto PO file for 'lilypond' (version 2.15.95)
Hello, gentle maintainer. This is a message from the Translation Project robot. A revised PO file for textual domain 'lilypond' has been submitted by the Esperanto team of translators. The file is available at: http://translationproject.org/latest/lilypond/eo.po (We can arrange things so that in the future such files are automatically e-mailed to you when they arrive. Ask at the address below if you want this.) All other PO files for your package are available in: http://translationproject.org/latest/lilypond/ Please consider including all of these in your next release, whether official or a pretest. Whenever you have a new distribution with a new version number ready, containing a newer POT file, please send the URL of that distribution tarball to the address below. The tarball may be just a pretest or a snapshot, it does not even have to compile. It is just used by the translators when they need some extra translation context. The following HTML page has been updated: http://translationproject.org/domain/lilypond.html If any question arises, please contact the translation coordinator. Thank you for all your work, The Translation Project robot, in the name of your translation coordinator. coordina...@translationproject.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Git tree testing in make dist: do not require bash (issue 6484047)
LGTM http://codereview.appspot.com/6484047/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 2706 in lilypond: add link to enc2ly
My misunderstanding: from Frédéric's comment, I thought he was posting a changed patch, which should have a Patchy test. It was late last night after wrestling a recalcitrant trial balance at the office, so perhaps the synapses weren't firing in sequence. At any rate, I see Graham has pushed it for Frédéric. Sorry for my unprecise comment. Thank you Graham for pushing, Cheers, Frédéric ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
more announcements for 2.16
If people want to have the 2.16.0 release announcement spread in more places, they might want to look at: http://code.google.com/p/lilypond/issues/detail?id=1719 and make a list here. Please don't send announcements to other locations quite yet; I'd like to have 3 days for last-minute fixes. Notably, we have unfortunately omitted at least one very hard-working developer from the authors list. This is being fixed on our website and in git, but I'd like to avoid such mistakes in future emails. If you're not listed in http://lilypond.org/website/authors.html please get in touch before Monday, 27 Aug 2012. That's when we'll send announcements to other locations (if anybody suggests anything). - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
new scheme indentation script in staging
We have an indentation script for scheme in staging now. We're not actually running the script on the source tree until 1 or 2 big patches are merged: Mike's skyline stuff, and possibly the guile2.0 stuff. This will hopefully get the fixes done in the near future without introducing lots of merge problems. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Problem with snippet 654 after 2.15.28
Le Fri, 24 Aug 2012 16:05:18 +0200, Phil Holmes em...@philholmes.net a écrit: Up until 2.15.27 http://lsr.dsi.unimi.it/LSR/Item?id=654 runs OK. Afterwards it seems to loop infinitely. I've tried convert-ly and it left the snippet unchanged. Could someone who understands what it's doing check whether a lily syntax change is needed, or is it revealing a bug? In this snippet, the last sentence is : More detailed documentation (in pdf format), and also the most recent changePitch.ly can be found here. where the word here is a link : http://gillesth.free.fr/Lilypond/changePitch/ Have you the last version ? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
On Thu, Aug 23, 2012 at 8:12 AM, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: I wish you a lot of fun and inspiration at the Waltrop LilyPond meeting! Likewise. Greetings from Paris (only 41.5°C today, yay!); sorry not to be with you guys, but I wish you a lot of fun and have no doubt that things will be both entertaining and interesting. Please just remember to take a few pictures and notes for the upcoming LilyPond Report! (And remember to disable BW mode on your cameras, unlike me last month with Joe ;-) Cheers, Valentin. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Waltrop meeting outline
On Fri, Aug 24, 2012 at 2:31 PM, Valentin Villenave valen...@villenave.netwrote: On Thu, Aug 23, 2012 at 8:12 AM, Martin Tarenskeen m.tarensk...@zonnet.nl wrote: I wish you a lot of fun and inspiration at the Waltrop LilyPond meeting! Likewise. Greetings from Paris (only 41.5°C today, yay!); sorry not to be with you guys, but I wish you a lot of fun and have no doubt that things will be both entertaining and interesting. Please just remember to take a few pictures and notes for the upcoming LilyPond Report! (And remember to disable BW mode on your cameras, unlike me last month with Joe ;-) Don't forget that we also took a photo (color, presumably) with Ngoc's camera. Unfortunately, it seems that I have some trouble in arranging to have a computer, camera, and USB cable all in the same place... Cheers, Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Lilypond 2.16.0 released!
Many congratulations to everyone that worked so hard on this release! Please drink a beer for me this weekend in Waltrop. On Fri, Aug 24, 2012 at 12:01 PM, Graham Percival gra...@percival-music.ca wrote: We are proud to announce the release of GNU LilyPond 2.16.0. LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. Many improvements have been made in the past year since the previous main stable version. A few major improvements are: * Support for kievan square notation * User and programming interfaces have greatly improved * Music functions have become quite more versatile A full list of new features is given in: http://lilypond.org/doc/v2.16/Documentation/changes/index.html Happy music typesetting! LilyPond 2.16 was brought to you by. Main development team: Bertrand Bordage, Trevor Daniels, Phil Holmes, Ian Hulin, Reinhold Kainhofer, David Kastrup, Jonathan Kulp, Werner Lemberg, John Mandereau, Patrick McCarty, Joe Neeman, Han-Wen Nienhuys, Jan Nieuwenhuizen, Graham Percival, Mark Polesky, Neil Puttock, Mike Solomon, Carl Sorensen, Francisco Vila, Valentin Villenave, Jan Warchoł Programming contributors: Aleksandr Andreev, Sven Axelsson, Peter Chubb, Karin Hoethker, Mark Hohl, Justin Ohmie, Benkő Pál, Julien Rioux, Patrick Schmidt, Adam Spiers, Heikki Taurainen, Piers Titus van der Torren, Jan-Peter Voigt, Janek Warchol Documentation contributors: James Lowe, Pavel Roskin, Alberto Simoes, Stefan Weil Bug squad: Colin Campbell, Eluze, Phil Holmes, Marek Klein, Ralph Palmer, James Lowe Support: Colin Campbell, Christian Hitz, Phil Holmes Translation contributors: Jean-Charles Malahieude, Till Paala, Yoshiki Sawada - Graham Percival David Kastrup ___ Info-lilypond mailing list info-lilyp...@gnu.org https://lists.gnu.org/mailman/listinfo/info-lilypond -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
