Re: compile.itely placement

2009-03-13 Thread Graham Percival
On Fri, Mar 13, 2009 at 12:49:48PM +0100, John Mandereau wrote: > Graham Percival a écrit : >> I'm not clear about this, either. Actually, if anything >> introduction.itely is going to die entirely (as part of the >> web-gop stuff). >> > All right. I can't work on GOP in the 4 coming weeks: I

Re: compile.itely placement

2009-03-13 Thread John Mandereau
Graham Percival a écrit : I'm not clear about this, either. Actually, if anything introduction.itely is going to die entirely (as part of the web-gop stuff). All right. I can't work on GOP in the 4 coming weeks: I must work on translaed documentation compilation by translating node names in

Re: compile.itely placement

2009-03-13 Thread Graham Percival
On Fri, Mar 13, 2009 at 10:56:40AM +0100, John Mandereau wrote: > Trevor Daniels a écrit : >> Re your recent commits: >> >> shouldn't compile.itely and introduction.itely be in /devel rather >> than /user? > I don't understand why you suggest to place introduction.itely in devel/. I'm not clear

Re: compile.itely placement

2009-03-13 Thread John Mandereau
Trevor Daniels a écrit : Re your recent commits: shouldn't compile.itely and introduction.itely be in /devel rather than /user? I don't understand why you suggest to place introduction.itely in devel/. As for compile.itely, it's easier to put it in user/, because compilation of Texinfo docs i

compile.itely placement

2009-03-13 Thread Trevor Daniels
John Re your recent commits: shouldn't compile.itely and introduction.itely be in /devel rather than /user? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel