Re: lilypond authors, release notes, announcements
Am 05.01.2011 10:32, schrieb James: Hello, On 05/01/2011 05:44, Graham Percival wrote: It looks like we're getting close to the first release candidate. - could any new contributors check: http://lilypond.org/authors.html to make sure they're there? if you have git access, you should be in development team, and choose your own title. If not, you should be listed in current contributors, in whichever categories you think is relevant. Our list of translators looks particularly slim. Send patches for: Documentation/included/authors.itexi I'll do this (to save duplicating work for anyone else). James, thanks for this offer! I am not sure about my entry - IMHO tablature is more important to me, and I think more patches from me concerned these issues (not to forget that Carl had to rework a whole lot of them). My contribution to fonts was the rotation of the G clef and the varsegno sign (which nobody seems to use, anyway ;-) But aside from this kind of nitpicking, I feel proud to be on the list and I hope that better time management will allow for spending more time on improving and extending lilypond. Regards, Marc James ___ 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: lilypond authors, release notes, announcements
Marc,
On 05/01/2011 09:50, Marc Hohl wrote:
My contribution to fonts was the rotation of the G clef and the varsegno
sign
(which nobody seems to use, anyway ;-)
Au contraire mon amis!
I use the varsegno glyph at the slightest opportunity!
It helps the 'beginners' (I find) that I play with as it seems to be
much more easy to spot for them that are not used to jumping about in a
score, than the regular segno.
I am sure that I am breaking some engraving 'rule' but it's a nice glyph.
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex' in a
body of text. I suppose some would call it a 'logotype' or colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
Have fun
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 10:09:27AM +, James wrote:
Marc,
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex'
in a body of text. I suppose some would call it a 'logotype' or
colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
I've mused about trying to create a logo using the markup
commands. If you think about all the graphical ones, plus music
glyphs, there's a lot of options. The d could be a rotated bass
clef, the ls could be compressed treble clefs, the p could be a
half note, etc. Or simply just using some artistic black and
white shapes and the like.
I'm not terribly graphically artistic, so I always gave up after 5
minutes... but I think it could be cool to have a lilypond-created
logo (which we could call with \lilypond inside a markup).
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On 2011-01-05 11:09, James wrote: Marc, On 05/01/2011 09:50, Marc Hohl wrote: My contribution to fonts was the rotation of the G clef and the varsegno sign (which nobody seems to use, anyway ;-) Au contraire mon amis! I use the varsegno glyph at the slightest opportunity! Dito. It helps the 'beginners' (I find) that I play with as it seems to be much more easy to spot for them that are not used to jumping about in a score, than the regular segno. Additionally, sometimes I think it's far more easily to integrate in the overall design than the usual symbol. Yours takes no precious vertical space, and I don't have to bother with shifting around till it's at the best place. I am sure that I am breaking some engraving 'rule' but it's a nice glyph. I've seen it in Bosworth Co. scores only, but they seem to use it exclusively instead of the common shape. But I also made up the habit of telling the ones I hand my scores out to that I use a unusual symbol for d'al segno, to avoid irritations. Cheers, Alexander ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Am 05.01.2011 11:09, schrieb James:
Marc,
On 05/01/2011 09:50, Marc Hohl wrote:
My contribution to fonts was the rotation of the G clef and the varsegno
sign
(which nobody seems to use, anyway ;-)
Au contraire mon amis!
I use the varsegno glyph at the slightest opportunity!
It helps the 'beginners' (I find) that I play with as it seems to be
much more easy to spot for them that are not used to jumping about in
a score, than the regular segno.
Great to hear!
I am sure that I am breaking some engraving 'rule' but it's a nice glyph.
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex' in
a body of text. I suppose some would call it a 'logotype' or colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
Hey, that's an interesting idea - do you have already some ideas how the
lilylogo should look like?
Regards,
Marc
Have fun
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On 2011-01-05 11:13, Graham Percival wrote:
On Wed, Jan 05, 2011 at 10:09:27AM +, James wrote:
Marc,
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex'
in a body of text. I suppose some would call it a 'logotype' or
colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
I've mused about trying to create a logo using the markup
commands. If you think about all the graphical ones, plus music
glyphs, there's a lot of options. The d could be a rotated bass
clef, the ls could be compressed treble clefs, the p could be a
half note, etc.
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
However, I'd certainly use a predefined command for the inclusion of
something like Valentin's logos from lilynet.net. [*] (Sadly, I don't
remember the correct address where I downloaded it from. I mean the SVG
sources of http://www.lilynet.net/img/lilylogo.png and
http://news.lilynet.net/local/cache-vignettes/L125xH100/lesite-d163a.png.)
One might argue that the quaver looks childish, but IMHO it does in a
very joyful and charming manner. And I really like the lilys, but I'm
not sure whether a full-colored logo is a good default choice.
[*] I actually already used these once, but in a separate title page
generated with inkscape, not via LilyPond itself.
Cheers,
Alexander
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
It looks like we're getting close to the first release candidate. - could any new contributors check: http://lilypond.org/authors.html to make sure they're there? if you have git access, you should be in development team, and choose your own title. If not, you should be listed in current contributors, in whichever categories you think is relevant. Our list of translators looks particularly slim. Send patches for: Documentation/included/authors.itexi - who wants to write release notes? Do it in the same style as previous ones. Keep it brief because various places have size limits. - based on the written policy: http://lilypond.org/doc/v2.13/Documentation/contributor/major-release-checklist - we're not using any potential requirements. - I'm not paying any attention to unsorted stuff. In particular, I'm not going to send any announcements anywhere other than lilypond.org. If you think we should be sending announcements, then start making/updating a list. Since I haven't been very active on the LilyPond lists the last year, I think it would be appropriate to remove my name from the Current development team list. After a computer upgrade, my certificates to the git repository don't work anymore and I gave up trying to fix it, so for the moment I don't have any working git access. Could I please ask Graham or some other kind soul to edit the file and move my name to an appropriate place (perhaps the trash bin :-) ). Regards /Mats ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Hello
On 05/01/2011 10:36, Alexander Kobel wrote:
On 2011-01-05 11:13, Graham Percival wrote:
On Wed, Jan 05, 2011 at 10:09:27AM +, James wrote:
Marc,
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex'
in a body of text. I suppose some would call it a 'logotype' or
colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
I've mused about trying to create a logo using the markup
commands. If you think about all the graphical ones, plus music
glyphs, there's a lot of options. The d could be a rotated bass
clef, the ls could be compressed treble clefs, the p could be a
half note, etc.
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
Everything in its place, but I think for this case I'd agree.
However, I'd certainly use a predefined command for the inclusion of
something like Valentin's logos from lilynet.net. [*] (Sadly, I don't
remember the correct address where I downloaded it from. I mean the SVG
sources ofhttp://www.lilynet.net/img/lilylogo.png and
http://news.lilynet.net/local/cache-vignettes/L125xH100/lesite-d163a.png.)
One might argue that the quaver looks childish, but IMHO it does in a
very joyful and charming manner. And I really like the lilys, but I'm
not sure whether a full-colored logo is a good default choice.
No this isn't what I was referring to. Of course the whole lilypond
'icon' with the green and white is ok for the 'logo' and I like the
little 'happy quaver' but never really thought of a place for it; but I
was thinking more of a 'lilypond' in some
cursive-cum-signature-cum-all-joined-up script, but something 'created'
as a glyph than just put together.
If you think of J S Bach's signature then that could be used as nice
glyph on a tagline.
It was just the varsegno made me think of it.
James
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On 2011-01-05 12:11, James wrote: No this isn't what I was referring to. [...] I was thinking more of a 'lilypond' in some cursive-cum-signature-cum-all-joined-up script, but something 'created' as a glyph than just put together. If you think of J S Bach's signature then that could be used as nice glyph on a tagline. Ah, okay, I get it. Sorry for the misunderstanding. Of course I meant logo + LilyPond text, not the logo alone, but still that's a different thing. Yeah, that'd be nice indeed... ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 11:11:26AM +, James wrote: Hello On 05/01/2011 10:36, Alexander Kobel wrote: I've mused about trying to create a logo using the markup commands. If you think about all the graphical ones, plus music glyphs, there's a lot of options. The d could be a rotated bass clef, the ls could be compressed treble clefs, the p could be a half note, etc. I tend not to like those assembled logos very much. Most of the time, they end up too clumsy IMHO; more like something quickly hacked together, just for the sake of quoting musical symbols. Everything in its place, but I think for this case I'd agree. It needn't use any music glyphs if the artist(s) don't like it. I mean, the \LaTeX command is basically just letters in different fonts that are positioned slightly higher or lower than the baseline. And in italics. etc. We could play those games with our own markup commands. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
2011/1/5 Graham Percival gra...@percival-music.ca
On Wed, Jan 05, 2011 at 10:09:27AM +, James wrote:
Marc,
What I think we need actually - slightly off topic - is a nice
LilyPond-glyph similar in essence to when you see the word 'Latex'
in a body of text. I suppose some would call it a 'logotype' or
colophon.
tagline = \markup { Engraved by \musicglyph #scripts.lilylogo }
I've mused about trying to create a logo using the markup
commands. If you think about all the graphical ones, plus music
glyphs, there's a lot of options. The d could be a rotated bass
clef, the ls could be compressed treble clefs, the p could be a
half note, etc.
In my opinion it would look a little too fancy.
Nevertheless the idea of creating LilyPond logo is interesting.
cheers,
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Il giorno mer, 05/01/2011 alle 11.36 +0100, Alexander Kobel ha scritto:
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
You mean something like this? (my 5 minute try, really horrible)
\version 2.13.45
\markup {
\lower #.5 { \number 1 }
\musicglyph #scripts.ustaccatissimo
\lower #.5 { \number 1 }
\musicglyph #scripts.ustaccatissimo
\lower #.5 { \dynamic p }
\musicglyph #noteheads.s0 \hspace #1
\musicglyph #scripts.prall
\semiflat
}
However, I'd certainly use a predefined command for the inclusion of
something like Valentin's logos from lilynet.net.
That's a nice idea. Maybe we could provide a blackwhite logo also...
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On 2011-01-05 12:58, Federico Bruni wrote:
Il giorno mer, 05/01/2011 alle 11.36 +0100, Alexander Kobel ha scritto:
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
You mean something like this? (my 5 minute try, really horrible)
\version 2.13.45
\markup {
\lower #.5 { \number 1 }
\musicglyph #scripts.ustaccatissimo
\lower #.5 { \number 1 }
\musicglyph #scripts.ustaccatissimo
\lower #.5 { \dynamic p }
\musicglyph #noteheads.s0 \hspace #1
\musicglyph #scripts.prall
\semiflat
}
13371p4wn3d, huh? ;-)
Yup, that's what I meant. I know a couple of amateur musicians who
copied some musical symbols to replace single characters of their names
for their letterheads. I can't think of a single one which doesn't look
ugly. Sizes don't match, kerning (if that term is allowed for this)
does not match, it looks crowded... Just like using about the whole
fonts folder for an A5 greeting card.
I'm aware that a good designer can do amazing stuff in this direction,
but this will need subtle quotations and resemblence to the symbols, not
just concatenating and rotating a few of them. If someone's up to it -
well, then show us what you can do!
However, I'd certainly use a predefined command for the inclusion of
something like Valentin's logos from lilynet.net.
That's a nice idea. Maybe we could provide a blackwhite logo also...
Still, I like James initial idea of a scripted logo. But in the
meantime, this looks like a good alternative to me.
Isn't there an engraver application which has some inkpot-and-feather
logo? Something along this line.
Cheers,
Alexander
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Potential issue 39 fix w/ patch
I've included before and after photos.Cheers,MS 0001-Potential-fix-for-issue-39.patch Description: Binary data inline: issue39after.pnginline: issue39before.png___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 5, 2011 at 11:58 AM, Federico Bruni fedel...@gmail.com wrote:
Il giorno mer, 05/01/2011 alle 11.36 +0100, Alexander Kobel ha scritto:
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
You mean something like this? (my 5 minute try, really horrible)
That looks quite busy to my taste. My latest 5-minute hack is
something like this:
\markup {
\column {
\line {
\italic \concat {
\concat {
\huge \bold \lower #.5 L
\large ily
}
\concat {
\large { \dynamic p }
\large ond
}
}}}
\line {
\fontsize #5
\rotate #270
\translate-scaled #'(-4.2 . 2)
\line
{ \musicglyph #flags.u7 }
}
}
hmm... now that I look at it again, the flag.u7 is really questionable.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Am 05.01.2011 13:33, schrieb Graham Percival:
On Wed, Jan 5, 2011 at 11:58 AM, Federico Brunifedel...@gmail.com wrote:
Il giorno mer, 05/01/2011 alle 11.36 +0100, Alexander Kobel ha scritto:
I tend not to like those assembled logos very much. Most of the time,
they end up too clumsy IMHO; more like something quickly hacked
together, just for the sake of quoting musical symbols.
You mean something like this? (my 5 minute try, really horrible)
That looks quite busy to my taste. My latest 5-minute hack is
something like this:
[...]
hmm... now that I look at it again, the flag.u7 is really questionable.
How about something more subtle?
\markup { \italic \concat { Lily \raise #1.1 \rotate #-10 { \tiny
\note-by-number #1 #0 #-0.6 } ond }}
The spacing is not 100% correct, and perhaps a better letter font could
be found, but you get
the idea.
Marc
Cheers,
- Graham
___
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: lilypond authors, release notes, announcements
Am Mittwoch, 5. Januar 2011, um 13:20:06 schrieb Alexander Kobel: Yup, that's what I meant. I know a couple of amateur musicians who copied some musical symbols to replace single characters of their names for their letterheads. I can't think of a single one which doesn't look ugly. Sizes don't match, kerning (if that term is allowed for this) does not match, it looks crowded... Just like using about the whole fonts folder for an A5 greeting card. I really like Adoro's logo, created from Lilypond font glyphs: http://www.adoromusicpub.com/ 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: lilypond authors, release notes, announcements
Am Mittwoch, 5. Januar 2011, um 13:33:26 schrieb Graham Percival: On Wed, Jan 5, 2011 at 11:58 AM, Federico Bruni fedel...@gmail.com wrote: Il giorno mer, 05/01/2011 alle 11.36 +0100, Alexander Kobel ha scritto: I tend not to like those assembled logos very much. Most of the time, they end up too clumsy IMHO; more like something quickly hacked together, just for the sake of quoting musical symbols. You mean something like this? (my 5 minute try, really horrible) That looks quite busy to my taste. My latest 5-minute hack is something like this: Attached is a small modification (created in inkscape rather than lilypond itself). What I really don't like about it is the different slant of the L, the l and the p)... 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 attachment: logo.png___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 03:17:51PM +0100, Reinhold Kainhofer wrote: Am Mittwoch, 5. Januar 2011, um 13:33:26 schrieb Graham Percival: That looks quite busy to my taste. My latest 5-minute hack is something like this: Attached is a small modification (created in inkscape rather than lilypond itself). What I really don't like about it is the different slant of the L, the l and the p)... Wow, I like it! Is there any way to get the greyed-out staff in lilypond directly? There's two things that I'm not completely sold on. The half-note d seems a bit weird, and I think the initial L could be spruced up somehow -- it feels a bit blocky. Either a more cursive font, or using some weird mensural glyph for the L ? Anyway, that's definitely the kind of thing I was hoping that people would create! Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Colin, On 05/01/2011 13:33, Colin Campbell wrote: On Wed, 2011-01-05 at 09:32 +, James wrote: You should probably move me from Documentation to Bug Squad, James. At the moment, I don't think I can manage both, but perhaps I can return to the fold later in the year! No problem. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 02:30:29PM +, James wrote: Colin, On 05/01/2011 13:33, Colin Campbell wrote: On Wed, 2011-01-05 at 09:32 +, James wrote: You should probably move me from Documentation to Bug Squad, James. At the moment, I don't think I can manage both, but perhaps I can return to the fold later in the year! I think you should be listed in both places; I certainly don't think you should removed from the Documentation list. If somebody has worked in multiples areas, they should be listed in all relevant areas. (this is reflected in a comment at the top of the authors file, but unless you look at the source you wouldn't see it) Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
lilypond.org - Denemo
Greetings List, I noticed that on http://lilypond.org/easier-editing.html Denemo is described as using an outdated version Lilypond. I would like to ask where you got that information and why do you think it is (still) valid. Denemo works with 2.12 and 2.13 just well and emits that version information to our Lilypond generator. Greetings, Nils http://www.denemo.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
On Wed, Jan 05, 2011 at 03:49:03PM +0100, Nils Gey wrote: I noticed that on http://lilypond.org/easier-editing.html Denemo is described as using an outdated version Lilypond. I would like to ask where you got that information and why do you think it is (still) valid. We have asked for help with the new website extensively in the summer of 2009 and (coincidently) summer of 2010. See http://lists.gnu.org/archive/html/lilypond-user/2010-05/msg00072.html for example. Since nobody pointed out this problem before, I'm not shedding any tears now. Denemo works with 2.12 and 2.13 just well and emits that version information to our Lilypond generator. Hopefully somebody will send a patch. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Score follower
Hello, I want to create a score follower, that is a software which shows the scores and the current position I am playing on my keyboard. I tried some rendering engines (Guidolib, Musescore, ...), but Lilypond has the best graphical output. Now I need informations about the scores like pitch, duration, voice, x-y-coordinates and page. I tried \displayMusic, but it seems there is no graphical information. I also tried -dbackend=scm, but it seems there is no pitch/voice information. Has anyone ever been faced with the same problem and can help me? Viele Grüße, Konstantin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
Hopefully somebody will send a patch. Don't you have a Lilypond webmaster to remove the box? A dedicated webmaster (maybe in personal union with other tasks) is a good thing because people like to have one person as contact if they have problems with the webpage. I strongly recommend to create such a post and/or to use a Wiki-like CMS to build your website around so that (trusted) users can edit the pages themselves if its too much work. Greetings, Nils On Wed, 5 Jan 2011 15:03:41 + Graham Percival gra...@percival-music.ca wrote: On Wed, Jan 05, 2011 at 03:49:03PM +0100, Nils Gey wrote: I noticed that on http://lilypond.org/easier-editing.html Denemo is described as using an outdated version Lilypond. I would like to ask where you got that information and why do you think it is (still) valid. We have asked for help with the new website extensively in the summer of 2009 and (coincidently) summer of 2010. See http://lists.gnu.org/archive/html/lilypond-user/2010-05/msg00072.html for example. Since nobody pointed out this problem before, I'm not shedding any tears now. Denemo works with 2.12 and 2.13 just well and emits that version information to our Lilypond generator. Hopefully somebody will send a patch. - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Score follower
Hello On 05/01/2011 12:27, Konstantin wrote: Hello, I want to create a score follower, that is a software which shows the scores and the current position I am playing on my keyboard. I tried some rendering engines (Guidolib, Musescore, ...), but Lilypond has the best graphical output. Now I need informations about the scores like pitch, duration, voice, x-y-coordinates and page. I tried \displayMusic, but it seems there is no graphical information. I also tried -dbackend=scm, but it seems there is no pitch/voice information. Has anyone ever been faced with the same problem and can help me? http://code.google.com/p/lilypond/issues/detail?id=965 I have tried this - I don't really use Linux but I managed to get this working sort (as my Linux machine is in a VM I used similar tools on a Mac), however I am not sure this is what you want? This is rather primitive, but maybe this can give you a start. James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
Nils On 05/01/2011 15:22, Nils Gey wrote: Hopefully somebody will send a patch. Don't you have a Lilypond webmaster to remove the box? The website is generated in the same way we generate all of our 'documentation' (there are some differences but essentially it is the same). That is anyone can submit a patch to change the website, however there is a Doc 'meister' who reviews this and approves any changes to the website which will get updated periodically. A dedicated webmaster (maybe in personal union with other tasks) is a good thing because people like to have one person as contact if they have problems with the webpage. I strongly recommend to create such a post and/or to use a Wiki-like CMS to build your website around so that (trusted) users can edit the pages themselves if its too much work. We do have such a person. He just sent you a response previously ;) Do you have any specific suggestions on what it should say or can we just remove the box entirely? James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Score follower
James james.lowe at datacore.com writes: [snip] http://code.google.com/p/lilypond/issues/detail?id=965 I have tried this - I don't really use Linux but I managed to get this working sort (as my Linux machine is in a VM I used similar tools on a Mac), however I am not sure this is what you want? [snap] Hello James, thank you for this link. The problem there is: the timing points are not extracted from lilypond. They are manually created (with help of a python script). Second problem: the smallest graphical object is a complete system, but I need graphical (and acoustical) informations about every single scores. Regards Konstantin ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Issue 879
- Original Message - From: Keith OHara k-ohara5...@oco.net To: lilypond-devel@gnu.org Sent: Tuesday, January 04, 2011 7:40 PM Subject: Re: Issue 879 Phil Holmes mail at philholmes.net writes: \remove Hara_kiri_engraver \consists Hara_kiri_engraver I know I don't properly understand this stuff still, but doesn't the \consists re-instate the previously removed engraver on the line above? You are correct. I looked at the history of the file containing this, using http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=tree and found that one change is titled: RemoveEmptyStaves: Remove Harakiri engraver before adding it again. This reason is explained there. It is to avoid ever having two engravers of the same type, which caused problems. This kind of detail often goes without comment in code, or at most a 3-word avoid having two, because there would otherwise be so many such comments. Thanks for pointing this out. I can't see a good reason for not adding the comment to the file: If RemoveEmptyStaves is called twice, two Hara_kiri_engravers would be added, which leads to a warning. This code makes sure that no previous Hara_kiri_engraver is left before adding a new one. ? -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Score follower
Hello On 05/01/2011 15:44, Konstantin wrote: Jamesjames.loweat datacore.com writes: [snip] http://code.google.com/p/lilypond/issues/detail?id=965 I have tried this - I don't really use Linux but I managed to get this working sort (as my Linux machine is in a VM I used similar tools on a Mac), however I am not sure this is what you want? [snap] Hello James, thank you for this link. The problem there is: the timing points are not extracted from lilypond. They are manually created (with help of a python script). Second problem: the smallest graphical object is a complete system, but I need graphical (and acoustical) informations about every single scores. Regards If you do not get a direct answer (as I cannot help you here) then I do suggest you look at some of the recent (within the last 6 - 8 months) of email threads in dev and user For example http://lists.gnu.org/archive/html/lilypond-devel/2010-10/msg00457.html Mike Solomon, one of our more 'lateral thinking' developers came up with a nice 'wave form renderer' that takes information from the scores. http://lists.gnu.org/archive/html/lilypond-devel/2010-07/msg8.html That again can give you some hints if no one else responds. Here's another thread about extracting note head co-ordinates. http://lists.gnu.org/archive/html/lilypond-devel/2009-07/msg00029.html I hope some of these are helpful, but as I say if you search some of your key words in the user and dev mail http://lists.gnu.org/archive/html/lilypond-user/ and http://lists.gnu.org/archive/html/lilypond-devel/ There's a mine of information. James James ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Score follower
On 1/5/11 8:44 AM, Konstantin kammerm...@gmx.de wrote: James james.lowe at datacore.com writes: [snip] http://code.google.com/p/lilypond/issues/detail?id=965 I have tried this - I don't really use Linux but I managed to get this working sort (as my Linux machine is in a VM I used similar tools on a Mac), however I am not sure this is what you want? [snap] Hello James, thank you for this link. The problem there is: the timing points are not extracted from lilypond. They are manually created (with help of a python script). Second problem: the smallest graphical object is a complete system, but I need graphical (and acoustical) informations about every single scores. Unfortunately, the information you wish to have is not available. If you will search the threads about musicXML output, you will see that the inability to couple musical information with graphical information is the main obstacle to musicXML output. The music information is available in the stream events. The graphical information is available in the final output. At present there is no way to connect the two. Ideas have been given before on the -devel lists. I'm sorry there's not a better answer for you. Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Score follower
Konstantin, I have a metadata patch floating around that can help you kludge your way through this. It is not too hard, but will require some work: 1) Create a sort of metadata property for whatever grob you wanna trace. 2) for those grobs, create an override for the print method that first calls the correct print method and then uses the generated stencil for xy coordinate info, returning this stencil at the end of the function after having harvested its coordinates. You can have pretty prints to the command line of the grobs' metadata and coordinates, or you can write these to a file using Scheme. If this sounds like Chinese, lemme know and I can try to cook up a simple proof of concept depending on what you want to do. Cheers, Mike On Jan 5, 2011, at 11:40, Carl Sorensen c_soren...@byu.edu wrote: On 1/5/11 8:44 AM, Konstantin kammerm...@gmx.de wrote: James james.lowe at datacore.com writes: [snip] http://code.google.com/p/lilypond/issues/detail?id=965 I have tried this - I don't really use Linux but I managed to get this working sort (as my Linux machine is in a VM I used similar tools on a Mac), however I am not sure this is what you want? [snap] Hello James, thank you for this link. The problem there is: the timing points are not extracted from lilypond. They are manually created (with help of a python script). Second problem: the smallest graphical object is a complete system, but I need graphical (and acoustical) informations about every single scores. Unfortunately, the information you wish to have is not available. If you will search the threads about musicXML output, you will see that the inability to couple musical information with graphical information is the main obstacle to musicXML output. The music information is available in the stream events. The graphical information is available in the final output. At present there is no way to connect the two. Ideas have been given before on the -devel lists. I'm sorry there's not a better answer for you. Carl ___ 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: Can't compile docs
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Wednesday, January 05, 2011 5:29 AM
Subject: Re: Can't compile docs
On Tue, Jan 04, 2011 at 09:06:56PM -, Phil Holmes wrote:
I've been creating a patch for the CG and wanted to test it. Early
this afternoon, I edited issues.itexi and compiled it locally, and
the changes were what I'd created. However, I'd missed a minor
edit, so I updated it and tried the make doc again. The change
wasn't reflected in the local web pages.
sigh, I hate it when reality makes nice clean documentation
inaccurate. I've added some warnings about the doc build to the
quick start.
I did a make doc-clean and make doc and got a failed build.
I've retried this a few times since with no joy but much time.
I've also recommended against doc-clean in favor of removing the
build directory entirely.
Without seeing the build error -- and be warned that the actual
build error is probably 200-500 lines above the end of the compile
log -- I would recommend doing
touch Documentation/*.te??
make
and check if that works. If it fails, then try make once more,
since sometimes it fails when you don't have a clean build dir.
If it fails twice in a row, then something is wrong.
If make succeedes, then you could try make doc again. Note
that almost all compile-problems in the docs will be caught by a
plain old make.
Cheers,
- Graham
I'd tried a touch before, and still had no joy. This time I deleted the
build directory, re-ran autoconfigure, recreated the build directory as per
the CG and then ran make, which was OK. LilyPond executes OK. Then ran
make doc and get an error after an hour or so. The last 500 lines of the
terminal output are attached. My build/out-www is essentially empty.
Any thoughts?
--
Phil Holmes
pdfTeX warning (dest): name{Invoking abc2ly} has been referenced but does not e
xist, replaced by a fixed one
pdfTeX warning (dest): name{Invoking musicxml2ly} has been referenced but does
not exist, replaced by a fixed one
pdfTeX warning (dest): name{Invoking midi2ly} has been referenced but does not
exist, replaced by a fixed one
pdfTeX warning (dest): name{Converting from other formats} has been referenced
but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Other editors} has been referenced but does not exi
st, replaced by a fixed one
pdfTeX warning (dest): name{Vim mode} has been referenced but does not exist, r
eplaced by a fixed one
pdfTeX warning (dest): name{Emacs mode} has been referenced but does not exist,
replaced by a fixed one
pdfTeX warning (dest): name{Text editor support} has been referenced but does n
ot exist, replaced by a fixed one
pdfTeX warning (dest): name{External programs} has been referenced but does not
exist, replaced by a fixed one
pdfTeX warning (dest): name{Alternate methods of mixing text and music} has bee
n referenced but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Sharing the table of contents} has been referenced
but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{lilypond-book templates} has been referenced but do
es not exist, replaced by a fixed one
pdfTeX warning (dest): name{Filename extensions} has been referenced but does n
ot exist, replaced by a fixed one
pdfTeX warning (dest): name{Invoking lilypond-book} has been referenced but doe
s not exist, replaced by a fixed one
pdfTeX warning (dest): name{Music fragment options} has been referenced but doe
s not exist, replaced by a fixed one
pdfTeX warning (dest): name{Integrating music and text} has been referenced but
does not exist, replaced by a fixed one
pdfTeX warning (dest): name{An example of a musicological document} has been re
ferenced but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Manual conversions} has been referenced but does no
t exist, replaced by a fixed one
pdfTeX warning (dest): name{Problems running convert-ly} has been referenced bu
t does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Command line options for convert-ly} has been refer
enced but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Invoking convert-ly} has been referenced but does n
ot exist, replaced by a fixed one
pdfTeX warning (dest): name{Why does the syntax change?} has been referenced bu
t does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Updating files with convert-ly} has been referenced
but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Warning staff affinities should only decrease} has
been referenced but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Error message FT_Get_Glyph_Name} has been reference
d but does not exist, replaced by a fixed one
pdfTeX warning (dest): name{Error message Unbound variable %} has been referenc
ed but does not exist,
mensural notation improvements (issue3797046)
Reviewers: , Message: here is the patch set I hinted at several times: http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00212.html http://lists.gnu.org/archive/html/lilypond-devel/2011-01/msg00097.html some changes are just very slightly related: mf/parmesan-custodes.mf just makes custodes longer (inspired by Petrucci's Odhecaton, see http://imslp.org/wiki/Harmonice_Musices_Odhecaton_(Petrucci,_Ottaviano) scm/parser-clef.scm adds Petrucci-like subbass clef lily/ligature-bracket-engraver.cc is hair splitting over what to include and what not. the important ones: mf/parmesan-noteheads.mf adds the noteheads scm/output-lib.scm makes them usable as note head styles the remaining ones add ligature support; to achieve it, I had to reorganise the code, e.g. to create separate stencils for the two notes of a flexa shape (oblique ligature); while at it, I did some todos as well (removed join-right-amount) and added support for some customization: now the user can request flexa shapes even where they are not compulsory by the ligature-flexa property and can control their size within a ligature. these properties must be set for the second note of the flexa; I know it is ugly, but I don't have any better idea, since these are properties of neither a single note, nor of the whole ligature. test files: is it ok to modify existing regression tests? I mean not only adding more, but changing in mensural-ligatures.ly the Ockeghem examples to look more like the ones in codex Chigi, see scans in attachment to http://lists.gnu.org/archive/html/lilypond-devel/2010-12/msg00398.html thanks, p Description: mensural notation improvements - support coloratio (even in ligatures) - more flexible ligatura shapes Please review this at http://codereview.appspot.com/3797046/ Affected files: M lily/include/mensural-ligature.hh M lily/ligature-bracket-engraver.cc M lily/mensural-ligature-engraver.cc M lily/mensural-ligature.cc M mf/parmesan-custodes.mf M mf/parmesan-noteheads.mf M scm/define-grob-properties.scm M scm/define-grobs.scm M scm/output-lib.scm M scm/parser-clef.scm ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
Le 5 janv. 2011 à 11:37, Mats Bengtsson a écrit : Since I haven't been very active on the LilyPond lists the last year, I think it would be appropriate to remove my name from the Current development team list. Mine too, please. I don't think I've done anything in this release. Nicolas ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
2011/1/5 James james.l...@datacore.com:
Nils
On 05/01/2011 15:22, Nils Gey wrote:
Hopefully somebody will send a patch.
Don't you have a Lilypond webmaster to remove the box?
The website is generated in the same way we generate all of our
'documentation' (there are some differences but essentially it is the same).
That is anyone can submit a patch to change the website, however there is a
Doc 'meister' who reviews this and approves any changes to the website which
will get updated periodically.
A dedicated webmaster (maybe in personal union with other tasks) is a good
thing because people like to have one person as contact if they have
problems with the webpage. I strongly recommend to create such a post and/or
to use a Wiki-like CMS to build your website around so that (trusted) users
can edit the pages themselves if its too much work.
We do have such a person. He just sent you a response previously ;)
Do you have any specific suggestions on what it should say or can we just
remove the box entirely?
The attached patch removes the box.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
From 37057211bc1ab4491dc21431cf0ec260c3f66d1a Mon Sep 17 00:00:00 2001
From: Francisco Vila francisco.v...@hispalinux.es
Date: Wed, 5 Jan 2011 22:57:00 +0100
Subject: [PATCH] Web: Remove warning about version used by Denemo.
---
Documentation/web/introduction.itexi |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi
index 75226eb..79a71c7 100644
--- a/Documentation/web/introduction.itexi
+++ b/Documentation/web/introduction.itexi
@@ -1058,11 +1058,6 @@ Moving the cursor in the LilyPond text moves the cursor in the graphical
view, and any syntax errors in your LilyPond tweaks are highlighted in
the text view when printed from there.
-...@warning{denemo officially supports an outdated Lilypond version 2.8.7,
-which lacks many of the features added since then. The Denemo developers
-are actively working to bring it up to our present stable version, 2.12.}
-...@divend
-
@divClass{column-center-top}
@subheading Text editors
--
1.7.0.4
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
2011/1/5 Francisco Vila paconet@gmail.com:
The attached patch removes the box.
Sorry! use this instead, the other removes a @divEnd and it shouldn't.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
From 0ebb81d9a8f278cd1c9211936100b13419def84b Mon Sep 17 00:00:00 2001
From: Francisco Vila francisco.v...@hispalinux.es
Date: Wed, 5 Jan 2011 22:57:00 +0100
Subject: [PATCH] Web: Remove warning about version used by Denemo.
---
Documentation/web/introduction.itexi |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/Documentation/web/introduction.itexi b/Documentation/web/introduction.itexi
index 75226eb..018b151 100644
--- a/Documentation/web/introduction.itexi
+++ b/Documentation/web/introduction.itexi
@@ -1058,9 +1058,6 @@ Moving the cursor in the LilyPond text moves the cursor in the graphical
view, and any syntax errors in your LilyPond tweaks are highlighted in
the text view when printed from there.
-...@warning{denemo officially supports an outdated Lilypond version 2.8.7,
-which lacks many of the features added since then. The Denemo developers
-are actively working to bring it up to our present stable version, 2.12.}
@divEnd
@divClass{column-center-top}
--
1.7.0.4
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 09:59:58PM +0100, Nicolas Sceaux wrote: Le 5 janv. 2011 à 11:37, Mats Bengtsson a écrit : Since I haven't been very active on the LilyPond lists the last year, I think it would be appropriate to remove my name from the Current development team list. Mine too, please. I don't think I've done anything in this release. Significant commits include: Fix 715 page numbers on a bookpart Instanciable scheme engravers Chord repetition I think the last two could be considered fairly major contributions, but it's up to you. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond authors, release notes, announcements
On Wed, Jan 05, 2011 at 08:43:47PM -0700, Colin Campbell wrote: On Wed, 2011-01-05 at 14:38 +, Graham Percival wrote: I think you should be listed in both places; I certainly don't think you should removed from the Documentation list. If somebody has worked in multiples areas, they should be listed in all relevant areas. Well, it's certainly my hope to do both, once the insanity of replacing a CFO just before the year-end audit subsides! Later in the Spring, perhaps. For clarity, the authors list is a reflection of what you have done so far, not what you hope to be doing in the future. On the basis of your work during the 2.12-to-2.14 period, I think you should be listed in both Documentation and Bug squad. Once 2.14 is out, we move all contributor names into past contributor, and start the list again. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Potential issue 39 fix w/ patch
Mike Solomon mikesol at ufl.edu writes: I've included before and after photos. Hi Mike. The hemidemisemiquaver(*) and the minim are supposed to be simultaneous, so I do not like the horizontal shift. There is no mention in issue 39 of the desired output. The only thing I can imagine wanting done automatically is lengthening the stem. Is it too late for that when note-collisions are being handled? If the best achievable output is only slightly more preferable than the collision, but costs significant computation for every note-collision, we might want to simply note this one as 'not worth fixing with the methods tried so far'. I'll still try your patch. -- Keith [*] I'm American, actually, so would normally say 64th note; I just like the cheap thrill I get out of writing hemidemisemiquaver. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond.org - Denemo
On Wed, Jan 5, 2011 at 10:02 PM, Francisco Vila paconet@gmail.com wrote: 2011/1/5 Francisco Vila paconet@gmail.com: The attached patch removes the box. Sorry! use this instead, the other removes a @divEnd and it shouldn't. Thanks, pushed. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
german website problems
None of these warnings happen in the other languages, so I think they're all problems in the german source, rather than in our build system. make website ... Initializing settings for web site: [de] ** closing warning (1 braces missing) (l. 319) *** Undefined node `Development' in @ref (in /main/src/lilypond/Documentation//web/news-front.itexi l. 29 in @qq) *** Undefined node `Development' in @ref (in /main/src/lilypond/Documentation//web/news-front.itexi l. 46 in @qq) *** Undefined node `Development' in @ref (l. 165) *** Undefined node `Development' in @ref (l. 167) *** Undefined node `Entwicklung' in @ref (in /main/src/lilypond/Documentation/de/web/download.itexi l. 68) *** Undefined node `Entwicklung' in @ref (in /main/src/lilypond/Documentation/de/web/manuals.itexi l. 126 in @divClass) *** Undefined node `Entwicklung' in @ref (in /main/src/lilypond/Documentation/de/web/community.itexi l. 25) *** Undefined node `Autoren' in @ref (in /main/src/lilypond/Documentation/de/web/community.itexi l. 28) *** Undefined node `Veröffentlichungen' in @ref (in /main/src/lilypond/Documentation/de/web/community.itexi l. 40 in @divClass) *** Undefined node `Ältere Neuigkeiten' in @ref (in /main/src/lilypond/Documentation/de/web/community.itexi l. 44) *** Unknown node in menu entry `Entwicklung' (in /main/src/lilypond/Documentation/de/web/community.itexi l. 62) *** Unknown node in menu entry `Autoren' (in /main/src/lilypond/Documentation/de/web/community.itexi l. 63) *** Unknown node in menu entry `Veröffentlichungen' (in /main/src/lilypond/Documentation/de/web/community.itexi l. 64) *** Unknown node in menu entry `Ältere Neuigkeiten' (in /main/src/lilypond/Documentation/de/web/community.itexi l. 65) WARNING: Unable to load the map file WARNING: Unable to find node 'Entwicklung' in book . WARNING: Unable to find node 'Entwicklung' in book . - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Can't compile docs
On Wed, Jan 05, 2011 at 05:30:09PM -, Phil Holmes wrote:
pdfTeX warning (dest): name{Invoking abc2ly} has been referenced but does not
e
xist, replaced by a fixed one
pdfTeX warning (dest): name{Invoking musicxml2ly} has been
referenced but does not exist, replaced by a fixed one
These don't look great, but I think they're normal problems.
cp -p web.texi out-www/web.texi
cp: cannot stat `web.texi': No such file or directory
make[3]: *** [out-www/web.texi] Error 1
make[3]: Leaving directory `/home/phil/lilypond-git/build/Documentation/de'
This is the actual problem, and the de/ part (German) is
absolutely vital, but I don't know how it's happening.
If you run:
git status
do you see something like this?
# On branch master
# Changed but not updated:
# (use git add/rm file... to update what will be committed)
# (use git checkout -- file... to discard changes in working
# directory)
#
# deleted:Documentation/de/web.texi
#
if so, the build problem is understandable, and you can fix it by
running:
git reset --hard origin
Do you have a
Documentation/de/web.texi
? (if not, git should notice this, but evidently something really
strange is happening, so if you don't see a problem in git status,
please check manually)
NB: you should have *both* a
Documentation/de/web/ directory (or folder), and
Documentation/de/web.texi file
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
