Re: Different file lengths and line numbers (Re: Broken Spanish documentation)

2007-08-25 Thread John Mandereau
Le dimanche 26 août 2007 à 03:03 +0200, Francisco Vila a écrit : > Yes, of course it does help. I used to view these details in the > savannah web interface or in gitk These interfaces are easier to use, but the command line is always faster :-) > > As you say, the question is which case works,

Different file lengths and line numbers (Re: Broken Spanish documentation)

2007-08-25 Thread Francisco Vila
El Sat, 25 de Aug de 2007, a las 10:55:25PM +0200, John Mandereau dijo: > > Not really; what matters is which case (upper- or lower-) works. My > recent commit messages to Git tell you all the details -- pull then do > "git log", and if you want to see a particular diff, do "git show > ". > > HT

Re: make LILYPOND_EXTERNAL_BINARY web fails on linux

2007-08-25 Thread Han-Wen Nienhuys
Graham Percival escreveu: > Linux/i386, debian/testing, lily 2.11.30 > > [EMAIL PROTECTED]:~/usr/src/lilypond/input$ make > LILYPOND_EXTERNAL_BINARY=~/usr/lilypond/usr/bin/lilypond web this looks fishy. It should be something like make LILYPOND_EXTERNAL_BINARY=~/usr/bin/lilypond web (you have

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Han-Wen Nienhuys
Graham Percival escreveu: > It's a question of 2.10 or 2.11 -- we'd have to drop 2.10, which might why would that be? I recommend having a separate database for each major branch, eg 2.8 and 2.10. Then there could be a mechanism to point the default from 2.10 to 2.12 once it's ready. > result

make LILYPOND_EXTERNAL_BINARY web fails on linux

2007-08-25 Thread Graham Percival
Linux/i386, debian/testing, lily 2.11.30 [EMAIL PROTECTED]:~/usr/src/lilypond/input$ make LILYPOND_EXTERNAL_BINARY=~/usr/lilypond/usr/bin/lilypond web make --no-builtin-rules out=www WWW make[1]: Entering directory `/home/gperciva/usr/src/lilypond/input' cd ./out-www; /home/gperciva/usr/lilypon

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Graham Percival
Han-Wen Nienhuys wrote: Graham Percival escreveu: OK - I will be traveling the 1st weeks of september, so it's unlikely that a stable release will happen before the beginning of October. That sounds perfect. I'd like to have a longer period between "almost ready" and "released". This

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Han-Wen Nienhuys
Francisco Vila escreveu: > El sáb, 25-08-2007 a las 16:32 -0700, Graham Percival escribió: >> Han-Wen Nienhuys wrote: >>> Comments, ideas? >>> >> I've been meaning to introduce this topic for months, right after I do a >> complete survey (and if necessary, update) of all existing bugs. This >

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Han-Wen Nienhuys
Graham Percival escreveu: > The docs are generally ok, but I'd like to take another look at the new > Program Usage manual. Again, I expect to be done by the end of August. > I'm not certain if the translators want to look at this before 2.12 > comes out. OK - I will be traveling the 1st weeks o

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Francisco Vila
El sáb, 25-08-2007 a las 16:32 -0700, Graham Percival escribió: > Han-Wen Nienhuys wrote: > > Comments, ideas? > > > I've been meaning to introduce this topic for months, right after I do a > complete survey (and if necessary, update) of all existing bugs. This > should happen Real Soon Now (

Re: Request for comments: LilyPond 2.12

2007-08-25 Thread Graham Percival
Han-Wen Nienhuys wrote: Comments, ideas? I've been meaning to introduce this topic for months, right after I do a complete survey (and if necessary, update) of all existing bugs. This should happen Real Soon Now (tm). The docs are generally ok, but I'd like to take another look at the new

Request for comments: LilyPond 2.12

2007-08-25 Thread Han-Wen Nienhuys
Hello everyone, Since most of the horizontal and vertical spacing hacks of Joe have stabilized, I think it is time now to start considering a new stable release. With the current release process, it should be possible to build a new stable release in a matter of days, so the real question, are

Re: plug ins...

2007-08-25 Thread Han-Wen Nienhuys
Carl D. Sorensen escreveu: >> -Original Message- >> From: Mike Salmon [mailto:[EMAIL PROTECTED] >> Sent: Friday, August 24, 2007 1:45 PM >> To: lilypond-devel@gnu.org >> Subject: plug ins... >> >> Hi all, >> >> I'm trying to find the staff code which generates the '-' >> symbol to make th

RE: plug ins...

2007-08-25 Thread Carl D. Sorensen
> -Original Message- > From: Mike Salmon [mailto:[EMAIL PROTECTED] > Sent: Friday, August 24, 2007 1:45 PM > To: lilypond-devel@gnu.org > Subject: plug ins... > > Hi all, > > I'm trying to find the staff code which generates the '-' > symbol to make the staff lines as I would like them

Re: Doc uptate patches

2007-08-25 Thread John Mandereau
Le mercredi 22 août 2007 à 19:18 +0200, Jean-Charles Malahieude a écrit : > Hi all ! > > Please apply both patches towards lilypond/translation. I've applied the first patch, the second will be included in my complete revision of instrument-notation.itely. Salut, John

Re: Broken Spanish documentation

2007-08-25 Thread John Mandereau
Le mercredi 22 août 2007 à 00:03 +0200, Francisco Vila a écrit : > El mar, 21-08-2007 a las 10:13 +0200, John Mandereau escribió: > > > Maybe this is caused by your recent change to @documentencoding in > > es/user/lilypond.tely (UTF-8 -> utf-8) -- why did you want to write the > > encoding lower-

Re: Broken Spanish documentation

2007-08-25 Thread John Mandereau
Le lundi 20 août 2007 à 20:15 +0200, Paco a écrit : > Hello all, > > I don't really if in 2.11.29 the link to the Spanish HTML manual worked, > but now in 2.11.30 it is broken. > > Also, the Spanish PDF lacks of accented characters at all, maybe my last > patches were not properly coded as UTF-8?

Fw: Suggestion for Lilypond Accidental option

2007-08-25 Thread Werner LEMBERG
I was asked to forward this mail. Werner --- Begin Message --- Hi, I found your email through the devel email archives. Please forward this to the appropriate people. Suggestion for additional style: teaching The teaching style would print cautionary accidents for all sharp or flat to