Rune Zedeler [EMAIL PROTECTED] writes:
Where can the famous patch be found?
In GUB, pull from http://lilypond/vc/gub.darcs, or
http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch
(Unable to compile latest guile-cvs).
(You may want to report that too)
Jan.
--
Jan
HN == Han-Wen Nienhuys [EMAIL PROTECTED] writes:
HN I notice that there are lots of functions to inspect music data
HN structures. It would be best if they were in a separate
HN file. Then, over time we can migrate them to the lilypond 'core'
HN Also, would it be possible to
John Mandereau escreveu:
Speaking of, isn't scripts/rev-to-commit.py supposed to update the
committishes automagically? It would need an update to work, though.
no, rev-to-commit was a hack to transition from CVS to git.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] -
Rune Zedeler escreveu:
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
see install.txt
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
HN == Han-Wen Nienhuys [EMAIL PROTECTED] writes:
HN also, on the larger scale, I don't fully understand the need for
HN the patch. Why isn't possible to have script/program that sings
HN any MIDI file? LilyPond already exports its lyrics to MIDI. I
HN imagine that the only
Joe Neeman escreveu:
On 1/3/07, *Han-Wen Nienhuys* [EMAIL PROTECTED]
mailto:[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
I will comment somehwo more differented later on, now just some short thoughts.
maybe the best is i would then just read the updated file (as you suggested)
and make my comments.
Original-Nachricht
Datum: Wed, 03 Jan 2007 00:35:25 +0100
Von: John Mandereau [EMAIL PROTECTED]
Le mercredi 03 janvier 2007 à 00:10 -0600, Daniel Tonda Castillo a
écrit :
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
Hello,
it seems that sometimes people push their origin branch
to savannah. Can you double check that you are not doing this?
FWIW, I use
git push sav
with .git/config
[remote sav]
url = ssh+git://[EMAIL PROTECTED]/srv/git/lilypond.git
push = master:refs/heads/master
Daniel Tonda Castillo wrote:
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...
I think I missed something... my understanding was that contexts were
created automatically as needed. In other words,
{ c'4 }
automatically expanded to
\score{
\new Staff {
\new Voice {
c'4
}
}
}
However, in bug 176 (below), a progerror went away by replacing a \new
Staff
Hi Daniel,
Congratulations on finishing the Spanish site, we now have 4 complete
translations!
You're probably working on this (saw your git efforts), but to a
non-spanish speaker as myself this looks a bit funny
lilypond.org/web/index.es.html (divider lines by me)
Sumérjase en ... de
Graham Percival escreveu:
I think I missed something... my understanding was that contexts were
created automatically as needed. In other words,
{ c'4 }
automatically expanded to
\score{
\new Staff {
\new Voice {
c'4
}
}
}
no, it doesn't work like that. The c4
Hi Graham,
I'm currently adding
@ignore
Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
When revising a translation, copy the HEAD committish of the
version that you are working on. See TRANSLATION for details.
@end ignore
headers to .(i)tely files of the user manual, in
John Mandereau wrote:
headers to .(i)tely files of the user manual, in order to make
translation checks, and I just saw that point-and-click.itely seems to
be stalled: it isn't included in lilypond.tely, and there is already a
Point and click node in running.itely. What should we do with this
Graham Percival wrote:
John Mandereau wrote:
headers to .(i)tely files of the user manual, in order to make
translation checks, and I just saw that point-and-click.itely seems to
be stalled: it isn't included in lilypond.tely, and there is already a
Point and click node in running.itely.
Jan Nieuwenhuizen escribió:
Hi Daniel,
Congratulations on finishing the Spanish site, we now have 4 complete
translations!
You're probably working on this (saw your git efforts), but to a
non-spanish speaker as myself this looks a bit funny
lilypond.org/web/index.es.html (divider lines by me)
John Mandereau wrote:
All translation hints other than support for a particular user should be
in English, so that all translators can share it.
Yes, that is totally true
Please read the revised README and translate the parts of README.de that
brings something interesting in addition to
The funny thins is that before I did any pull, everything worked out
just fine. This might be a problem due to my using cogito in ubuntu.
I'll try to compile a newer version of git and use that instead. In the
meantime what are your suggestions?
Daniel Tonda C.
John Mandereau escribió:
Hi,
so here comes the new German patch. As for now when making format-patch
I get three patches. One was the last one which is already applied to
the internet, the other is my own README.de, which I would like to
remove, and the third is the addition I did today. So I think you should
only
Daniel Tonda Castillo wrote:
Jan Nieuwenhuizen escribió:
Hi Daniel,
Congratulations on finishing the Spanish site, we now have 4 complete
translations!
You're probably working on this (saw your git efforts), but to a
non-spanish speaker as myself this looks a bit funny
Daniel Tonda Castillo wrote:
The funny thins is that before I did any pull, everything worked out
just fine. This might be a problem due to my using cogito in ubuntu
I'll try to compile a newer version of git and use that instead. In the
meantime what are your suggestions?
If you don't
[EMAIL PROTECTED]:
Rune Zedeler escreveu:
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
see install.txt
There is no install.txt, and the INSTALL.txt I found does not mention it:
$ git-pull
remote: Generating pack...
...
rename
Karl Hammar wrote:
[EMAIL PROTECTED]:
Rune Zedeler escreveu:
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
see install.txt
There is no install.txt, and the INSTALL.txt I found does not mention it:
At www.lilypond.org, click on the
Till Rettig wrote:
John Mandereau wrote:
Please read the revised README and translate the parts of README.de that
brings something interesting in addition to the English README.
Well, no I checked it. I don't think there is anything I have in my own
version. Just now when I commit I
Rune Zedeler [EMAIL PROTECTED] writes:
Where can the famous patch be found?
...
http://lilypond.org/vc/gub.darcs/patches/guile-1.8-rational.patch
...
Got the patch and build debian guile debs for i386.
If anybody would need them, they are available at:
Karl Hammar wrote:
[EMAIL PROTECTED]:
Rune Zedeler escreveu:
Where can the famous patch be found?
(Unable to compile latest guile-cvs).
see install.txt
There is no install.txt, and the INSTALL.txt I found does not mention it:
At www.lilypond.org,
Hmm, when building I get:
out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'.
out/music-glossary.nexi:6: warning: unrecognized encoding name `utf-8'.
out/INSTALL.texi:6: warning: unrecognized encoding
[lilypond 2.11.7]
I've just received the attached MusicXML file for testing purposes.
Trying musicxml2ly on this file, the script aborts with
Traceback (most recent call last):
File /usr/local/bin/musicxml2ly, line 656, in ?
main()
File /usr/local/bin/musicxml2ly, line 653, in
Le jeudi 04 janvier 2007 à 00:33 +0100, Karl Hammar a écrit :
Hmm, when building I get:
out/lilypond.nexi:62: warning: unrecognized encoding name `utf-8'.
out/lilypond-internals.nexi:10: warning: unrecognized encoding name `utf-8'.
out/music-glossary.nexi:6: warning: unrecognized encoding
Hello,
I've just pushed check-translation support for the user manual to
stable/2.10. I've done
cd Documentation
make ISOLANG=fr check-translation
for a testing purpose. How does it look to you?
As I'm currently the only person able to update the French user manual,
so it seems
John Mandereau wrote:
As I'm currently the only person able to update the French user manual,
so it seems to me a urgent issue. In the coming days/weeks, I'll
actually update French translation in stable/2.10, write documentation
for translators (in Documentation/TRANSLATION), cherry-pick the
32 matches
Mail list logo
