After finishing the priority 3 files which already have been sent, I
tried to do a pull to merge everything and get the newest web site.
Locally there were no errors when committing, this seems to have
happened after putting a different committish after the first commit.
After a bunch of erro
On 1/3/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Just a quick idea: how about adapting the skyline procedures to
also put crude outlines of beams and slurs in the staff outline?
With a bit of luck, we could use that to scrap the
outside_slur_callback.
If we did a bezier -> bunch of str
I get a lot of merge errors, after the git-pull:
git-rev-parse web/master
745ee84ea5b583686e53dc2628e5067492997773
[EMAIL PROTECTED]: lilypond]$ git pull
git://git.sv.gnu.org/lilypond.git/ web/master:web/master
Trying really trivial in-index merge...
es/sponsor/index.html: needs merge
es/sponso
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
-Rune
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Han-Wen Nienhuys wrote:
> John Mandereau escreveu:
> >>> git-rev-list HEAD | head -1
> >> It is way easier to say
> >>
> >> $ git rev-parse HEAD
> >
> > That's what README tells now.
>
> Actually, I think it's better to use
>
> make show-committish
>
> (which you removed from the README).
John Mandereau escreveu:
>>> git-rev-list HEAD | head -1
>> It is way easier to say
>>
>> $ git rev-parse HEAD
>
> That's what README tells now.
Actually, I think it's better to use
make show-committish
(which you removed from the README).
The SHA1 of the original is likely to be the one
Daniel Tonda wrote:
> I'm sorry but I made a mistake concerning the title of the second mail:
> "Priority 2 Translation of web site to spanish"
>
> It was supposed to be for the:
> Priority 3 Translation of web site to spanish
>
> I attach it again just in case it went unnoticed because of the ti
Ok, thanks!
2007/1/2, John Mandereau <[EMAIL PROTECTED]>:
Daniel Tonda wrote:
> I've finished the priority 3 files for the lilypond-web site:
>
> According to the mail I sent about dangling directory, the files should be:
>
> es/sponsor/index.html
> es/sponsor/natura.html
> es/sponsor/options.ht
Hi,
On Wed, 3 Jan 2007, John Mandereau wrote:
> Johannes Schindelin wrote:
> >
> > On Mon, 1 Jan 2007, Till Rettig wrote:
> >
> > > Es ist dabei wichtig, dass die erste Zeile das commitish enthält,
> >
> > Why would it be important that the first line has a committish?
>
> To record the revi
Just a quick idea: how about adapting the skyline procedures to
also put crude outlines of beams and slurs in the staff outline?
With a bit of luck, we could use that to scrap the
outside_slur_callback.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software
Johannes Schindelin wrote:
> Hi,
>
> I'll just comment the German text in English, and leave the complete
> translation to you...
>
> On Mon, 1 Jan 2007, Till Rettig wrote:
>
> > Es muss git (und evtl. cogito) installiert sein, das letztere
> > Vereinfacht die Handhabung. Weitere Informationen
Daniel Tonda wrote:
> I've finished the priority 3 files for the lilypond-web site:
>
> According to the mail I sent about dangling directory, the files should be:
>
> es/sponsor/index.html
> es/sponsor/natura.html
> es/sponsor/options.html
> es/about/automated-engraving/applications.html
> es/ab
Hi,
I'll just comment the German text in English, and leave the complete
translation to you...
On Mon, 1 Jan 2007, Till Rettig wrote:
> Es muss git (und evtl. cogito) installiert sein, das letztere
> Vereinfacht die Handhabung. Weitere Informationen finden sich auch noch
> im LilyPond-Wiki
>
Till Rettig wrote:
> This is now about the help file that I wrote (more or less for myself)
> to make the translation process and work with git a bit clearer. It kind
> of combines what was there about using git on this list the last weeks,
> some hints from the wiki and reference to the README
Till Rettig wrote:
> Jan Nieuwenhuizen wrote:
> > This imported cleanly. Thanks. John Mandereau, our new Translation
> > Meister will be taking over from me.
> >
> >
> Ok, will remember this. In fact I sent another patch a couple of hours
> later on to make up the mess in the testimonials.ht
Werner LEMBERG wrote:
> > Btw, is there any chance that Texinfo is actively developed to
> > support internationalization? Would that need sponsoring, or an
> > important number of contributors?
>
> What do you mean with `internationalization'? Limited UTF-8 support
> has been added Dec. 30th to
> BTW It would probably be easier to tag the note,
>
> < \tieToVoice #"othervoice" e >
>
> then the staff level engraver notices the E, and looks for a
> matching note from Voice = "othervoice".
I will accept (almost) all constructions to make this work. Given the
many abilities of lilypond, t
> Btw, is there any chance that Texinfo is actively developed to
> support internationalization? Would that need sponsoring, or an
> important number of contributors?
What do you mean with `internationalization'? Limited UTF-8 support
has been added Dec. 30th to the CVS of texinfo.tex (using th
Milan Zamazal escreveu:
> We have finished the first version of the LilyPond singing support using
> the Festival speech synthesis system. On the user side it works
> somewhat similarly to MIDI output: The user inserts a special LilyPond
> command to lyrics places he wants to sing and by processin
Milan Zamazal escreveu:
>> "HN" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> HN> - Do you want this to be integrated in to LilyPond?
>
> Yes, it's much easier for users to get the functionality with LilyPond.
>
> HN> AFAICT, the patch well separated from LilyPond, and quite
This is now about the help file that I wrote (more or less for myself)
to make the translation process and work with git a bit clearer. It kind
of combines what was there about using git on this list the last weeks,
some hints from the wiki and reference to the README file. Han-Wen
thought t
Jan Nieuwenhuizen wrote:
Till Rettig <[EMAIL PROTECTED]> writes:
> Here is the patch!
This imported cleanly. Thanks. John Mandereau, our new Translation
Meister will be taking over from me.
Ok, will remember this. In fact I sent another patch a couple of hours
later on to make up t
Werner LEMBERG escreveu:
>> I think the approach should be to have an engraver at Staff level,
>> which will collect especially tagged tie-events and attach them to
>> noteheads from a different Voice.
>
> What do you consider as `especially tagged tie events'? Is this
> something on the user le
> I think the approach should be to have an engraver at Staff level,
> which will collect especially tagged tie-events and attach them to
> noteheads from a different Voice.
What do you consider as `especially tagged tie events'? Is this
something on the user level?
Werner
_
Han-Wen Nienhuys wrote:
Werner LEMBERG escreveu:
This is more or less the same feature request as
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00841.html
and
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00842.html
Indeed! I missed that somehow. And his
Werner LEMBERG escreveu:
>> This is more or less the same feature request as
>> http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00841.html
>> and
>> http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00842.html
>
> Indeed! I missed that somehow. And his <<< ... >>> suggestion
Wilbert Berendsen wrote:
Shouldn't in this case the dots be placed centered above the stems rather
than the note head? Because I have some heavily sloped 8-note beams, where
the staccato dots are placed almost inside the beam.
Before changing the program in this manner, we would need to see s
Milan Zamazal escreveu:
> We have finished the first version of the LilyPond singing support using
> the Festival speech synthesis system. On the user side it works
> somewhat similarly to MIDI output: The user inserts a special LilyPond
> command to lyrics places he wants to sing and by processin
On Tuesday 02 January 2007 13:39, Werner LEMBERG wrote:
> > This is more or less the same feature request as
> > http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00841.html
> > and
> > http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00842.html
>
> Indeed! I missed that somehow
Cameron Horsburgh wrote:
An addition for the manual in section 10.3.1 "Creating MIDI Files"
after the second sentence
Thanks, that's perfect. Added to git.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.or
Till Rettig <[EMAIL PROTECTED]> writes:
> Ok, I checked again the wiki pages and made a new version of my local
> git repository, and finally I got the right commitish and could add
> changes! Here is the patch!
This imported cleanly. Thanks. John Mandereau, our new Translation
Meister will be
On 1/2/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Joe Neeman escreveu:
> diff --git a/lily/grob.cc b/lily/grob.cc
> index 139a387..91f8ce5 100644
> --- a/lily/grob.cc
> +++ b/lily/grob.cc
> @@ -420,11 +420,21 @@ Grob::extent (Grob *refp, Axis a) const
> Interval
> Grob::pure_height (Gr
Werner LEMBERG escreveu:
> Calling Windows version of lilypond 2.11.7 on a simple file gives an
> `unbound variable' error for `times' in lily.scm, line 358.
Thanks, fixed.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notati
Jan Nieuwenhuizen wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> >> Can't we make a marco (_i x) as a marker, that expands to x, like the
> >> _i we use in C++?
> >
> > Yes, good idea.
>
> Done. Shall we use the regular po/lilypond.pot file for translation,
> which means hooking-up mu
Joe Neeman escreveu:
> diff --git a/lily/grob.cc b/lily/grob.cc
> index 139a387..91f8ce5 100644
> --- a/lily/grob.cc
> +++ b/lily/grob.cc
> @@ -420,11 +420,21 @@ Grob::extent (Grob *refp, Axis a) const
> Interval
> Grob::pure_height (Grob *refp, int start, int end)
> {
> - SCM proc = get_pro
Han-Wen Nienhuys wrote:
> I have a questoin: can you have a look at the png-ln target in
> doclang-targets.make
> and see if it's still necessary. I've commented it out, because
>
> on/user/./out-www/lily-accb4c008b.png ./out-www/lily-accb4c008b.png && ln
> -sf ../../../../Documentation/user/.
Joe Neeman escreveu:
> Sure. I assume the first number is the percentage of lines covered in
> that file, but what does (lines) mean?
number of covered lines in the file, I think.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Musi
> This is more or less the same feature request as
> http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00841.html
> and
> http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00842.html
Indeed! I missed that somehow. And his <<< ... >>> suggestion is
also very nice. In the backg
This is more or less the same feature request as
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00841.html
and
http://lists.gnu.org/archive/html/lilypond-user/2006-12/msg00842.html
/Mats
Werner LEMBERG wrote:
How can I pass a slur from one voice to another one?
Look at this examp
Calling Windows version of lilypond 2.11.7 on a simple file gives an
`unbound variable' error for `times' in lily.scm, line 358.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>> Can't we make a marco (_i x) as a marker, that expands to x, like the
>> _i we use in C++?
>
> Yes, good idea.
Done. Shall we use the regular po/lilypond.pot file for translation,
which means hooking-up music-functions.ly?
Jan.
--
Jan Nieuwenhui
An addition for the manual in section 10.3.1 "Creating MIDI Files"
after the second sentence
[The tempo is specified using the \tempo command. In this example the
tempo of quarter notes is set to 72 beats per minute.] The tempo
specification can not take dotted note lengths as an argumen
How can I pass a slur from one voice to another one?
Look at this example, something which happens quite often in piano or
organ music:
\relative c'' {
<< { 1 | 1 | 1 } \\
{ d16 e8. ~ e2. ~ | \stemUp e1 ~ | e1 } >>
}
Starting with the second bar I would li
43 matches
Mail list logo
