Mike Solomon [Thu, 12 May 2011 23:28:24 +0000 (19:28 -0400)]
Fixes the assert problem caused by ledger line spanners.
This fix makes it such that ledger lines are not printed when
there is a no-line staff symbol. This makes sense, as a note
cannot be above or below the staff if the staff does not exist,
which means that ledger lines should not be used.
James Lowe [Tue, 26 Apr 2011 21:39:28 +0000 (22:39 +0100)]
Doc: Adjusted CG Policy on @lilypond[] variables
As a reuslt of work on NR 3.2 Titles and Headers, it was necessary to
define some more explicit requirements for using the variables in the
@lilypond[ ... ] construct. Ssuch as removing staffsize
and page sizes within the actual @lilypond example which only add more noise
to the examples.
Also when the need to show taglines and/or page breaks and footers is required then
\book is needed in the example and this will result in unnecessary white space between top and bottom
of the page. So showing page breaking features or numbering examples becomes
problematic within the documentation.
The new @lilypond[papersize=X] variable allows for explicit page sizing without
the need to include it in the example itself. Allowing for better clarity.
The papersize=X takes variables from the scm/paper.scm else 'a4' is presumed.
Moved existing material to the front of this section so that it makes more sense
and added the new requirements for the various preferred variables.
Allow for spaces in ttf font glyph names. Fixes #1562.
Apparently, the Verdana.ttf font that comes with Windows 7 SP1
has glyphs 571 and 571 using names "glyph 571" and "glyph 572", i.e.,
their glyph names contain spaces. This breaks the PostScript output.
Thanks to Chris Lidell and James Lowe for their help to nail this
bug.
Keith OHara [Tue, 24 May 2011 01:49:23 +0000 (18:49 -0700)]
Loose lines honor padding between systems
When placing a loose line (e.g. Lyrics) at the top or bottom of a
system, include as a constraint the padding to the neighboring
system or markup. Fix 1654.
Trevor Daniels [Thu, 12 May 2011 08:39:31 +0000 (09:39 +0100)]
Fix calculation of vertical offset when 'staff-padding is set
- fix 877: Ottava clefs may not look good
- the previous code incorrectly calculated the offset from
the staff rather than the parent; this happened to coincide
with the correct value for most parents but gave an incorrect
offset for OctavateEight above the F-clef
Mike Solomon [Tue, 26 Apr 2011 11:09:21 +0000 (07:09 -0400)]
Fixes cross staff issue with beam collision avoidance.
Beam collision avoidance is now turned off for "fake" cross staff beams
(those that are registered as cross staff because of auto-beaming but
are in fact not). Additionally, beams no longer process other
cross-staff beams as covered grobs.
Mike Solomon [Fri, 22 Apr 2011 15:29:33 +0000 (11:29 -0400)]
Update beam collision in the documentation.
Notify users that beam collision avoidance does not occur for cross
staff beams and suggest that users use manual beams for beams that
end right before a staff change.
Fix "make doc" error: Character set messup in pdf-scheme.cc
In "make doc", somehow the LANG env variable is cleared, so
glib returned charset=ANSI_X3.4-1968 for the input string. This would
disallow any accented characters in the input string.
However, we know that the input string is by definition always UTF-8,
so the solution is not to use the current locale, but hardcode UTF-8.
Once we switch to guile 2.0, we should use (sting->utf16 str 'big)
instead of manually converting the string in C.
pdf-metadata: Use UTF-16BE for metadata if required
All Latin1 metadata strings need to be printed out to the .ps file
in Latin1 (NOT in UTF-8), and all non-Latin1 strings need to use
UTF-16BE encoding.
The escaping of parentheses and backslashes needs to be applied
AFTER encoding the string (since the escaping is required to correctly
detect the end of the encoding string when reading the byte-sequence
of the encoded string from the file. Basically, we are dumping a binary
sequence to the file, enclosed by parentheses. All \051 bytes need
to be escaped to make sure they are not detected as the closing
parenthesis.)
pdf-metadata: Use UTF-16BE for metadata if required
All Latin1 metadata strings need to be printed out to the .ps file
in Latin1 (NOT in UTF-8), and all non-Latin1 strings need to use
UTF-16BE encoding.
The escaping of parentheses and backslashes needs to be applied
AFTER encoding the string (since the escaping is required to correctly
detect the end of the encoding string when reading the byte-sequence
of the encoded string from the file. Basically, we are dumping a binary
sequence to the file, enclosed by parentheses. All \051 bytes need
to be escaped to make sure they are not detected as the closing
parenthesis.)
Add feature to link to a particular page or a page containing a given label
The main part of this patch was done by Dan Eble and posted to the
lilypond-devel mailinglist on December 27, 2010.
Like \with-url, this works only with the PDF backend.
-) Add markup functions \with-link (links to the page containing the
given label) and \page-link (links to the given page number)
-) Internally, they are handled like the \with-url markup function,
creating a pdfmark in the .ps file that creates the link in the
PDF file.
-) Add links to the pages for all TOC entries.