It works on PPC 10.5.5 (PowerBook 1.67 MHz)
Stan
On Oct 3, 2008, at 5:30 PM, Han-Wen Nienhuys wrote:
See
http://lilypond.org/~hanwen/lilypad.tar.bz2
this does not include lilypond itself, but if gui wrapper works, I
will put it in the next builds for GUB. Can people verify on the
following
Lilypond app works for me, on 10.5.4 x86.
Carl
On 10/3/08 4:30 PM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> See
>
> http://lilypond.org/~hanwen/lilypad.tar.bz2
>
> this does not include lilypond itself, but if gui wrapper works, I
> will put it in the next builds for GUB. Can people v
starts up in x86, intel!
Josh
On Oct 3, 2008, at 3:30 PM, Han-Wen Nienhuys wrote:
http://lilypond.org/~hanwen/lilypad.tar.bz2
**
/* Joshua D. Parmenter
http://www.realizedsound.net/josh/
“Every composer – at all times and in all cases – gives his own
See
http://lilypond.org/~hanwen/lilypad.tar.bz2
this does not include lilypond itself, but if gui wrapper works, I
will put it in the next builds for GUB. Can people verify on the
following platforms?
10.3 PPC
10.4 PPC
10.5 PPC (?)
10.4 x86
10.5 x86
On Fri, Oct 3, 2008 at 7:18 PM
You need to have a python (2.4 or newer) installation that includes py2app,
http://svn.pythonmac.org/py2app/py2app/trunk/doc/index.html
when you have that, you should check out the lilypad installer at
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=shortlog;h=refs/heads/macos-lilypad
then
lgtm
http://codereview.appspot.com/6453/diff/205/6
File lily/arpeggio.cc (right):
http://codereview.appspot.com/6453/diff/205/6#newcode22
Line 22: #define EPS 1e-3
use const
http://codereview.appspot.com/6453/diff/205/6#newcode109
Line 109: while (mol.extent (Y_AXIS).length () + EPS < heads.le
2008/10/3 John Mandereau <[EMAIL PROTECTED]>:
> On 2008/10/03 20:32 +0200, Francisco Vila wrote:
>> Done, it's my first time, sorry for the dumb commit name.
>
> All this advice is for the next time...
> When you merge a branch, you're supposed to keep the commit message head
> line, so it's obviou
On 2008/10/03 20:32 +0200, Francisco Vila wrote:
> Done, it's my first time, sorry for the dumb commit name.
All this advice is for the next time...
When you merge a branch, you're supposed to keep the commit message head
line, so it's obvious this commit is a merge commit, and you must keep
the c
2008/10/3 John Mandereau <[EMAIL PROTECTED]>:
> Hi Francisco,
>
> I can't merge lilypond/translation into master because it produces
> conflicts in 3 doc files in Spanish; could you merge and fix the
> conflicts yourself, and push the result to either lilypond/translation
> or master (pushing to bo
Hi Francisco,
I can't merge lilypond/translation into master because it produces
conflicts in 3 doc files in Spanish; could you merge and fix the
conflicts yourself, and push the result to either lilypond/translation
or master (pushing to both is better, but it's not essential)?
Thanks in advance
2008/10/2 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> On Wed, Oct 1, 2008 at 6:28 PM, <[EMAIL PROTECTED]> wrote:
>> I decided to use rint () instead since I can't see a situation where it
>> wouldn't work (obviously apart from the case where somebody changes
>> Arpeggio #'font-size); isn't the extent
Valentin, you wrote Friday, October 03, 2008 8:42 AM
2008/10/2 Trevor Daniels <[EMAIL PROTECTED]>:
I wish we could have a "common notation" section that would deal with
the voice as an instrument (for instance, the parlato notehead example
is quite good; we could also add the
http://lsr.dsi.u
2008/10/3 Werner LEMBERG <[EMAIL PROTECTED]>:
>
>> I'm simply suggesting that we should use (or there should be a)
>> Texi2XHMTL rather than Texi2HTML.
>
> Ahh, this is something *completely* different :-) XHTML is fine -- the
> closing tags (not necessary in HTML) are good for humans too, but XML
2008/10/2 Trevor Daniels <[EMAIL PROTECTED]>:
> I have to agree with you that Common notation for vocals
> is too long, and would be better split into at least two
> sections. Taking your idea a little further, what do you
> think about
>
> 2.1.1 Common notation for entering lyrics
> Refere
14 matches
Mail list logo
