Alexander Kobel [Fri, 22 Jan 2010 02:34:14 +0000 (18:34 -0800)]
Fix X-translation of \fill-line markup.
fill-line currently only considers the extents of the stencils, not
their position relative to the X-origin; with the patch, they are
shifted according to the first stencil argument.
John Mandereau [Thu, 21 Jan 2010 18:43:53 +0000 (19:43 +0100)]
Update translation instructions in the Contribuotrs' Guide
- remove explanation for converting old translations that didn't use
@translationof, as there are probably no longer such docs around;
- really explain committishes stuff;
- remove last traces of the old Documentation index in HTML and the
switch to the new website in Texinfo;
- link to new CG sectiosn about Git usage;
- explicitly tell translators the freedom they may want to take w.r.t.
partial translation of a file or taking distance from the text in
English, using Community section of the website as an example.
Graham Percival [Wed, 20 Jan 2010 21:45:20 +0000 (21:45 +0000)]
Usage: add stub for info about shared \includes.
This is aimed at non-lilypond-distributed projects, such as
Dr. Chubb's articulate.ly (better MIDI sound). Ideally we'd have
nothing in this section (because anything useful would be merged
with lilypond, possibly about being cleaned up a bit), but adding
info here is a useful stepping stone.
Graham Percival [Wed, 20 Jan 2010 21:29:09 +0000 (21:29 +0000)]
Doc: new chapter "External programs" in Usage.
This consists of the old "Converting from other formats" chapter,
plus the "Point and click" and "Text editor support" from the
Running lilypond chapter; all of these kind-of stuck out
awkwardly.
No nodes were harmed (renamed) in the making of this patch so far.
"Running lilypond-book"'s "Alternate methods..." has been moved
into External programs, with the new name of "LilyPond output in
other programs". The old name still exists for ease of TOC and
whatnot, but anybody referring to it might want to change to the
new name to avoid a relatively pointless redirect.
James [Sat, 16 Jan 2010 22:57:08 +0000 (22:57 +0000)]
Doc:Doc-work.itexi edits - LilyPond Formatting
Removed dupe wording of 1 bar per line preferred
Grouped few reqs together in a more logical order
minor punctuation and grammar edits (expanded contractions, used third person not first)
Reworded some phrases so it scans better
James [Sat, 16 Jan 2010 22:34:31 +0000 (22:34 +0000)]
Doc:Tab-example add whiteout in hidefretnumber var
updated version number
tidied up indentation
made spacing and line lengths consistent for each bar/variable
removed bar checks
removed unnecessary commented out lines
Graham Percival [Sat, 16 Jan 2010 16:38:47 +0000 (16:38 +0000)]
Make it easier to change the lilypond-git dir.
I don't recommend that people do this, but *sigh* there's a lot of
interest in it. (OTOH, I guess that's to be expected from people
who want to work on open-source projects)
Neil Puttock [Fri, 15 Jan 2010 00:02:23 +0000 (00:02 +0000)]
Fix DynamicTextSpanner left alignment.
When a DynamicTextSpanner directly follows a DynamicScript, padding is
required to ensure the 'left 'text doesn't collide with the
dynamic sign. Unfortunately, this default value skews the
spanner's left bound to the right when no dynamic script is present.
This patch caters for both situations by resetting 'left 'padding
and 'left 'attach-dir as required, adding extra padding read from the
property 'right-padding to fine-tune the space between the text elements.
* add regtests demonstrating 'right-padding and correct alignment
* remove hard-coded 'bound-details setting in New_dynamic_engraver, which
prevented user override
* add dynamic-text-interface with user property 'right-padding
* add 'before-line-breaking callback dynamic-text-spanner::before-line-breaking
which checks whether the left bound is a DynamicText; if this is true,
set nested properties 'left 'attach-dir/'padding to prevent collision
Joseph Wakeling [Thu, 14 Jan 2010 23:30:21 +0000 (15:30 -0800)]
Doc: CG: Sending and receiving patches via email.
This contains the solution for MIMEtype problems experienced
with some email clients, and a link to the Wine wiki page on
git which contains much useful info.