Thanks to 'gnomino' on the bug list, here's a slightly
improved definition of fermataMarkup that takes the
markup's direction into account to either print
the dfermata or ufermata glyph accordingly.
Patrick McCarty [Sun, 2 Aug 2009 06:08:23 +0000 (23:08 -0700)]
SVG backend: Output a single SVG file for each page
If the SVG backend is used when creating multiple-page scores, a single
SVG file is created, using the <pageSet> and <page> elements to delimit
individual pages.
Unfortunately, these elements are not supported by any known user
agent, and they are part of a W3C Working Draft (SVG Print 1.2) that
might not reach recommendation status for several years.
At this point in time, a better solution is to output a single SVG file
for each individual page. Outputters are created and closed for every
page, and the unique filename suffixes are used for each successive page.
We want to *eventually* add support for <pageSet> and <page> with a -d
option, so the source code comments have been updated to reflect this.
Joe Neeman [Sun, 2 Aug 2009 20:18:32 +0000 (13:18 -0700)]
Simplify the handling of neighbor columns.
Now we keep track of only one left-neighbor and one right-neighbor
for each column. This makes the loose column determination simpler
and less fragile. Also, we now use a spacing wish if it has
any right-item in the appropriate column (before, we only used it
if its left-most right-item was in the appropriate column). This
fixes the ad-hoc loose-column determination for strict note
spacing.
John Mandereau [Wed, 5 Aug 2009 11:37:52 +0000 (13:37 +0200)]
Web: import new web site from web-gop branch.
Overall structure by Graham, with many comments and suggestions from
-user. Patrick McCarty worked extensively on the css and its
integration with texinfo. Jonathan worked on the Introduction.
Patrick Schmidt did further work on the CSS and the News page.
I reworked the structure of files and directories to integrate it as
well as possible in Lily sources structure and build system.
Status/to-do of this draft:
* no PDF output -- best would be to generate per-page PDF and add
"Print this page" links from HTML pages, which will be doable with a
Texinfo parser;
* no big HTML page output: this makes little sense for a website, and
the init file is currently not compatible with it: the images paths
in the CSS would need to be adjusted to have both one big page and
multiple pages outputs;
* HTML output: file names should be tweaked, which requires converting
Jan's patch to texi2html script into a function in
web-texi2html.init;
* SVG annotated images should be converted to PNG;
* examples of LilyPond scores are missing, they will likely go into a
new directory e.g. Documentation/examples;
* top news in the HTML website and a RSS feed should be generated from
Documentation/general/news.itexi;
* cross-references mechanisms between the new web site and the manuals
should be set up;
* download links should be generated using update-version database;
* online and offline targets should be adjusted;
* support for translating this document is yet to be added;
Marc Hohl [Fri, 10 Jul 2009 08:53:06 +0000 (10:53 +0200)]
New tablature features
this patch includes:
1) tablature is now "numbers only" as default
2) dead notes and palm mute is supported
3) "tied to" fret numbers become invisible
(or parenthesized after line breaks or in a second volta)
4) the slope of glissando lines points in the right direction
5) grace notes (even parenthesized) are represented by smaller
fret numbers.
Patrick McCarty [Sun, 2 Aug 2009 09:37:41 +0000 (02:37 -0700)]
Fix handling of missing stencil expressions
I had not tested the case of multiple \book blocks.
For example, in output-ps.scm a warning is assigned for "utf-8-string",
but this assignment persists for the next \book block, which is
undesirable; the assignments are only supposed to be used while the
stencils are being dumped with the outputter.
This patch removes the "missing" stencil expressions from the
output-module when the outputter is closed.
Joe Neeman [Thu, 30 Jul 2009 20:48:16 +0000 (13:48 -0700)]
Rewrite the vertical layout of staves/systems.
This combines the positioning of systems and staves into
a single pass of a rod-and-spring problem. As a consequence,
the spacing of staves within a system is much more configurable.
Most properties related to vertical spacing have been removed
(eg. page-top-space, between-system-space, between-system-padding)
and replaced with more powerful versions (eg. first-system-spacing,
first-system-title-spacing, between-system-spacing).