Re: Need help with building docs on openSUSE build service
On 01/07/2010 04:24 PM, Jan Nieuwenhuizen wrote: > Op donderdag 07-01-2010 om 16:03 uur [tijdzone +0200], schreef Dave > Plater: > > >> Just had a successful build on line, it fails because of permissions on >> the info dir though, it was either "export GS_LIB="/home/$USER/.fonts" >> or "# norootforbuild" that did it. >> > Then you just may have found a workaround... > > >> As far as your gs bug goes, I get a ghostscript error when I try to view >> the file that causes the failure in mc. >> > ...not sure if it's really helpful though, because with gs 8.70 it > works fine. I think I mentioned that before? ;-) > > I'm attaching the resulting pdf. > > Greetings, > Jan. > > > Well my 11.2 x86_64 home:plater:branches:openSUSE:Factory:Contrib lilypond build has just succeeded, I had to patch out the running of "install-info" in GNUmakefile.in and I'm now close to a finished package. The addition of "export GS_LIB="/home/$USER/.fonts" did the trick for the failure of the doc build, it's lucky that I had it present in my $HOME directory. It must have come from a previous version of suse that I had installed, I haven't cleaned out my home directory since at least 11.0 or maybe even 10.3 and I've updated through factory since 10.3. You are correct that gs shouldn't segfault on a corrupt file or in this case possibly because of the lack of a directory that contains a file called fonts.dir and contains only 0 and a line feed. This would be an upstream bug but upstream will say it's fixed in 8.70. I would appreciate it if you could check my package as I'm not experienced with lilypond before I go any further. The doc build fails on 11.1 ATM but 11.2 and Factory standard succeed, I'll sort out 11.1 at a later stage, I've been neglecting all other work over lilypond. Regards Dave P ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 659: alternate segno symbol (issue181144)
> -) Compiling the font gives some warnings: > > Invoking "fontforge -script feta26.pe feta26.pfb"... > Copyright (c) 2000-2009 by George Williams. > Executable based on sources from 22:35 GMT 22-Jun-2009. > Library based on sources from 22:35 GMT 22-Jun-2009. > Internal Error in scripts.varcoda: couldn't find a needed exit from an > intersection > Internal Error: > > Could not find finalm > > Internal Error in scripts.varcoda: couldn't find a needed exit from an > intersection [Not tested yet the actual changes.] Is your fontforge version compiled with --enable-double? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 659: alternate segno symbol (issue181144)
Werner LEMBERG schrieb: -) Compiling the font gives some warnings: Invoking "fontforge -script feta26.pe feta26.pfb"... Copyright (c) 2000-2009 by George Williams. Executable based on sources from 22:35 GMT 22-Jun-2009. Library based on sources from 22:35 GMT 22-Jun-2009. Internal Error in scripts.varcoda: couldn't find a needed exit from an intersection Internal Error: Could not find finalm Internal Error in scripts.varcoda: couldn't find a needed exit from an intersection [Not tested yet the actual changes.] Is your fontforge version compiled with --enable-double? I use fontforge out of the box from my ubuntu distro. I don't know how it is built. Marc Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Patch: issue #659
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/6 Marc Hohl :
I've just posted a patch for the alternate segno sign.
To use the new symbol stored at scripts.varsegno, I have
adapted the arguments for the \bar command.
Very nice. It's a bit different from the examples posted on the
tracker, but looks very elegant. :)
Thanks!
Yes, the picture in the tracker has one loop missing, but in
all other sources, the sign looked (mainly) as mine.
Two general thoughts:
1) I think the internal double bar is a bit too heavy for the glyph,
though I can understand why you'd use the default to tie in with the
span-bar.
But how can this be solved? Should there be some kind of "segno double
bar"
with a smaller width?
2) Should the sign scale for different line-counts? Of course, this
would be much more complicated to implement, since you'd have to split
the glyph into several parts. :)
Phooey, I don't know if I am able to cope with this...
Generally, I like this sign, because it sticks in the staff lines and
therefore doesn't occupy space above the staff (in comparison
to the normal segno mark), but it seems not to be
used very often.
I also had the idea to enhance the \repeat command, so one can code
\repeat segno { ... } and lilypond inserts .S and S. instead of ||:
and :||
but I don't have a clue (yet) how to cope with the coda, because coda
signs are not barlines, so I'll have to deal with \marks and stuff.
But in general, a proper usage for sengo parts is still missing in
lilypond's features in my opinion.
There is one problem I didn't manage to solve:
I had to shrink the width of the character to 0 to place it
between the double bar lines; this works but has the drawback
that notes are too close to the segno bar. How can I solve this?
I think if you just add the segno glyph to the double-bar, i.e.,
m.add_at_edge (X_AXIS, LEFT, thin, thinkern);
m.add_at_edge (X_AXIS, RIGHT, thin, thinkern);
m.add_stencil (segno);
you can probably add a correction to the SpanBar to ensure it lines up
with the centre of the segno (either in ly:span-bar::print or as an
'X-offset callback).
Ah, ok. Is there a possibility to get the width of the segno sign
to compute the shift in ly:span-bar::print? I am still
struggling with c++...
Ah, no, I think I got it. I see that in bar-line.cc there is a comment about
the double bars ans symmetry. If I change this definition, it works.
Marc
Thanks,
Marc
Regards,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 659: alternate segno symbol (issue181144)
n.putt...@gmail.com schrieb:
http://codereview.appspot.com/181144/diff/1002/1003
File input/regression/bar-line-segno.ly (right):
http://codereview.appspot.com/181144/diff/1002/1003#newcode9
input/regression/bar-line-segno.ly:9: \relative \new StaffGroup <<
\relative c'
Ok, done. I copied this just from input/regression/bar-lines-tick.ly
where this error also appears.
http://codereview.appspot.com/181144/diff/1002/1004
File lily/bar-line.cc (right):
http://codereview.appspot.com/181144/diff/1002/1004#newcode382
lily/bar-line.cc:382: " @code{|.|}, @code{:}, @code{dashed}, code{S} and
@code{'}.\n"
@code{S}
Done.
http://codereview.appspot.com/181144
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
On Thu, Jan 07, 2010 at 05:46:51PM -0700, Carl Sorensen wrote: > On 1/7/10 5:10 PM, "Graham Percival" wrote: > > > That's because you're looking at the fuzzy doc-webpage in the 2.13 > > docs, instead of the real "staging" webpage in ~graham/. > > No, I'm looking on the docs that are built on my local system. Yes, the fuzzy (huh, I originally meant to write "futzy", of whose meaning I'm not entirely certain, but it sounds like it'd have the meaning I'm looking for) doc-webpage in the 2.13 docs. I still have 5 hours of work on the webpage/doc to do, and it wouldn't be efficient to discuss it before then. At my current rate of progress on my own tasks (instead of responding to other stuff), I estimate it'll be one week before it's done. > Then let me suggest some changes to the Development page. My objective is > to be able to click to all the manuals from one page without having to > scroll. Without knowing your preferred window size and font size, it's impossible to treat this as a design goal. :) It's definitely not possible to do this on my eee 701; it might be possible on my aspire one with a full-screen window; it might be possible on my desktop with a non-full-screen window but it really depends on how big the window is. I'll bear the rest of the suggestions in mind while I work on it. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
On Thu, Jan 07, 2010 at 06:48:24PM -0800, Patrick McCarty wrote: > I *really* wish the website had a "sitemap" with links to every manual > from the stable and development documentation. > > Maybe a two-column webpage with the 2.12 links in the left column and > the 2.13 links in the right column? No. People should be using the stable docs. Developers (i.e. non-people) should use the devel page. That was a basic architectural decision a year ago, and it's not going to change without substantial evidence that we got it wrong. The other suggestions looked good, though. I'll let you know when it's ready to be looked at. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Texinfo @ifset question
On Thu, Jan 07, 2010 at 06:34:50PM -0800, Mark Polesky wrote: > Graham Percival wrote: > > You could change the web branch to point to the 2.13 CG. > > That's a good idea; but can we make it future-proof? In the new website, that was done a few weeks ago: scripts/build/create-version-itexi.py In the old website, I don't care WTF or HTF it's done. A hard link would be fine. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
On Fri, Jan 08, 2010 at 01:29:43AM +0100, Francisco Vila wrote: > Hello, I can not say since when, but currently all 2.12 docs show > titles and links in English: > > http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/ > http://lilypond.org/doc/v2.12/Documentation/user/lilypond/ > etc. > > so in En (obviously), but also in Fr, De and Es. Sorry, we're not going to have another 2.12 release unless there's an overwhelming need for it. If it's not working in the 2.13 docs, please let John know; otherwise, just stay tuned for the 2.14 release in a month or two. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH:] Enhancement: Providing ly:grob-set-nested-property!
I posted this patch some time ago, and according to Neil's proposals, I uploaded it to rietveld. This patch features a new function similar to the already existing ly:grob-set-property! http://codereview.appspot.com/183159 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
Le vendredi 08 janvier 2010 à 01:29 +0100, Francisco Vila a écrit : > Hello, I can not say since when, but currently all 2.12 docs show > titles and links in English: > > http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/ > http://lilypond.org/doc/v2.12/Documentation/user/lilypond/ > etc. > > so in En (obviously), but also in Fr, De and Es. This is likely one of the disadvantage of the build system not checking accurately documentation dependencies; I wouldn't be surprised if a version of texi2html incompatible with the init file in 2.12 branch caused this. As Graham said, there will probably no other 2.12 release to fix this. To prevent this kind of issue in the future, I welcome assistance in translation coordination in order to free me time for developing better translation and documentation tools; otherwise I'll have to choose between coordinating translations with half-backed tools (this is the current situation) or stop managing contacts with translators until I've set up or developed decent tools. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
Am Freitag, 8. Januar 2010 03:18:41 schrieb Carl Sorensen: > It's basically the same set of links as in the 2.12 documentation. But it > doesn't have all of the choices for each manual (one big page, pdf). > Therefore, when you click on any manual, you get to a page that gives you > all the choices, and then you click on the split HTML. Yes, and that is highly annoying to me. This requires 1 more click and at least 5 seconds more to go to the manual you want to see. > The All link from the manuals page gets you to a page (Documentation quick > links) that you can use to get to any of the split HTML pages. If that > page had the Contributor's Guide on it it would be perfect for my use, and > I'd bookmark that as my Local Documentation link. Yes! Can't we make that the default documentation page? I don't think that newcomers will want the choice between all the "exotic" documentation formats. It's better to show them something quickly. And the first line of that page already tells the user that there are other formats, too, and where to find them. 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
2010/1/8 Graham Percival : > On Fri, Jan 08, 2010 at 01:29:43AM +0100, Francisco Vila wrote: >> Hello, I can not say since when, but currently all 2.12 docs show >> titles and links in English: >> >> http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/ >> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/ >> etc. >> >> so in En (obviously), but also in Fr, De and Es. > > Sorry, we're not going to have another 2.12 release unless there's > an overwhelming need for it. If it's not working in the 2.13 > docs, please let John know; otherwise, just stay tuned for the > 2.14 release in a month or two. OK, but regarding to the translations, this is the biggest regression ever. Those (old) docs were once well translated and they are now unusable; otoh newest docs are not translated yet. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
Am Freitag, 8. Januar 2010 10:02:12 schrieb Graham Percival: > On Fri, Jan 08, 2010 at 01:29:43AM +0100, Francisco Vila wrote: > > Hello, I can not say since when, but currently all 2.12 docs show > > titles and links in English: > > > > http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/ > > http://lilypond.org/doc/v2.12/Documentation/user/lilypond/ > > etc. > > > > so in En (obviously), but also in Fr, De and Es. > > Sorry, we're not going to have another 2.12 release unless there's > an overwhelming need for it. If it's not working in the 2.13 > docs, please let John know; otherwise, just stay tuned for the > 2.14 release in a month or two. Pardon? What would you do if lilypond 2.12 would not print e.g. the initial clef? Of course you would do another release to fix this! Now, our translated docs (remember, not everybody knows English as well as we do!) have all their headings and thus also their complete TOC in English rather than in their localized version, making them unusable to anyone who doesn't speak English! So, I see the overwhelming need to fix this issue. 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
Am Freitag, 8. Januar 2010 09:58:31 schrieb Graham Percival: > On Thu, Jan 07, 2010 at 06:48:24PM -0800, Patrick McCarty wrote: > > I *really* wish the website had a "sitemap" with links to every manual > > from the stable and development documentation. > > > > Maybe a two-column webpage with the 2.12 links in the left column and > > the 2.13 links in the right column? > > No. People should be using the stable docs. Developers (i.e. > non-people) should use the devel page. That was a basic > architectural decision a year ago, and it's not going to change > without substantial evidence that we got it wrong. To help people answering questions on the mailing lists, it might still be useful. So I hand-wrote such a page with a table of links to both 2.12 and 2.13 docs: http://kainhofer.com/~lilypond/lily-docs.html No css magic or anything is done there, just the bare-bones table of links. 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 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
On Fri, Jan 08, 2010 at 12:55:06PM +0100, Reinhold Kainhofer wrote: > Am Freitag, 8. Januar 2010 10:02:12 schrieb Graham Percival: > > Sorry, we're not going to have another 2.12 release unless there's > > an overwhelming need for it. > > Pardon? What would you do if lilypond 2.12 would not print e.g. the initial > clef? That fits the definition of "overwhelming need". > So, I see the overwhelming need to fix this issue. Ok, let's get a few more opinions. Should we release a 2.12.4 which is identical to 2.12.3 other than changing lilypond-texi2html.pl? If so, who is volunteering to do the work on lilypond-texi2html.pl ? If the answers are "yes" and "I've just pushed a change to stable/2.12 and it will work", then I'll make another release. I don't think it's worth it, since 2.14 is coming soon, but if there's lots of interest in doing this, I'll put in the time as release manager. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
more translation breakage
grr. If you add new files in master, check that you add them properly. file from VC not distributed: lilypond-2.13.11/Documentation/es/search-box.ihtml file from VC not distributed: lilypond-2.13.11/Documentation/hu/search-box.ihtml - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: more translation breakage
Le vendredi 08 janvier 2010 à 12:15 +, Graham Percival a écrit : > grr. If you add new files in master, check that you add them properly. > > file from VC not distributed: > lilypond-2.13.11/Documentation/es/search-box.ihtml > file from VC not distributed: > lilypond-2.13.11/Documentation/hu/search-box.ihtml Fixed. I have no easy mean to check this, sorry. Cheers, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
2010/1/8 Graham Percival : > On Fri, Jan 08, 2010 at 12:55:06PM +0100, Reinhold Kainhofer wrote: >> Am Freitag, 8. Januar 2010 10:02:12 schrieb Graham Percival: >> > Sorry, we're not going to have another 2.12 release unless there's >> > an overwhelming need for it. >> >> Pardon? What would you do if lilypond 2.12 would not print e.g. the initial >> clef? > > That fits the definition of "overwhelming need". > >> So, I see the overwhelming need to fix this issue. > > Ok, let's get a few more opinions. Should we release a 2.12.4 > which is identical to 2.12.3 other than changing > lilypond-texi2html.pl? If so, who is volunteering to do the work > on lilypond-texi2html.pl ? I volunteer but I don't have the lightest idea of what to do :-) For less than that we released new 2.11 versions with a fourth minor number. 2.11.14-1 and 2.11.14-2 both on 26-Jan-2007, 2.11.15-1 on 01-Feb-2007 and 2.11.15-2 a day later, on 02-Feb 2.11.17-1 and 2.11.17-2, both on 09-Feb 2.11.35-1 on 21-Nov-2007 and 2.11.35-2 two days later etc -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
Le vendredi 08 janvier 2010 à 13:56 +0100, Francisco Vila a écrit : > I volunteer but I don't have the lightest idea of what to do :-) Blindly replacing texi2html init file (and probably the default CSS file too) by the one from master branch. At least, that's what I'll try first as soon as I find time. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
On Fri, Jan 08, 2010 at 01:56:45PM +0100, Francisco Vila wrote: > For less than that we released new 2.11 versions with a fourth minor number. 2.11 was unstable, which has different rules than stable. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
On 1/8/10 1:54 AM, "Graham Percival" wrote: > On Thu, Jan 07, 2010 at 05:46:51PM -0700, Carl Sorensen wrote: >> On 1/7/10 5:10 PM, "Graham Percival" wrote: >> >>> That's because you're looking at the fuzzy doc-webpage in the 2.13 >>> docs, instead of the real "staging" webpage in ~graham/. >> >> No, I'm looking on the docs that are built on my local system. > > Yes, the fuzzy (huh, I originally meant to write "futzy", of whose > meaning I'm not entirely certain, but it sounds like it'd have the > meaning I'm looking for) doc-webpage in the 2.13 docs. > > I still have 5 hours of work on the webpage/doc to do, and it > wouldn't be efficient to discuss it before then. At my current > rate of progress on my own tasks (instead of responding to other > stuff), I estimate it'll be one week before it's done. > > >> Then let me suggest some changes to the Development page. My objective is >> to be able to click to all the manuals from one page without having to >> scroll. > > Without knowing your preferred window size and font size, it's > impossible to treat this as a design goal. :) I understand. > It's definitely not possible to do this on my eee 701; it might be > possible on my aspire one with a full-screen window; it might be > possible on my desktop with a non-full-screen window but it really > depends on how big the window is. > However, the 2.12 version of the website meets this goal for me on every system I have (I don't have an eee). Or it would, if a link to the Contributor's guide were added. So a design goal of working within the same screen real estate as the Documentation Home for 2.12 would be both feasible (for the design) and functional (for me). > I'll bear the rest of the suggestions in mind while I work on it. Thanks very much. I appreciate all of your work on LilyPond. Thanks, Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Contributor's Guide on Website
On Fri, Jan 8, 2010 at 2:06 PM, Carl Sorensen wrote: > > On 1/8/10 1:54 AM, "Graham Percival" wrote: >> It's definitely not possible to do this on my eee 701; it might be >> possible on my aspire one with a full-screen window; it might be >> possible on my desktop with a non-full-screen window but it really >> depends on how big the window is. > > However, the 2.12 version of the website meets this goal for me on every > system I have (I don't have an eee). Or it would, if a link to the > Contributor's guide were added. So a design goal of working within > the same screen real estate as the Documentation Home for 2.12 would be both > feasible (for the design) and functional (for me). Don't forget that the 2.12 docs is split into the main doc page, and a "developer resources" link. If we split the new manuals page into two separate pages (which I'd rather avoid, but I'm not ruling out), then this task would be a lot easier. :) Also, on my system with my browser windows set to my normal amount, the 2.12 docs cut off just below "thankyous". Granted the lower stuff isn't terribly important anyway. I must admit that the new manuals page *does* cut off important stuff. Other than reducing the padding around the boxes (which could well be done) or eliminating the "manuals for VERSION", it's not obvious how else we could save space. I'll keep on thinking about it, and in any case once I've implemented a few of the other suggestions, it might be better (or worse). Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG addition about Git pulling
***snip "do we actually want a separate 'For unix developers' "
discussion about the new CG 1 introduction ***
I'm not happy with the current layout in having it as a node. If we
have it at all, I'd suggest a small bit at the top of the "for other
contributors" section. Mark, what do you think about this patch?
Cheers,
- Graham
From f45b650b077e61b32ece725cd2177c619535d95c Mon Sep 17 00:00:00 2001
From: Graham Percival
Date: Fri, 8 Jan 2010 15:11:02 +
Subject: [PATCH] Doc: CG: merge two "for XYZ contributors" together.
---
Documentation/contributor/introduction.itexi | 29 +-
1 files changed, 10 insertions(+), 19 deletions(-)
diff --git a/Documentation/contributor/introduction.itexi b/Documentation/contributor/introduction.itexi
index 7a1f586..94c9608 100644
--- a/Documentation/contributor/introduction.itexi
+++ b/Documentation/contributor/introduction.itexi
@@ -3,11 +3,11 @@
@node Introduction to contributing
@chapter Introduction to contributing
+FIXME add fluff.
@menu
* Overview of tasks::
-* For unix developers::
-* For other contributors::
+* Summary of contributing::
* Mentors::
@end menu
@@ -21,26 +21,17 @@ quite possibly as the very first thing. This requires having a
macro for it, which depends on issue 939.
-...@node For unix developers
-...@section For unix developers
+...@node Summary of contributing
+...@section Summary of contributing
+...@cartouche
-To download the LilyPond Git repository:
-
-...@example
-git clone git://git.sv.gnu.org/lilypond.git
-...@end example
-
-Documentation is built using Texinfo. Subscribe to the
-developers' mailing list at
-...@uref{http://lists.gnu.org/mailman/listinfo/lilypond-devel} and
-send well-formed Git patches to
-...@uref{mailto:lilypond-devel@@gnu.org} for discussion.
-
-
-...@node For other contributors
-...@section For other contributors
+...@strong{ultra-fast summary for Unix developers}: source code is at
+...@code{git://git.sv.gnu.org/lilypond.git}. Documentation is built
+with Texinfo, after pre-processing with @code{lilypond-book}.
+Send well-formed patches to @email{lilypond-devel@@gnu.org}.
+...@end cartouche
The LilyPond source code is maintained as a Git repository, which
contains:
--
1.6.0.4
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond mentors started
I've added the below material to CG 1 introduction. I'd really like to get going with this; is anybody else willing to mentor? In particular, I'm looking for doc and translation people. 1. Doc mentors: this will let me spend more time on the build system, new website, GUB, and the like. 2. Translation mentors: as he mentioned a few hours ago, this will let John spend more time on the build system, new website, and the like. Colin and James: I'm your mentor. You can expect me to reply to emails within a day. I think you know your current tasks. It's now your responsibility to inform me if you're uncertain about anything, or willing to do more, or whatever. (see below) -devel list: I'm trying not to sound arrogant, but I think the lilypond community would be better served if I spent more time on the website, releases, etc., instead of reminding new doc workers to put two spaces after a period and avoid referring to the reader directly. However, I feel strongly that new contributors should have a dedicated person to give them guidance (even if they never ask for help, they should know there's somebody to turn to), so if nobody wants to take over those two, I'll keep on prioritizing them over everything else I do. I know that we've gotten a bit disheartened by people offering to work on the docs but then disappearing; I don't think this will happen here. They've both sent me git patches. They might need reminding to stay within 50 characters or avoid adding whitespace errors, but other than that I consider them housebroken. The hardest part of new contributors is over, so if they were going to give up, I think this would have happened already. They _will_ need to be reminded to read the doc chapter of the CG, and they _will_ make mistakes (there's a lot of policies in there), but I don't think it'll be a lot of work. Jonathan: I rejected your offer of help before, since I thought you should have more time to recover from your tendonitis. If that's been going well, and if you're willing, I think you would be a great mentor for them. I don't need you to type a lot -- don't fix their patches for them; either push the patch, or send them an email telling them to "re-read the doc policy page, especially the 4th point" or whatever. They both seem bright, so I'm sure they can deal with a slightly-cryptic reply if that saves you a lot of typing. - CG 1.4 Mentors - We have a semi-formal system of mentorship, similar to the medieval “journeyman/master” training system. New contributors will have a dedicated mentor to help them “learn the ropes”. Note: This is subject to the availability of mentors; certain jobs have more potential mentors than others. Contributor responsibilities 1. Ask your mentor which sections of the CG you should read. 2. If you get stuck for longer than 10 minutes, ask your mentor. They might not be able to help you with all problems, but we find that new contributors often get stuck with something that could be solved/explained with 2 or 3 sentences from a mentor. 3. Send patches to your mentor for initial comments. 4. Inform your mentor if you’re going to be away for a month, or if you leave entirely. Contributing to lilypond isn’t for everybody; just let your mentor know so that we can reassign that work to somebody else. 5. Inform your mentor if you’re willing to do more work – we always have way more work than we have helpers available. Mentor responsibilities 1. Respond to questions from your contributor(s) promptly, even if the reponse is just “sorry, I don’t know” or “sorry, I’m very busy for the next 3 days; I’ll get back to you then”. Make sure they feel valued. 2. Inform your contributor(s) about the expected turnaround for your emails – do you work on lilypond every day, or every weekend, or what? Also, if you’ll be unavailable for longer than usual (say, if you normally reply within 24 hours, but you’ll be at a conference for a week), let your contributors know. Again, make sure thay feel valued, and that your silence (if they ask a question during that period) isn’t their fault. 3. Inform your contributor(s) if they need to do anything unusual for the builds, such as doing a “make clean / doc-clean” or switching git branches (not expected, but just in case...) 4. You don’t need to be able to completely approve patches. Make sure the patch meets whatever you know of the guidelines (for doc style, code indentation, whatever), and then send it on to the frog list or -devel for more comments. If you feel confident about the patch, you can push it directly (this is mainly intended for docs and translations; code patches should almost always go to -devel before being pushed). 5. Keep track of patches from your contributor. If you’ve sent a patch to -devel, it’s your responsibility to pester people to get comments for it, or at very least add it to the google tracker. -- Cheers, - Graham ___
Re: Issue 659: alternate segno symbol (issue181144)
>> [Not tested yet the actual changes.] Is your fontforge version >> compiled with --enable-double? > > I use fontforge out of the box from my ubuntu distro. I don't know > how it is built. Since you get warnings even without your changes, you haven't --enable-double. I strongly suggest to get the sources and compile fontforge by yourself -- and you should ask the Ubuntu maintainer to add this configuration flag to the default build. BTW, I'm using the CVS source from 20090812 which runs fine. Sometimes fontforge is broken so it is good in general to know a version which works :-) Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
> Thus, the slash of the character sticks out of the bounding box by > some amount. This might cause problems if images are converted to, say, cropped PNG images. You must assure somehow that the slash won't get cut off. Everything else looks fine! BTW, I don't get any warning from my fontforge executable. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG addition about Git pulling
Graham Percival wrote: > ***snip "do we actually want a separate 'For unix > developers' " discussion about the new CG 1 introduction > *** > > I'm not happy with the current layout in having it as a > node. If we have it at all, I'd suggest a small bit at > the top of the "for other contributors" section. Mark, > what do you think about this patch? I think it's better; what about you, Trevor? Some other thoughts: 1) Do we really need intro fluff before every chapter TOC? 2) I don't like the word "Summary", but we've already used "Introduction" and "Overview", both of which are better words for what that section really is. Off the top of my head, I can't think of anything else though. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
2010/1/8 Graham Percival : > On Fri, Jan 08, 2010 at 01:56:45PM +0100, Francisco Vila wrote: >> For less than that we released new 2.11 versions with a fourth minor number. > > 2.11 was unstable, which has different rules than stable. Ah, stable can tolerate this and unstable can not? -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG addition about Git pulling
On Fri, Jan 08, 2010 at 10:15:18AM -0800, Mark Polesky wrote: > Graham Percival wrote: > > I'm not happy with the current layout in having it as a > > node. If we have it at all, I'd suggest a small bit at > > the top of the "for other contributors" section. Mark, > > what do you think about this patch? > > I think it's better; what about you, Trevor? > > Some other thoughts: > > 1) Do we really need intro fluff before every chapter TOC? Why not? The doc policy says that we should, and it doesn't take a lot of thought to make up a sentence there. Certainly in most cases, the contents of the chapter are obvious from the two or three-word title, but some chapters benefit from having an explanation of their contents. And if we do it for some, I'd rather do it for all. > 2) I don't like the word "Summary", but we've already used >"Introduction" and "Overview", both of which are better >words for what that section really is. Off the top of >my head, I can't think of anything else though. I paused over this, too, but I couldn't come up with anything else. We can't re-use "introduction", but maybe "overview of tasks" should be renamed "help us" (I mean, that matches the material on the website, so I'd argue for this regardless of the naming of the Summary section). 1 Introduction 1.1 Help us 1.2 Overview of work process / Overview of contribution / Overview to development 1.3 Mentors 1.4 lily-git (maybe -- have you decided one way or the other?) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
On Fri, Jan 8, 2010 at 5:08 AM, Graham Percival wrote: > On Fri, Jan 08, 2010 at 01:56:45PM +0100, Francisco Vila wrote: >> For less than that we released new 2.11 versions with a fourth minor number. > > 2.11 was unstable, which has different rules than stable. If we figure out what's wrong, and push a fix to the stable branch, we should be able to release a 2.12.3-2, right? -Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Untranslated titles+links on latest online docs
On Fri, Jan 08, 2010 at 12:07:33PM -0800, Patrick McCarty wrote: > On Fri, Jan 8, 2010 at 5:08 AM, Graham Percival > wrote: > > On Fri, Jan 08, 2010 at 01:56:45PM +0100, Francisco Vila wrote: > >> For less than that we released new 2.11 versions with a fourth minor > >> number. > > > > 2.11 was unstable, which has different rules than stable. > > If we figure out what's wrong, and push a fix to the stable branch, we > should be able to release a 2.12.3-2, right? Maybe. I might need to spend a few hours fighting with GUB to make it do this (a. I'll need to learn how, and b. I might need to fix various problems in GUB because this hasn't been done in almost a whole year). I'm willing to prioritize this over the website work that Carl wanted. It's certainly something that I _should_ be able to do. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: CG addition about Git pulling
Mark Polesky wrote Friday, January 08, 2010 6:15 PM Graham Percival wrote: ***snip "do we actually want a separate 'For unix developers' " discussion about the new CG 1 introduction *** I'm not happy with the current layout in having it as a node. If we have it at all, I'd suggest a small bit at the top of the "for other contributors" section. Mark, what do you think about this patch? I think it's better; what about you, Trevor? Agreed - it's better. Some other thoughts: 1) Do we really need intro fluff before every chapter TOC? 2) I don't like the word "Summary", but we've already used "Introduction" and "Overview", both of which are better words for what that section really is. Off the top of my head, I can't think of anything else though. Why not qualify each of these generic words? Like Graham did with "Summary of contributing"? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add nested properties setting to \paper blocks. (issue182042)
On Sun, 2010-01-03 at 07:49 +, joenee...@gmail.com wrote: > Reviewers: hanwenn, > > > http://codereview.appspot.com/182042/diff/1004/6 > File lily/lily-lexer.cc (right): > > http://codereview.appspot.com/182042/diff/1004/6#newcode274 > lily/lily-lexer.cc:274: Lily_lexer::set_identifier (SCM path, SCM s) > On 2010/01/03 06:39:30, hanwenn wrote: > > can you update the comment that explains the calling convention. > (Possibly you > > should update the .h) > > I can update the .h but I can't find any comment explaining the calling > convention... ping! ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add basic scheme programmable engravers. (issue181109)
All done and submitted. On a unrelated note, I noticed that all of the input files under input/ have been removed in 2c89fdcaa84c848c9a81bc3b74d26359a1e93529 Author: Graham Percival 2009-10-04 10:42:12 while I applaud trimmng the directory, some of these files have actually been instrumental to developing lilypond (in particular, Bach's sarabande, Schubert's morgenlied, the Mozart horn concert) as benchmarks, and during development les-nereides.ly is a good quick check to make sure basic functionality is still alive. What was the reasoning for removing everything? On Sat, Jan 2, 2010 at 4:13 AM, wrote: > Neat! > -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Need help with building docs on openSUSE build service
On 01/07/2010 04:24 PM, Jan Nieuwenhuizen wrote: > Op donderdag 07-01-2010 om 16:03 uur [tijdzone +0200], schreef Dave > Plater: > > >> Just had a successful build on line, it fails because of permissions on >> the info dir though, it was either "export GS_LIB="/home/$USER/.fonts" >> or "# norootforbuild" that did it. >> > Then you just may have found a workaround... > > >> As far as your gs bug goes, I get a ghostscript error when I try to view >> the file that causes the failure in mc. >> > ...not sure if it's really helpful though, because with gs 8.70 it > works fine. I think I mentioned that before? ;-) > > I'm attaching the resulting pdf. > > Greetings, > Jan. > > > I had one more gs based build failure only in factory standard x86_64 which a rebuild didn't have, so it's still lurking around but it doesn't happen all the time. Regards Dave P ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Add basic scheme programmable engravers. (issue181109)
On Sat, Jan 09, 2010 at 01:51:26AM -0200, Han-Wen Nienhuys wrote: > On a unrelated note, I noticed that all of the input files under > input/ have been removed in > > 2c89fdcaa84c848c9a81bc3b74d26359a1e93529 > Author: Graham Percival 2009-10-04 > 10:42:12 > > while I applaud trimmng the directory, some of these files have > actually been instrumental to developing lilypond (in particular, > Bach's sarabande, Schubert's morgenlied, the Mozart horn concert) as > benchmarks, and during development les-nereides.ly is a good quick > check to make sure basic functionality is still alive. > > What was the reasoning for removing everything? http://lists.gnu.org/archive/html/lilypond-devel/2009-10/msg00101.html as well as 2 or 3 earlier messages to -devel (between 1 and 8 months before I did it) asking if anybody minded. I must admit that I lost Jan's request; I should have added it to the google tracker. But I'll do this as soon as I know for certain what we want to keep. typography-demo.ly is already in the regtests. Do we want to keep all the below? - bach sarabande - schubert morgenlier - mozart horn concerto - les-nereides Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
