Le lundi 10 août 2009 à 01:18 -0700, Graham Percival a écrit :
> We've lost 50% of potential contributors to the website because of
> git.
And we've lost the same percentage of potential French translators; I'm
sorry to remark that most of them who didn't spend the effort to master
Git and stopped
Le lundi 10 août 2009 à 00:36 +0100, Ian Hulin a écrit :
> So providing we could stitch this into the lilypond parsing, you could get
> \afterGrace #(5.16) {c'1} {d16[ e16]) ;or
> \afterGrace {c1} {d16[ e16]} ; or even
>
> \afterGrace #:fraction #(5.16} #main: {c1} #grace {d16[ e 16]} ; and
> \af
Le mardi 11 août 2009 à 04:46 -0700, Graham Percival a écrit :
> Odd behavior: if I rm -rf target/*/build/lilypond*,
> target/*/src/lilypond*, target/*/status/lilypond*, and
> target/*/installer/lilypond* (I'm trying to be safe), it seems
> to build ok. But if I try to rebuild with "make lilypon
rface::height #]
?: 15* [# #]
In :
5: 16* [+ 4 {#}]
:5:22: In procedure + in expression (+ 4
(system-start-text::calc-y-offset grob)):
:5:22: Wrong type: #
--
John Mandereau
signature.asc
Description: Ceci est une partie de message numériquement signée
_
Le mardi 11 août 2009 à 15:44 +0200, John Mandereau a écrit :
> It looks like a grob suicides in Documentation/snippets/incipit.ly, as I
> get the backtrace below when issuing 'make doc'. I suspect a check for
> SCM_UNSPECIFIED should be added either in the override in incipi
ally, if I call gs manually on the .eps files, I get no error :-/
Now I'm trying to do a clean build with latest changes on master.
Thanks in advance for hints
--
John Mandereau
signature.asc
Description: Ceci est une partie de message numériquement signée
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le mardi 11 août 2009 à 10:45 -0700, Mark Polesky a écrit :
> When grepping for pad-markup, two hits are from translated docs.
> Do I just silently modify them, or do I need to notify the
> translators?
Why don't you just convert-ly docs after having written the convert-ly
rule and compiled conver
Le mardi 11 août 2009 à 21:01 +0100, Neil Puttock a écrit :
> 2009/8/11 John Mandereau :
>
> > Why don't you just convert-ly docs after having written the convert-ly
> > rule and compiled convert-ly?
>
> Is this possible on Windows? (I've never tried it mysel
Le mardi 11 août 2009 à 21:01 -0700, Graham Percival a écrit :
> This changed the message, but the underlying problem is still
> there. I tried another "make lilypond", without deleting
> anything. (a few commits changed Documentation/general/ and css
> stuff, but nothing else happened on master)
Le mercredi 12 août 2009 à 17:27 -0700, Graham Percival a écrit :
> I was talking about @lilypond stuff, not snippets. i.e. if
> Documentation/fr/notation/rhythms.itely
> contains some old autobeaming stuff requring a NOT_SMART rule,
> what happens? We can't leave it alone, since that would bre
Le jeudi 13 août 2009 à 01:31 +0200, Jan Nieuwenhuizen a écrit :
> That's a nice way of putting it... I do like the new web site,
> but I'd feel bad if what we now have goes life, so I put in
> some effort to help this time ;-)
Very very cool! I left this a bit over as my LilyPond time is complt
Le mardi 11 août 2009 à 21:19 -0600, Carl Sorensen a écrit :
> And if makelsr.py hasn't been done, LilyPond will get the snippet from
> Documentation/snippets/new instead of Documentation/snippets.
This is wrong -- see LILYPOND_BOOK_INCLUDES in make/lilypond-vars.make
-- and not needed anyway: any
Le jeudi 13 août 2009 à 10:52 -0600, Carl Sorensen a écrit :
> I try not to look at any of the make files; it's hopeless for me to
> understand them.
I can understand, I used to be hopeless too. Don't waste your time
understanding them, as their timelife is now known to be very limited.
> Is th
Le jeudi 13 août 2009 à 09:56 -0700, Mark Polesky a écrit :
> c) change the English version and expect them to see the change
>on their own, or
If the changes are not spread across different files, translators will
notice them; this is the preferred option for changes in text in English
outsid
Le vendredi 14 août 2009 à 16:01 +0200, Jan Nieuwenhuizen a écrit :
> We have a problem using the --split=node --node-names that we use
> for the current web [general]: translated files get different
> names, ie for Introduction (nl: Inleiding)
>
> http://lilypond.org/~janneke/lilypond.org/In
Le samedi 15 août 2009 à 07:50 -0600, Carl Sorensen a écrit :
> I think that John Mandereau is working on the 2000 lines of python we would
> need to parse texinfo. We may be close to this in the next couple of
> months!
Well, I bet I can make the parser less than 1000 lines, including
Le samedi 15 août 2009 à 09:43 +0200, Jan Nieuwenhuizen a écrit :
> - And also, please go read the texi2html script and see if you
>come out alive on the other end. If I saw someone saying this
>was great, I might not even want to *see* their printed notation
>output?
I read it a few
Le lundi 17 août 2009 à 14:26 -0700, Graham Percival a écrit :
> Besides, if somebody's setting a list, they already have to know
> to remove the #' from the #'(1.0 -2.3) when putting it into
> scheme.
(1.0 -2.3) is not a list (it's a function call), but '(1.0 -2.3) and
(list 1.0 -2.3) are.
John
Le lundi 17 août 2009 à 21:31 -0700, Graham Percival a écrit :
> 1. I have jpg files in Documentation/pictures/out-www/, but they
> don't get copied to out-www/offline-root/Documentation/pictures/.
> All the pngs are copied, though.
Fixed (but untested).
> 2. We currently have filenames in the
Le mardi 18 août 2009 à 03:55 -0700, Graham Percival a écrit :
> If necessary we could use inkscape or rsvg, but I'd rather not
> increase the build requirements. (IIRC inkscape isn't required
> for master)
Inkscape is required by input/regression/backend-svg.ly, which had been
disabled when some
Hi guys,
2009/8/25 Graham Percival :
> More to the point, they shouldn't be created at all -- shouldn't
> they go in out/ ?
Of course they should. I'll look at this and all other issues with
the build system when I'm back in France this week-end.
Greetings from Pisa,
John
_
Hi Werner,
2009/8/26 Werner LEMBERG :
> Can someone please tell me the commands (lilypond and gs, I assume,
> with *all* options) to convert a LY file to PNG and to PDF, as used
> for the notation reference? The full set of options to lilypond isn't
> shown in the log file...
I hope you redirect
Le dimanche 30 août 2009 à 16:05 -0700, Patrick McCarty a écrit :
> Attached is a patch that modifies `make distclean' so that it behaves
> correctly.
>
> Okay to apply?
LGTM.
Sorry for my current absence in Lily development, but I'm busy with
setting up a joint supervision for my PhD.
Greetings
Le lundi 31 août 2009 à 10:16 +0200, John Mandereau a écrit :
> Le dimanche 30 août 2009 à 16:05 -0700, Patrick McCarty a écrit :
> > Attached is a patch that modifies `make distclean' so that it behaves
> > correctly.
> >
> > Okay to apply?
BTW please no longe
Le mercredi 02 septembre 2009 à 19:38 +0200, Francisco Vila a écrit :
> 2009/9/2 :
> > On Wed, Sep 2, 2009, Trevor Daniels said:
> >>> I've found that church modes are not translated
> >>> ... Ionian, Dorian etc ...
> >
> > No need to translate them from Latin/greek into vernacular;
>
> I could
Le dimanche 06 septembre 2009 à 09:30 +0200, Joseph Wakeling a écrit :
> I'm not sure how to interpret what's there -- presumably that only a
> subset of the intended output has been written to collated-files.pdf?
As Graham pointed out, you didn't paste the relevant part of the log,
but the error
Hi guys,
Le mardi 08 septembre 2009 à 10:13 +0100, Graham Percival a écrit :
> > > I propose to extend /VERSION to include:
> > > STABLE_VERSION
> > > DEVEL_VERSION
> - I'm asking if it's a good idea.
This would be yet another incarnation of caching data from another
branch in Git sources, so plea
Le samedi 05 septembre 2009 à 00:43 +0100, Graham Percival a écrit :
> 3) we might be switching to SCons "soon", so there's unfortunately
> little interest in tracking down the above problems. As always,
> patches appreciated if you're particularly curious about this
> issue.
I won't suppo
Le lundi 07 septembre 2009 à 16:42 -0700, Patrick McCarty a écrit :
> The part that (I think) is relevant to LilyPond is below:
>
> [...]
> The licensing of the Free version of the core Ghostscript code has
> been changed to GPLv3 or later. Previously, the core code was GPLv2
> only. Ghost
Le mardi 08 septembre 2009 à 12:30 +0200, Joseph Wakeling a écrit :
> [century_schoolbook_l_serif_3.0673828125]Segmentation fault (core
> dumped)
> command failed: /home/myusername/code/lily/out/bin/lilypond
What is the snippet that causes a segmentation fault?
> I note that texi2html is only 1
Le mardi 08 septembre 2009 à 12:46 +0200, Joseph Wakeling a écrit :
> It's trying to build BUILD-DIR/out/lybook-db/snippet-names--494188324.ly
> whose content is:
I meant, what is the exact snippet that fails? Does it still fail if
you compile it with the trick described in HACKING and with EPS b
Hi folks,
After a bit of private discussion with Jan and Graham, I've decided to
stop maintaining current build system (or rather the parts I used to
maintain), and we should switch to a build system that allows writing
build routines easier to maintain and understand. Jan proposed SCons
[0], and
Le mardi 08 septembre 2009 à 19:41 +0100, Graham Percival a écrit :
> While I feel incredibly guilty for speaking against any project
> that includes a link to XKCD, I really do not think this is the
> best project for us.
Neither do I.
> - is it portable? (quote: "there is no configure script,
Le mardi 08 septembre 2009 à 21:12 +0200, Werner LEMBERG a écrit :
> BTW, there is a `better make', written in Perl:
>
> http://makepp.sourceforge.net/
>
> According to this page, makepp `currently runs only on probably all
> Linux/Unix-variants and Windows, as well as Ebcdic platforms BS2000
>
Le mardi 08 septembre 2009 à 19:53 +0100, Graham Percival a écrit :
> For the record (as discussed in private email), I'm quite
> concerned about waf's relative new-ness and occasional lack of
> development. My preference would be to use a stable, widely used
> build system, since any problems in
Le mardi 08 septembre 2009 à 19:53 +0100, Graham Percival a écrit :
> The most important two factors, in my mind, are "how interested
> are you?" (very interested), and "will you have enough time to
> finish it?". I'm not so concerned about using waf for everything,
> but do you think you can get
Le jeudi 10 septembre 2009 à 00:24 +0200, Joseph Wakeling a écrit :
> But anyway, I'm willing to do the typing side of it. I just need you to
> clarify exactly what I should put: presumably GPLv2 for code files and
> GFDLv1.1 for docs are the base licenses, but would you and Jan approve
> putting
Hi Carl,
Le jeudi 10 septembre 2009 à 16:25 -0600, Carl Sorensen a écrit :
> I'd be willing to give a hand if I can. I read your wiki page, but didn't
> get anything from it in terms of how I could help. Give me a ping if you
> get to the point that you can carve out some kind of task for me to t
Le vendredi 11 septembre 2009 à 20:39 -0600, Carl Sorensen a écrit :
> I've successfully written the script so that it works on my setup, but where
> should I put configobj.py so that it will be available? And should I even
> try to go this way, or should I write my own parsing code?
You may put
Le samedi 12 septembre 2009 à 02:57 +0100, Graham Percival a écrit :
> Hmm. Could you / have you contacted the waf developers about
> making the version-checking function part of their main distro?
No, because I'm not familiar enough with Waf and my code isn't
stabilized enough, so I put my custo
Le samedi 12 septembre 2009 à 02:54 +0100, Graham Percival a écrit :
> It's a recognition that I royally screwed up over the summer in
> attempting too many big things at once. The new website, the doc
> rearrangment, and learning GUB. As a result, I failed to complete
> *any* of them during the
Le samedi 12 septembre 2009 à 06:28 -0600, Carl Sorensen a écrit :
> The source file for configobj.py has copyright information, a description of
> the license, and a link to the full license. Is that enough?
Yes, it is.
> I've pushed a wscript containing the code to
>
> (a) parse VERSION to o
Le samedi 12 septembre 2009 à 16:32 +0200, John Mandereau a écrit :
> It might be better to put it back to the beginning of the file. FWIW
> PACKAGE_NAME is used for the tarball name, so we might want to .lower()
> it.
BTW we must pay attention to the fact that conf.env['top-bui
Le dimanche 13 septembre 2009 à 06:45 -0600, Carl Sorensen a écrit :
> 80 characters maximum; I generally try to keep the lines about 70
> characters.
FWIW in Python code it's often hard to keep lines below 80 characters,
so I try to keep them around 80 characters and require them to be less
than
Le dimanche 13 septembre 2009 à 09:44 +0100, Graham Percival a écrit :
> > Is lilypond-book affected by the macro expansions?
>
> I assumed it was, but perhaps not.
>
> Here, let's do a quick test. Add an @afourpaper to one of the
> manuals, but not the others. Wait a day, then see how they bo
Hi Jan,
In my current attempt to build LilyPond with GUB, I hit a name clash in
netpbm, patch attached. I hate languages without namespaces or
equivalent concept :-)
Best,
John
From 030efb393486e5717e74dc91b9b145020ab7b014 Mon Sep 17 00:00:00 2001
From: John Mandereau
Date: Sun, 13 Sep 2009 16
Le lundi 14 septembre 2009 à 12:37 -0400, Kieren MacMillan a écrit :
> 3. Programming. In order to get this done before, say, 2020, we'll
> need at least one lead developer with good Scheme-fu to (1) write
> most of the heavy-lifting code, and/or (2) vet my/our Froggie work.
> In either case
Le mercredi 16 septembre 2009 à 06:04 +0100, Graham Percival a écrit :
> Ok. I'm just worried about re-creating the stepmake mess, where
> Han-Wen and Jan spent a lot of time creating it, but never got it
> merged upstream. As a result, it's become an evolutionary dead
> end.
This can hardly be
Le mercredi 16 septembre 2009 à 07:12 +0100, Graham Percival a écrit :
> Building general.texi is enabled by default.
We might misunderstand each other. The online target is made of all
docs built in a way to be put on a web site with automatic language
selection, whereas the offline target is f
Le vendredi 18 septembre 2009 à 18:26 +0100, Graham Percival a écrit :
> 2) lilypond-doc doesn't use multiple CPUs. I was pleasantly
> surprised to find that the general compiling commands (for both
> lilypond and non-lilypond) used -j4, but the "make doc" doesn't
> appear to do this. I spent
Le samedi 19 septembre 2009 à 07:30 +0100, Graham Percival a écrit :
> But we *don't* have "a licensing situation" on a file-by-file
> basis. Everything[1] under Documentation/ is FDL; everything
> else[2] is GPLv2.
>
> [1] it would be very useful if somebody could create an example to
> replac
Le vendredi 18 septembre 2009 à 06:56 +0100, Graham Percival a écrit :
> Some time later today (knock on wood) I'll make the official
> 2.13.4 release. This will happen whenever I manage to solve or
> bludgeon all the issues involved in building GUB on my university
> machine. As such,
> - I'm n
Le samedi 19 septembre 2009 à 19:45 +0100, Anthony W. Youngman a
écrit :
> The snippets are not public domain, unless the author put them there.
> The *music* may be public domain, but the *arrangement* is copyright
> whoever wrote the lilypond code (unless you make the argument that the
> snip
Le samedi 19 septembre 2009 à 18:34 +0100, Graham Percival a écrit :
> I'd rather not keep track of individual licenses in the source
> tree. Since he's stated that his work is in public domain,
> there'd be no problems with people extracting it for any CC stuff.
> ... err wait, are we talking ab
Le samedi 19 septembre 2009 à 21:50 +0100, Neil Puttock a écrit :
> If it's not too much trouble for you to do this, John, I'd be
> interested to know whether you can get it too work; I've been trying
> without success over the last few weeks to do comparisons between
> various 2.12 & 2.13 release
Le lundi 21 septembre 2009 à 23:54 +0100, Trevor Daniels a écrit :
> Has the version of texinfo you are using changed? I use texi2html,
> admittedly a very old version, for my local doc compiles and don't
> see this problem.
Remember that the accepted Texinfo language depends on the Texinfo
proc
Le lundi 21 septembre 2009 à 09:12 +0100, Graham Percival a écrit :
> then debug. Currently it's not finding version.itexi in
> Documentation/out-www/ ... it gets built in Documentation/out/.
I couldn't reproduce this error, but I hit a truckload of broken image
paths, and hopefully fixed them.
Le samedi 19 septembre 2009 à 22:26 +0100, Neil Puttock a écrit :
> I don't know whether it's significant, but I've found it's easy to
> tell when the testing's gone wrong, since the job forking message has
> too few jobs (on a good day, it usually averages around 20,000 per job
> for -j3 on my sy
Le mercredi 23 septembre 2009 à 11:50 +0100, Graham Percival a écrit :
> I can work-around the problem by adding --always to the git describe
> command-line, but then we end up with tags like this:
> git tag -m "release of lilypond
> 834700852f25a6ade4a2f8efe2b13bc71278d3a (2.13.4-0)"
> "gub-rel
Le mercredi 23 septembre 2009 à 19:52 +0100, Graham Percival a écrit :
> GUB uses shallow clones, presumably to decrease the bandwidth
> requirement? I don't know, but I'd rather not start messing with
> stuff that currently works.
For source code other than the project that is being packaged, s
Le mercredi 23 septembre 2009 à 21:02 +0100, Neil Puttock a écrit :
> It looks like there's no forced regeneration of the musicxml snippets:
> on my system, unless I do `make test-clean' first, they all have the
> wrong \version (i.e., 2.13.4), which causes `make test-baseline' to
> fail on the fi
Le mercredi 16 septembre 2009 à 19:53 +0200, Jean-Charles Malahieude a
écrit :
> Checking for LilyPond binary : not found, trying standard check
> Checking for program lilypond: ok /home/jcharles/bin/lilypond
Patrick McCarty wrote:
> Checking for LilyPond binary:
Le vendredi 25 septembre 2009 à 23:59 +0100, Neil Puttock a écrit :
> LGTM, though I'd appreciate it if somebody else could give the patch a
> final look (especially the lilypond-book changes, since I'm not that
> familiar with it).
Sure, see below.
> --- a/scripts/lilypond-book.py
> +++ b/scrip
Le dimanche 27 septembre 2009 à 17:37 +0100, Graham Percival a écrit :
> How much of scheme do we get into, though? I mean, what about
> moving it back into Notation?
This would be wrong: even if we expanded it up to make a big chapter, it
would not become reference documentation (we alreadhy hav
Le dimanche 27 septembre 2009 à 13:57 +0100, Graham Percival a écrit :
> What do people think about the doc reorg shown in:
> http://kainhofer.com/~lilypond/Documentation/general/Manuals.html
> (and the actual manual pages, of course)
I think the frame "Read it now" is superfluous, a simple link "
Le dimanche 27 septembre 2009 à 19:08 +0100, Graham Percival a écrit :
> I'm wondering if we can call them "Function index" and "Concept
> index". Or something like that. It just seems weird to have a
> "LilyPond index" for every manual.
Maybe "Function and concept index", as this index actually
Le dimanche 04 octobre 2009 à 14:06 +0100, Graham Percival a écrit :
> Sorry, that would involve too much suckage and conditionals in the
> source file, or macros calling other macros. I agree it's not
> ideal, but it's better than the alternative.
What about naming the frame "All formats" instea
Le mardi 13 octobre 2009 à 18:44 +0100, Graham Percival a écrit :
> Are you looking in Documentation/out-www/, or
> out-www/offline-root/Documentation/ ?
>
> IIRC, the former has had broken images for a while, but they get
> fixed when copying/linking them into the toplevel
> out-www/offline-root/
Le dimanche 18 octobre 2009 à 21:22 +0100, Graham Percival a écrit :
> I don't have a clue. If I type "make doc" in Documentation/, then
> I look in Documentation/out-www/. If I type "make doc" in /, then
> I look in out-www/, and keep on looking in subdirectories until I
> see something that loo
Hi Martin,
I reviewed your changed version on midi2ly with inclusion in official
sources in mind, the patch that match your work (minus trailing
whitespaces and indentation errors). If you want your future work on
midi2ly to be considered for committing into official sources, it is
highly recomme
Le samedi 24 octobre 2009 à 17:13 +, codesite-nore...@google.com a
écrit :
> We don't *have* to discuss it as a tracker issue,
Especially when it's not necessary, as Google Code sends text emails
with horrible indentation, or rather I'm not able to fill Google Code
tracker form in a way to avo
Le lundi 26 octobre 2009 à 12:38 +0100, John Mandereau a écrit :
> Moving HTML output of General one directory up
For completeness, let's keep in mind that this structure won't work for
online docs, because HTTP content negotiation would cause a conflict in
between "manual.html
Hi guys,
I forgot to reply to -devel too, so I include at least all of Graham's
reply.
Le mardi 03 novembre 2009 à 19:21 +, Graham Percival a écrit :
> On Fri, Oct 30, 2009 at 07:18:50PM +0100, John Mandereau wrote:
> > The problem is, we might end up creating many issu
Le mercredi 04 novembre 2009 à 00:11 +, Graham Percival a écrit :
> Sure! At the time, I thought you were completely engrossed in
> sorting out your move, and I didn't want to bother you.
I'm engrossed with many other things, but never mind: I still don't have
time to work on the translations
Le mercredi 04 novembre 2009 à 09:23 +0100, Jan Nieuwenhuizen a écrit :
> Op dinsdag 03-11-2009 om 19:21 uur [tijdzone +], schreef Graham
> Percival:
> > On Fri, Oct 30, 2009 at 07:18:50PM +0100, John Mandereau wrote:
> > > I agree with this, but I will not responsib
Le jeudi 05 novembre 2009 à 18:28 +, Graham Percival a écrit :
> Is that a firm rule, or just a suggestion?
Node names are used like titles in Info, so unless if there's a good
reason (e.g. the node name is a program name), it should start with a
capital, shouldn't it?
> Sure we can, with sy
Le jeudi 05 novembre 2009 à 00:30 +, Graham Percival a écrit :
> It seems to work. I had to change all the @ref{} in the text, but
> it looks fine now.
Barring well-argumented opposition, I'm going to revert this and apply
the patch below, as completely downcasing titles — node names are some
Le vendredi 06 novembre 2009 à 19:43 +, Graham Percival a écrit :
> On Fri, Nov 06, 2009 at 08:14:27PM +0100, John Mandereau wrote:
> > I warmly, highly and definitely second doc/v2.xx (first value of xx will
> > be 14), which is clearer than having stable docs at topl
Le jeudi 05 novembre 2009 à 22:40 +, Graham Percival a écrit :
> oh, FFS. Your solution is so ridiculously easy.
> (yes, please revert the lower-case patches from Jan and me, and
> use yours)
On theory, my solution is good, but in practice my patch miserably
fails. In most situations where I
Le samedi 07 novembre 2009 à 19:26 +, Graham Percival a écrit :
> I've got waf buliding contributor .html and .pdf in the dev/gperciva
> branch.
Ah, you got upset enough by the old build system too :-)
> I was pleasantly surprised to discover that waf supported a
> --targets= command-line,
Le mardi 10 novembre 2009 à 00:36 +, Graham Percival a écrit :
> I'm mostly just pissed about the "blddir" stupidness. It's not
> the 1970s, folks! Adding the "ui" won't cause the source file to
> be too large for the punch card! Besides, one of python's claims
> to fame is that it's more re
Le samedi 07 novembre 2009 à 19:26 +, Graham Percival a écrit :
> I've got waf buliding contributor .html and .pdf in the dev/gperciva
> branch. I was pleasantly surprised to discover that waf supported a
> --targets= command-line, so we can specific an individual manual to
> build. I'm les
Le mardi 10 novembre 2009 à 23:34 +, Graham Percival a écrit :
> The basic problem is that waf doesn't like to have directories in the
> build tree that aren't present in the source tree. After asking for
> help, the main author pointed out a not-really-documented function
> that allowed me to
Le mercredi 11 novembre 2009 à 23:07 +, Graham Percival a écrit :
> Given that most of our users are on windows, I defined
> "portability" as "it will run on operating system X with Y extra
> software installed", where X should be large and Y should be
> small.
Then SCons and Waf are reasonabl
Le mercredi 11 novembre 2009 à 23:36 +, Graham Percival a écrit :
> Hmm. I don't completely follow, but does this explain why waf
> always succeeds on the second attempt? If not, it might be
> something weirder... but then again, if you're following it up on
> the waf-user list, then it's no
Hi Kieren,
Le mercredi 11 novembre 2009 à 19:05 -0500, Kieren MacMillan a écrit :
> I'm trying to get a local build system in place (in order to edit the
> docs), and can't seem to get past some install errors — specifically
>
> sudo port install tetex
I don't have a Mac and I have never us
Le jeudi 12 novembre 2009 à 00:21 +0100, John Mandereau a écrit :
> Does the attached patch convince you to go on on Waf?
Actually, please ignore my patch and checkout a SVN copy of Waf instead
svn checkout http://waf.googlecode.com/svn/trunk/ && mv trunk waf
then invoke waf-ligh
Le mercredi 11 novembre 2009 à 23:33 -0500, Kieren MacMillan a écrit :
> out/dispatcher.dep:1: *** multiple target patterns. Stop.
> make: *** [all] Error 2
Which Make avatar and version do you use?
Best,
John
signature.asc
Description: Ceci est une partie de message numériquement signée
_
Le jeudi 12 novembre 2009 à 09:12 -0500, Kieren MacMillan a écrit :
> I don't know what a make "avatar" is...
I meant an implementation of Make. AFAIK building LilyPond requires GNU
Make.
> but when I type
>
> make --v
>
> it outputs
>
> GNU Make 3.80
> Copyright (C) 2002 Free
Le jeudi 12 novembre 2009 à 09:40 -0500, Kieren MacMillan a écrit :
> You're kidding, right?
> A 0.01 version difference is stopping me from being able to turn my
> [huge, but quickly waning] enthusiasm for Lilypond into useable and
> useful docs and bugfixes??
Yesterday, I spent hours debuggi
Le lundi 09 novembre 2009 à 20:08 +, Graham Percival a écrit :
> doing:
> $filename = lc($filename)
> works fine in the general lilypond-init.pl file.
In wich line or function exactly? The changes I proposed in a previous
email don't work for me, even not for manuals. In case it matters, I
Le jeudi 12 novembre 2009 à 01:29 +, Graham Percival a écrit :
> I like the changes to the @uref{} links, but we should be able to
> make all the html filenames lower-case by changing 2 or 3 lines in
> the texi2html-init file. I'm still not certain whether makeinfo /
> info is happy with lower
Le dimanche 15 novembre 2009 à 23:12 +0100, Frédéric Bron a écrit :
> did not know that (not in CG): I did the sudo apt-get build-dep
> lilypond. I have already tex2thml 1.82 (installed manually).
> redone git pull, make clean, make all, make doc.
You forgot "make doc-clean" in this sequence; in t
Le vendredi 20 novembre 2009 à 14:56 +, Graham Percival a écrit :
> 1) cd Documentation; make doc
> 2) go cook dinner or read slashdot or catch up on emails or
> whatever
> 3) if it fails, complain on -devel. If it succeedes, then commit
> the changes you want to test.
> 4) touch Documenta
Le jeudi 12 novembre 2009 à 18:09 +, Graham Percival a écrit :
> Lines 360, 381, 384. Documentation/lilypond-texi2html.init
> Works for contributor; I didn't bother checking the others. From
> a clean source tree.
Ah, thanks, my too limited understanding of the init file made me
downcase on
Le lundi 23 novembre 2009 à 18:03 +, Trevor Daniels a écrit :
> Having just installed ubuntu, a new git repo and compiled Lily and
> the docs for the first time I see that all the entries in out-www
> appear as unstaged changes in git.
>
> Should not out-www be included in .gitignore or am I
Le samedi 21 novembre 2009 à 19:17 +, Graham Percival a écrit :
> Hmm. Now I'm wondering if I had a half-built doc tree, with the
> remains of Jan's "@node lower-case" stuff. I cleared out
> Docuemtnation/out-www/, but I didn't think to touch out/xref-maps.
I hope it's not needed to touch t
Sorry for the delay, it often takes me a while to catch all traffic on
Lily lists when I'm back from a trip, even a few-days one.
Le jeudi 12 novembre 2009 à 17:54 +, Graham Percival a écrit :
> 1) if you can't duplicate the problem after checking out
> dev/gperciva, then I'll check a third t
Hi Carl,
Le mardi 24 novembre 2009 à 14:15 -0700, Carl Sorensen a écrit :
> I've done a git grep for ukelele, and found the misspelling existing in de/
> es/ and fr/ notation/fretted-strings.itely. I'm happy to fix it in all of
> those, and I think I should do so.
Certainly.
> I have read the C
Le mardi 24 novembre 2009 à 21:20 +, Graham Percival a écrit :
> On the 16th, I gave up and fixed this one myself. However, I
> discovered that I couldn't copy files from srcdir into the blddir
> without changing their name, which kind-of borks
> Documentation/pictures/.
I'm quite certain we
301 - 400 of 1573 matches
Mail list logo
