When I try:
make -f lilypond.make unlocked-test-export
(either manually, or as part of make lilypond), the build often
ends with an error message:
uploads/lilypond-2.13.4-HEAD.test-output.tar.bz2
Traceback (most recent call last):
File test-lily/rsync-test.py, line 200, in module
main
Mark Polesky wrote Friday, July 10, 2009 8:51 PM
I was having trouble finding glyphs in NR B.6, so I reorganized
things. I'm not saying I used the best approach, but I think this
would be an improvement. Any comments or suggestions? A better
approach? See the attached file.
Thanks.
- Mark
On vr, 2009-07-10 at 16:14 -0700, Graham Percival wrote:
On Sat, Jul 11, 2009 at 12:42:09AM +0200, John Mandereau wrote:
2009/7/10 Graham Percival gra...@percival-music.ca:
So... do we launch a shiny new 2.14 release with the old sucky
website, resulting in more users sending confused
On za, 2009-07-11 at 00:16 -0700, Graham Percival wrote:
The file: uploads/lilypond-2.13.4-HEAD.test-output.tar.bz2
clearly doesn't match the m = re.search (... line. What I can't
understand is *why* the script is searching for such a string...
or alternately, *why* does GUB give the test
Here's my proposal for doc rearrangement from a doc writer's
perspective.
( - minus, + plus )
LM
- background essay
- about the docs(nobody reads it there, anyway)
+ expand 2.1.1 Compiling a file into:
+ LM 1.1 Compiling with LilyPond and LilyPad
+ LM 1.2 Alternate editors
- (possibly)
Here's my proposal for the source/makefile view of documentation.
(this is the big argument one)
My understanding is that linking between texinfo manuals is easier
if the main files are in the same directory. With that in mind, I
propose:
docs/
docs/learning.tely
docs/learning/*.itely
Graham
In general, this looks good. More below ...
Trevor
- Original Message -
From: Graham Percival gra...@percival-music.ca
To: lilypond-devel@gnu.org
Sent: Saturday, July 11, 2009 11:14 AM
Subject: proposal for doc rearrangement
Here's my proposal for doc rearrangement from a
What does one do when a snippet that is in the docs becomes obsolete?
The docs tag can be removed from the LSR.
The snippet reference can be removed from the English .itely file.
Does one then go and remove the snippet reference from the translated .itely
files as well?
Thanks,
Carl
Jan Nieuwenhuizen wrote:
However, I very much argued in favour of bazaar, for the very
reasons you cite. The bazaar project has as usability, ease of
use and good documentation as a prime goal -- and also does
very well in these areas -- much unlike git. Although git has
improved a bit here
On 7/10/09 6:38 PM, John Mandereau john.mander...@gmail.com wrote:
2009/7/11 Graham Percival gra...@percival-music.ca:
Similiar stuff has happened to me, but since it involves the build
process, I never bothered trying to track down the problem. I
just do a make clean, make web-clean
On vr, 2009-07-10 at 03:17 -0700, Graham Percival wrote:
I tried adding an SCons build system for the website, but I'm not
at all impressed by the result after an hour. But if we *do*
switch to SCons or waf or cmake (hopefully not) or whatever, I'll
learn that new system.
Have a look at
Carl Sorensen wrote:
@subsection Shaped Notes
@lilypond
\include font-table.ly
#(display-font-table 'shape-notes)
@end lilypond
@subsection Ancient Notes
@lilypond
\include font-table.ly
#(display-font-table 'ancient-notes)
@end lilypond
I just discovered a neat trick, but I
When we transitioned from gub2 to gub3, the build numbers on the
installers, and all manner of documentation tarballs got broken: the
.py scripts inserted the build number implying that I have to connect
to lilypond.org from brazil for every build I did. I kludged up a fix
to have the gub scripts
On Fri, Jul 10, 2009 at 8:14 PM, Graham
Percivalgra...@percival-music.ca wrote:
Here's my thoughts:
- probably 95% of our users read English well.
- the new website is way better than the old website. Not so much
for downloading, but the Introduction, Documentation, and
Community pages
(moved from -user)
Jonathan Wilkes wrote:
1.1 Background
6th paragraph
so nitpicking about typographical details may seem academical.
to
so nitpicking typographical details may seem academic.
It's not as verbose as the example given on the website for
changes to documentation. But is
On Fri, Jul 10, 2009 at 8:14 PM, Graham
Percivalgra...@percival-music.ca wrote:
Basically, my misadventures on Wed night / Thurs day (the essay
stuff, not getting much done in SCons, and accidently losing an
hour's worth of stuff in git) left me really dispirited and
disinterested in any
On Sat, Jul 11, 2009 at 04:36:25PM -0300, Han-Wen Nienhuys wrote:
On Fri, Jul 10, 2009 at 8:14 PM, Graham
Percivalgra...@percival-music.ca wrote:
Basically, my misadventures on Wed night / Thurs day (the essay
stuff, not getting much done in SCons, and accidently losing an
hour's worth
On 7/11/09 12:29 PM, Mark Polesky markpole...@yahoo.com wrote:
Carl Sorensen wrote:
@subsection Shaped Notes
@lilypond
\include font-table.ly
#(display-font-table 'shape-notes)
@end lilypond
@subsection Ancient Notes
@lilypond
\include font-table.ly
#(display-font-table
On 7/11/09 4:21 AM, Graham Percival gra...@percival-music.ca wrote:
Here's my proposal for the source/makefile view of documentation.
(this is the big argument one)
In general, I think these proposals are reasonable.
My understanding is that linking between texinfo manuals is easier
On Fri, Jul 10, 2009 at 5:19 PM, Carl Sorensenc_soren...@byu.edu wrote:
On 7/10/09 5:52 PM, Patrick McCarty pnor...@gmail.com wrote:
This is what I do (on Linux):
1.) Move all of the LilyPond fonts (aybabtu, etc.) and the Century
Schoolbook fonts to ~/.fonts
2.) Run fc-cache -fv
3.) Open
On 7/11/09 3:08 PM, Patrick McCarty pnor...@gmail.com wrote:
On Fri, Jul 10, 2009 at 5:19 PM, Carl Sorensenc_soren...@byu.edu wrote:
On 7/10/09 5:52 PM, Patrick McCarty pnor...@gmail.com wrote:
This is what I do (on Linux):
1.) Move all of the LilyPond fonts (aybabtu, etc.) and the
On Sat, Jul 11, 2009 at 2:10 PM, Carl Sorensenc_soren...@byu.edu wrote:
On 7/11/09 3:08 PM, Patrick McCarty pnor...@gmail.com wrote:
On Fri, Jul 10, 2009 at 5:19 PM, Carl Sorensenc_soren...@byu.edu wrote:
On 7/10/09 5:52 PM, Patrick McCarty pnor...@gmail.com wrote:
This is what I do (on
OK, so I'm making syntax changes in autobeaming for LilyPond.
I've worked through rhythms.itely and input/lsr (and I'll soon work through
input/regression).
Now my make doc is failing because of snippets in /de/user/rhythms.itely
that use the old syntax and have, in many cases, been removed from
Okay, here's a patch. Can someone test this?
Thanks.
- Mark
0001-Docs-NR-B.6-The-Feta-Font-Organize-glyph-list.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
At *long* last I have completed my changes to the autobeaming rules.
The rietveld patch set is available at:
http://codereview.appspot.com/88155
The objective is to get all information that affects autobeaming in a single
place, so a single override will adjust the autobeam settings.
Autobeam
Carl Sorensen wrote:
At *long* last I have completed my changes to the autobeaming rules.
The rietveld patch set is available at:
http://codereview.appspot.com/88155
The objective is to get all information that affects autobeaming in a single
place, so a single override will adjust the
Carl Sorensen wrote:
As much as I like the lsr, I don't like having documentation depend on the
lsr. I shouldn't have to put snippets in the lsr in order to get them in
the documentation, or else I should have a much easier way of getting them
into the lsr.
Would it be easier to email
Carl Sorensen wrote:
At *long* last I have completed my changes to the autobeaming rules.
The rietveld patch set is available at:
http://codereview.appspot.com/88155
The objective is to get all information that affects autobeaming in a single
place, so a single override will adjust the
2009/7/11 Neil Puttock n.putt...@gmail.com:
How about using a `try' block to import conditionally?
Thanks for the suggestion. Here is an updated patch, in case peope
want to have this (otherwise please ignore).
Cheers,
Max
From 5066717052db35b69af549e1189a88090e12fb78 Mon Sep 17 00:00:00 2001
On Sat, Jul 11, 2009 at 03:36:04PM -0700, Mark Polesky wrote:
Okay, here's a patch. Can someone test this?
Mark,
I just compiled the docs, and it looks great!
I believe Francisco brought this a while back, but we should rename
this appendix to The Emmentaler font, since that is its current
On 7/11/09 6:07 PM, Jonathan Kulp jonlancek...@gmail.com wrote:
Carl Sorensen wrote:
At *long* last I have completed my changes to the autobeaming rules.
The rietveld patch set is available at:
http://codereview.appspot.com/88155
The objective is to get all information that
On Fri, 2009-07-10 at 19:21 -0600, Andrew Hawryluk wrote:
On Fri, Jul 10, 2009 at 9:09 AM, Reinhold
Kainhoferreinh...@kainhofer.com wrote:
Am Montag, 22. Juni 2009 15:31:14 schrieb Joe Neeman:
A quick update on the new vertical spacing: [...]
Anything I've missed?
While the new
32 matches
Mail list logo
