Graham Percival [Sun, 19 Sep 2010 15:37:17 +0000 (16:37 +0100)]
LSR: escape double backslashes.
4+4+10 backslashes on one line to do this?! How the bloody mao
can people (including myself) still refer to python as a "highly
readable language" ?
Also, I'm appalled at the state of makelsr.py. A few years ago it
was a nice and simple script; now it's a confusing mess of regex,
some stuff in functions, some stuff in global, etc. It took me
over an hour to add the "escape double backslahes" to this script.
Granted, I'm an idiot without previous experience with regex...
but hey, I'm the only person to work on this bug in the over 3
years. I think our python+build scripts need to be written with
idiots in mind, because smart people are too busy doing other
stuff.
James Lowe [Sat, 18 Sep 2010 09:10:49 +0000 (10:10 +0100)]
Doc: Tracker 1241 - Second Patch
Replaced Tec accented chars with UTF-8 ones.
Also made the space for each @[section] similar in essence to
@lilypond examples. There is nothing in CG about .bib file layout.
Also corrected some missed spacing edits from the previous patch.
James Lowe [Fri, 17 Sep 2010 14:28:38 +0000 (15:28 +0100)]
Doc: Tracker 1241 - First Patch
Replaced Tex accented chars with UTF-8 ones.
Also made the spacing for each @Book @TechReport @MastersThesis etc similar
in essence to @lilypond examples as there is nothing in the CG about spacing
or indentation. So I used some common sense and applied some consistency
throughout. There may still need be some more consistency applied (i.e. set
and explicit order of each entry (author, index, year, pages etc.).
Graham Percival [Tue, 14 Sep 2010 18:23:48 +0000 (19:23 +0100)]
Doc: move snap pizz into main text (fixes 1261)
Translator note: I left the actual snippet in git so that your
manuals would still compile, but you might want to make this
change in your manuals in case we want to remove the snippet later on.
Neil Puttock [Sun, 12 Sep 2010 20:49:11 +0000 (21:49 +0100)]
Fix #1258.
* lily/stem-engraver.cc (make_stem):
robustify property lookup for tremolo-type (ensures compilation can
continue even if there is an error inside make-repeat which prevents
correct calculation)
* scm/music-functions.scm (make-repeat):
don't filter out child music which uses the 'element property
Lilypond-book: Fix problem with os.path.abspath in Windows
The check whether input file == output file needs to use the absolute
path to the input file, since the CWD has changed meanwhile (and is
the output dir at that point). Unfortunately, we can't call os.path.abspath
right at the beginning and use the abspath for all of the processing,
because os.path.abspath will replace forward slashes by backslashes
in Windows (the path is normalized!). That path with backslashes
are then printed to the snippet map files and cause l-p to fail with
wrongly escaped characters...
As a solution, use the relative pathname of the input file for all
processing, but also store the abspath for that one particular
infile==outfile check.
Graham Percival [Mon, 6 Sep 2010 13:56:56 +0000 (14:56 +0100)]
Clarify infinity_f preprocessor definition.
The old code confuses various style programs, including our own
fixcc.py (it produces un-compilable code!). In particular:
-----
const Real infinity_f
= #ifdef
-----
which makes gcc unhapy.
The new format is easy for style programs to deal with, still
compiles, and is IMO just as clear anyway.
Graham Percival [Sun, 5 Sep 2010 13:04:08 +0000 (14:04 +0100)]
Typo fixes: backslash, join one set of comments.
The backslash was doing nothing. Nick said this was ok.
It's confusing having two of those almost-identical comments
indented, and two non-indented. They all fit within 80 chars.
Relax; I'm not going to go on a stylistic editing spree right
before 2.14. These are (I think) the only changes I'll be making
on master without more discussion.
Graham Percival [Fri, 20 Aug 2010 12:39:13 +0000 (13:39 +0100)]
Build: fix 775 configure should detect doc reqs.
It's a trivial patch, but I feel a bit sheepish proposing any
changes to the build system after making such a big deal about a
"build system freeze" back in June and July. :|