Urs Liska [Tue, 7 Jan 2014 11:51:02 +0000 (12:51 +0100)]
Issue 3785:Web:Background: Reword intr. paragraph
I've always found this page confusing because I didn't understand
why there is this "placeholder" page.
This commit addresses this by making the "manual" issue explicit.
Additionally I consider it more useful to _first_ tell the reader
what it is and _then_ advise him to skip the essay instead of
_immediately_ telling him "Probably you won't want to read this".
If it is necessary to have the link at the end of a paragraph
(and not only of a sentence) I'd simply insert a new paragraph
after the link.
Urs Liska [Tue, 7 Jan 2014 11:30:54 +0000 (12:30 +0100)]
Issue 3785: Web:Productions: Add title box
As stated in https://codereview.appspot.com/48450044/
I think the Introduction pages should have a title box
giving the user a first idea about the page.
In this case the visitor (currently) would reach the page,
doesn't see a heading and is faced two boxes,
"Concerts" and "Published sheet music" without further introduction.
Urs Liska [Tue, 7 Jan 2014 11:18:35 +0000 (12:18 +0100)]
Issue 3785: Web:Examples: Enclose in box
I think the pages below Introduction (and probably Community too)
should consistently start with a box and a subheading,
because there is no eye-catching page heading.
This is _one_ option to do that for the Examples page.
Others would be:
- Make that @div only enclose the introductory paragraph
- enclose the introductory paragraph _and_
- add a headingless div around the examples _or_
- add a div with @subheading "Gallery"
James Lowe [Sun, 5 Jan 2014 18:10:04 +0000 (18:10 +0000)]
Doc: NR Tidy up of Midi 3.5.x sections
General tidy up for consistent line breaks and
@seealso sections plus other minor Doc CG Guidelines
No information has been changed (added or deleted).
This patch is in preparation for another tracker issue (#2877) where
some information will be moved around and information from
some sections in 3.5.x merged/deleted/improved.
Trevor Daniels [Sat, 11 Jan 2014 15:10:32 +0000 (15:10 +0000)]
Issue 3796: Doc: Bump version number
The version number of this file should have been increased
to 2.18.0 when patch 22ea3eb6b78a50784ae02c3f29060e1c093262a4
for Issue 3720 was applied to prevent inappropriate conversions
being made by convert-ly.
Devon Schudy [Sat, 21 Dec 2013 03:55:51 +0000 (22:55 -0500)]
Tremolo cleanup. (issue 3745)
Scale durations when iterating, not in make-repeat. This means the original
repeat body is intact, so unfold-repeats and display methods no longer need
to undo the scaling.
Build tremolo spanners in Scheme, not C++.
Calculate tremolo-type in tremolo::get-music-list rather than storing it as a property.
shift-duration-log now clears the cached length, since it changes the length.
\shiftDurations no longer duplicates shift-duration-log.
David Kastrup [Wed, 1 Jan 2014 23:57:15 +0000 (00:57 +0100)]
Issue 3769: Lexer/Parser: Don't package location data in SCM_TOKEN semantic value
As the location data is available as the location value in the parser
anyway, there is no point in packaging it into the semantic value.
Among other things, this leads to a cleaner display when using
-ddebug-parser, and to better understandable code.
James Lowe [Mon, 6 Jan 2014 07:07:08 +0000 (07:07 +0000)]
Doc: Extending - @ignore for inline scheme coding
Issue 1999
Added @ignore for what was 2.8 'Inline Scheme Code' as the
current example is technically incorrect and finding/writing a
non-trivial example (to make the documenting of it worthwhile
in the first place) is 'rather hard'.
James Lowe [Wed, 1 Jan 2014 14:55:22 +0000 (14:55 +0000)]
change keymap for vim to view PDF not PS
Issue 3767
Also removed two comment lines indicating a maintainer and
'last modified' date; the latter being incorrect and the
former's email apparently not existing anymore
James Lowe [Fri, 27 Dec 2013 23:50:57 +0000 (23:50 +0000)]
Doc: NR add \chord to examples in A2
Issue 3755
Added new column to show a working example (also useful for Blind composers)
Minor layout quibbles with @multitable means using the @* (forced break)
for TexInfo commands - not strictly LP doc policy - to enhance clarity
Reduced the line-width slightly of the @lilypond examples simply to
help accommodate the extra column
James Lowe [Sun, 29 Dec 2013 05:46:45 +0000 (05:46 +0000)]
Doc: NR Tidy up of A4 - fretboard diagrams
Removed bar numbers - inappropriate for this section
Added an @appendixsubsec for each of the three pre-defined
fretboard instruments (Guitar, Ukulele and Mandolin) so as
to make it easier to find in the index but also to break up
the apparent 'wall' of fretboard diagrams when viewing the
Appendix.
Keith OHara [Wed, 18 Dec 2013 01:20:22 +0000 (17:20 -0800)]
note-spacing: let compressibility be uniform; issue 3304
Comments implied that half the width of accidentals, etc., was added
to the ideal spacing between notes, but in fact only compressibility
was affected. The non-uniform compressibility caused note-spacing
to become non-uniform when the lines were compressed. For example
A sequence {\stemUp a a d a] would have the head of the D tuck under
the preceding A.
This commit keeps spacing uniform on compressed lines until objects
come within padding of each other.
Keith OHara [Wed, 18 Dec 2013 00:41:51 +0000 (16:41 -0800)]
note-spacing: stretch somewhat uniformly
Start with a basic spring based on the note duration, and apply optical
corrections to that. This results in more consistent springs thus more
uniform stretching in polyphonic situations.
Dynamics usually have extra-spacing-width set to an empty interval so
that their placement does not cause other elements to shift.
With span bars, however, the resulting overlap is a worse cure than
the problem. So this switches off the width-hiding setting of
extra-spacing-width inside of staff groups using span bars by default.
No extra space is allocated, so dynamics will clear the span bars only
narrowly, a reasonable compromise.
James Lowe [Tue, 24 Dec 2013 06:52:22 +0000 (06:52 +0000)]
Doc: NR Updated Delayed Turn Snippet
Issue 3369
Suggestion from Arno Waschk
Simplification of original snippet
Note: This snippet will only work since 2.17 versions (where the /single
command has been implemented) and does not work on the 'current' LSR
(which is still at 2.14 as of this patch).
James Lowe [Tue, 31 Dec 2013 07:06:11 +0000 (07:06 +0000)]
Doc: Tidy up of chord-names-jazz.ly
Added a new context definitigon to remove the Bar Number Engraver
as it was clashing with the instrument names and looked messy.
As it was not actually pertinent to the example I thought this the
simplest method
Also tidied up the spacing of the information as per standard doc
guidelines
Mike Solomon [Mon, 16 Dec 2013 08:11:10 +0000 (10:11 +0200)]
Adds outside-staff-interface and outside-staff-axis-group-interface
When a property exists in an interface, the property should make sense for
a sensible of grobs that implement that interface. Otherwise, the property
should be part of a separate interface that applies to a sensibly-sized
group of grobs.
Various properties having to do with outside-staff calculations belong to
grob-interface. This does not make sense for many grobs (StaffSpacing,
NoteSpacing, SpacingSpanner, StaffSymbol just to name a few). There is a
limited collection of grobs for which outside-staff properties make sense.
The outside-staff-interface provides a separate interface to be implemented
by these grobs.
The same is true for axis groups that place outside-staff grobs, which form
a limited subset of grobs implementing the axis-group-interface. Rather than
putting the relevant properties in the axis-group-interface, we move
them to an outside-staff-axis-group-interface.
Devon Schudy [Sun, 15 Dec 2013 22:27:00 +0000 (17:27 -0500)]
Update documentation for what's supported in MIDI. (issue 3740)
Also clarify what articulate.ly supports.
Change the snippet for redefining a shorthand to use an ArticulationEvent
instead of an articulation name, so users who follow its example will have
their articulations work in MIDI.
Urs Liska [Fri, 20 Dec 2013 09:09:04 +0000 (10:09 +0100)]
Issue 3732: Web: Rewrite "Features" content
The "Features" page had some problematic content and structure.
This commit makes some points more clear, removes problematic
claims and introduces some more points pro LilyPond.
Additionally replace some "color2" divs by generic divClass
Carl Peterson [Thu, 12 Dec 2013 23:05:11 +0000 (18:05 -0500)]
fix sidebar colors in html documentation
Change the default color of the TOC sidebar when no manual-specific color has been specified. Because the text color was changed to white, the TOC was not legible in manuals like the glossary, which is not assigned a color currently.
Also, darkened most of the manual TOC sidebars to separate from header and footer colors. Lightened the header and footer for the Contributor's Guide since it is the "black book."
Carl Peterson [Mon, 9 Dec 2013 00:20:03 +0000 (19:20 -0500)]
CSS changes to color-code major manuals
Added styling to use a manual-specific class in the <body> tag to color code each of the major manuals.
Now:
* Learning Manual: Green book
* Notation Reference: Blue book
* Usage Manual: Yellow book
* Extending: Red book
* Internals Reference: Purple book
* Contributor's Guide: Black book
Carl Peterson [Sun, 8 Dec 2013 16:44:08 +0000 (11:44 -0500)]
Add classes to <body> tag of documentation files
To facilitate request from lilypond-user to facilitate differentiating among the various manuals, appending CSS classes to the <body> tag of the documentation files so that the main CSS stylesheet can be modified to look for those classes to specifically style each manual and development status.
The present solution for indicating development status is a hardcoded line in Documentation/lilypond-texi2html.init.
Urs Liska [Thu, 12 Dec 2013 10:16:10 +0000 (11:16 +0100)]
Web: Reword contactUsAbout macro
Providing information on new reviews/productions etc.
should be possible by simply writing an email to bug-lilypond.
Redirecting to the Bug Report guide is off-putting.
Janek Warchoł [Wed, 4 Dec 2013 14:26:03 +0000 (15:26 +0100)]
font: parametrize and cleanup sharp code
Changes:
* as much as possible is controlled by global parameters,
* variables have more consistent names,
* the functions are more consistently structured,
* stem ends are placed in one line using explicit beam direction.
The glyphs remain identical.
It would be good to extract one global procedure that would draw
all needed sharps (instead of having 6 similar ones), but i didn't
have enough time to do this.
Janek Warchoł [Wed, 4 Dec 2013 11:20:12 +0000 (12:20 +0100)]
font: rewrite and parametrize natural code
The logic remains virtually the same. List of changes:
* more descriptive variable names,
* removed surplus points (1', 3', 11', 21'),
* stem brushing is controlled in a simpler way,
* beam slant does no longer depend on stem thickness,
* all dimensions are explicitely and straightforwardly
derived from global parameters. This makes it trivial
to get a differently-looking natural by just changing
clearly defined values.
At size 20, the natural remains identical. At signifincantly
different sizes there are a few microscopic changes, but they
are too small to be noticeable:
* stem end thickness is defined in terms of stem thickness,
so regardless of design size the ratio between them is constant.
* beam slant is slightly more consistent. But you wouldn't notice
the change if i haven't told you ;-)