John Mandereau [Mon, 4 Jan 2010 01:03:09 +0000 (02:03 +0100)]
Web: tune second navigation bar and complete i18n
- rename search-box.html to search-box.ihtml;
- i18n the search box and hosting thanks footer line;
- replace hard-coded section node names with hard-coded chapter file
name prefixes and numeric arrays, fixing the CSS class of second
navigation bar in translations;
- replace "(main)" with chapter name in the second navigation bar.
Graham Percival [Sun, 3 Jan 2010 04:39:06 +0000 (04:39 +0000)]
Web: remove comment-based bug reports.
Guys, don't use comments to discuss problems in the website.
Email lilypond-devel or add an issue in the tracker. We spent a
lot of time trying to stop this practice during GDP.
I don't care if you want to have discussions via source code
comments for programming issues (although I it's a stupid way to
communicate), but keep this garbage out of the texinfo files.
Patrick McCarty [Thu, 31 Dec 2009 23:27:09 +0000 (15:27 -0800)]
Pango: concatenate multiple PangoLayoutLines.
If single-line markup contains newlines (either UNIX or DOS style), we
still want the markup to be printed on a single line.
Since text assigned to a PangoLayout is split, if necessary, into
multiple PangoLayoutLine objects, we simply want to concatenate them
into a single line.
Carl Sorensen [Wed, 30 Dec 2009 02:45:02 +0000 (19:45 -0700)]
Doc: Contributor/Programming add email comments
Han-Wen gave some answers about LiliyPond architecture
in an email on -devel. These answers are added to the CG in a
miscellaneous section of Programming
Look folks, don't screw with the texinfo macros unless you really,
really test it before pushing. These things are stupidly finicky
at the best of times. Also, take it step by step. Don't change a
whole bunch of things at once, because when (not if) it breaks
it's much harder to figure out how to fix it.
John Mandereau [Tue, 29 Dec 2009 22:43:30 +0000 (23:43 +0100)]
Web: nitpicks in Intro & Manuals, mostly typography and spelling
- Internals in PDF and Info formats also have clickable links,
- remove redundant copyright notice (alreaady defined in macros),
- replace '...' with @dots{},
- two spaces after the end of a sentence,
- comments for translators,
- spelling mistakes,
- a couple of wrong xref macros,
- last xml2ly is seven years old and outputs for Lily 1.x,
- a few other nits.
This is mainly intended to make regression tests output filenames more
stable against changes of their contents and changes in lilypond-book,
and could also make generated snippets reuse a little easier (as it
makes output filenames controllable and predictable by the user).
This doesn't break the hashing system that saves lilypond processing
time.
See complete discussion at
http://lists.gnu.org/archive/html/lilypond-devel/2009-12/msg00636.html
Graham Percival [Mon, 28 Dec 2009 21:41:53 +0000 (21:41 +0000)]
Web build: make better links for stable.
I shouldn't be allowed to use anything other than lily-git; I lost
this work from my local git repo when I was trying to fix it from
briefly going back to 2.12.2. Fortunately I'd already uploaded it
into lilypond.org:lilypond/trusted-scripts, so I could restore
from that backup.
John Mandereau [Mon, 28 Dec 2009 20:51:25 +0000 (21:51 +0100)]
Remove non-POSIX grep option "--label"
This reverts commit d4401de33195113a8859629b4bd9483a03d9ab5c.
This option was not really useful anyway, as an empty output of
"find $(outdir) -name '*.html'" is the sign of a build error.
Use different types of events for cueDuring and quoteDuring
Typically, \quoteDuring is supposed to duplicate everything in a voice,
while \cueDuring is supposed to only quote the notes, but not e.g.
phrasing, slurs, accents, markup, etc.
So, this commit adds an additional property quotedCueEventTypes in
addition to quotedEventTypes, which allows to quote different types
for \cueDuring than for \quoteDuring.
By default, \quoteDuring now quotes everything (i.e. StreamEvent), while
\cueDuring quotes only notes, rest, ties, beams and tuplets.
Also document the difference between cue/quoteDuring and how to
selected the quoted event types
Matthias Kilian [Sun, 27 Dec 2009 15:53:20 +0000 (16:53 +0100)]
Always use $(PYTHON) scriptname.py.
The often-used idiom #!/usr/bin/env python not only is potentially
dangerous, but it also fails if there are several versions of python
installed, with the python binaries named python2.4, python2.5,
python2.6, ...
This patch hopefully catches all remaining cases of a missing $(PYTHON).
This reverts commit c731b754b33ee68a06f475193f9f8db2b1f76ae9. The
changes I'm reverting were introduced because some translated Texinfo
documents (namely website drafts) missed a @documentlanguage, causing
extract_texi_filenames to mess up xref-map files.
Joe Neeman [Sun, 27 Dec 2009 00:18:00 +0000 (11:18 +1100)]
Fix 916.
Handle the case where a loose line is marked as breakable. Previously,
the unbroken version of the last column was included as a loose line,
which broke System::broken_col_range.
projects / lilypond.git / log