Graham Percival [Mon, 10 Aug 2009 23:21:27 +0000 (16:21 -0700)]
Revert "WEB: hide "(main)" toc entry, add rounding to second (new first) item."
This reverts commit c7c62df72da7222b2ccff52438f385e5c8c9f3c6. We
specifically *do* want the (main) toc entry... at least, I went to
a lot of trouble hacking the perl script to give us one, so I
don't want to remove it unless there's overwhelming discussion in
favor of removal.
Joe Neeman [Mon, 10 Aug 2009 23:44:54 +0000 (09:44 +1000)]
Fixes for moving marks down to staff level.
Enlarge the x-extent by a little bit so that bar numbers aren't moved
down too much.
Prune staves other than the one we are moving to, to preserve cross-staff
correctness.
Neil Puttock [Sun, 9 Aug 2009 22:25:15 +0000 (23:25 +0100)]
New instrument name positioning in scheme.
* split ly:system-start-text::print into three scheme callbacks in
output-lib.scm (X-/Y-offset calculations and print function)
* compensate for system start delimiter extents so all instrument names
in a system are aligned correctly based on self-alignment-X
* use 'when from left-bound instead of get_break_index () to determine
which text to print; this fixes incorrect indentation and text for
shortInstrumentName overrides (Issue #452)
* remove acknowledger for system-start-text from
system-start-delimiter-engraver.cc
* remove system-start-text.cc
* add system-start-text-interface to define-grob-interfaces.scm
* add library functions used by new callbacks to lily-library.scm
and output-lib.scm
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;
projects / lilypond.git / log