Re: keyboard-headword.ly

2008-07-03 Thread Graham Percival
Thanks, applied. Cheers, - Graham On Wed, 2 Jul 2008 20:27:11 -0700 "Patrick McCarty" <[EMAIL PROTECTED]> wrote: > On Wed, Jul 2, 2008 at 1:35 PM, Graham Percival <[EMAIL PROTECTED]> > wrote: > > > > Also, could somebody deal fix this file? I still haven't read up > > on UTF-8, and don't reall

Re: keyboard-headword.ly

2008-07-02 Thread Patrick McCarty
On Wed, Jul 2, 2008 at 1:35 PM, Graham Percival <[EMAIL PROTECTED]> wrote: > > Also, could somebody deal fix this file? I still haven't read up > on UTF-8, and don't really know how to differentiate between it > and plain ascii. Here's a patch to fix the file. Thanks, Patrick 0001-Fix-encoding

Re: keyboard-headword.ly

2008-07-02 Thread Graham Percival
On Wed, 02 Jul 2008 06:41:12 +0200 (CEST) Werner LEMBERG <[EMAIL PROTECTED]> wrote: > > > This example gives a warning: > > > Preprocessing graphical objects... > > > programming error: FT_Get_Glyph_Name () error: invalid argument > > > continuing, cross fingers [...] > > > > You've saved his cod

Re: keyboard-headword.ly

2008-07-01 Thread Werner LEMBERG
> > This example gives a warning: > > Preprocessing graphical objects... > > programming error: FT_Get_Glyph_Name () error: invalid argument > > continuing, cross fingers [...] > > You've saved his code in the wrong encoding (probably latin-1). Just > save or convert it to UTF-8, and everything's

Re: keyboard-headword.ly

2008-07-01 Thread Werner LEMBERG
> This example gives a warning: > Preprocessing graphical objects... > programming error: FT_Get_Glyph_Name () error: invalid argument > continuing, cross fingers [...] You've saved his code in the wrong encoding (probably latin-1). Just save or convert it to UTF-8, and everything's fine.

Re: keyboard-headword.ly

2008-07-01 Thread Andrew Hawryluk
I like the Ravel. Sergei will have to wait another 5.5 years before appearing in the LP docs. Andrew On Tue, Jul 1, 2008 at 4:50 PM, Graham Percival <[EMAIL PROTECTED]> wrote: > On Tue, 1 Jul 2008 23:34:17 +0100 > "Neil Puttock" <[EMAIL PROTECTED]> wrote: > >> BTW, I think some of the headwords w

Re: keyboard-headword.ly

2008-07-01 Thread Graham Percival
On Tue, 1 Jul 2008 23:34:17 +0100 "Neil Puttock" <[EMAIL PROTECTED]> wrote: > BTW, I think some of the headwords would look better without > ragged-right = ##t. Modify at will. :) In this case, please change the actual .ly. Cheers, - Graham ___ lily

Re: keyboard-headword.ly

2008-07-01 Thread Neil Puttock
2008/7/1 Graham Percival <[EMAIL PROTECTED]>: > This example gives a warning: > Preprocessing graphical objects... > programming error: FT_Get_Glyph_Name () error: invalid argument > continuing, cross fingers > programming error: Glyph has no name, but font supports glyph > naming. > Skipping glyp

Re: keyboard-headword.ly

2008-07-01 Thread Graham Percival
On Tue, 1 Jul 2008 21:53:15 +0100 "Neil Puttock" <[EMAIL PROTECTED]> wrote: > 2008/7/1 Graham Percival <[EMAIL PROTECTED]>: > > Andrew, sorry about this. We've had this problem before with > > beautiful examples; see the mailist archives from... last Dec, I > > think. Trevor Baca had a beautiful

Re: keyboard-headword.ly

2008-07-01 Thread Neil Puttock
2008/7/1 Graham Percival <[EMAIL PROTECTED]>: > Oops! I forgot to check this. Deleted, and rebuilding GDP output > to remove the infraction from that webserver. > > Andrew, sorry about this. We've had this problem before with beautiful > examples; see the mailist archives from... last Dec, I thi

Re: keyboard-headword.ly

2008-07-01 Thread Graham Percival
Oops! I forgot to check this. Deleted, and rebuilding GDP output to remove the infraction from that webserver. Andrew, sorry about this. We've had this problem before with beautiful examples; see the mailist archives from... last Dec, I think. Trevor Baca had a beautiful example from... Rachma

keyboard-headword.ly

2008-07-01 Thread Neil Puttock
Hi everybody, Andrew's snippet for section 2.2 (Rach G minor prelude), whilst lovely, is unfortunately still under copyright in the EU (life + 70 years), so can't be included in the docs. :( Regards, Neil ___ lilypond-devel mailing list lilypond-devel