-) Add a search field to the toc pane in our docs. If the user types three
letters or more, an AJAX request is sent to the server to perform a
search. The AJAX part is implemented in JS, the search part itself is
implemented in PHP on the server side, which wades through a pre-generated
index file (pure text).
-) The texi2html init file now has the ability to create our own search
index file, currently in pure text (the search script will go through it
line for line.
-) The search box is shown via JavaScript only if the files are viewed over
http. If the user has JavaScript disabled or if the files are viewed as
static pages (and not over http), then no search box appears, since it
would not work anyway.
-) Also, don't show search box when AJAX initialization failed.
-) Print nice message if search index can't be opened, don't fail with error
-) Install and use language-dependent index files for all known languages
-) If we don't have a texinfo index, don't load the JS and don't print
out the search box. (Workaround: css_lines is called before
init_out, so we need to do the check already in css_lines!)
If the index would be empty, don't create an empty .idx file
-) If AJAX works and a user presses enter, the same AJAX query is triggered
as when entering some letters, and the results appear on the same page.
However, if for some reason AJAX does not work (in particular, if the
onSubmit action handler isn't called), then a search page is loaded
with the same results as the AJAX query...
This is clearly not ideal, but at least it's slightly
better than having empty sections. Hopefully someone
else will add more accurate/helpful information later.
The possibility to download the source code as a tarball
wasn't mentioned at all; I added it for completeness' sake,
whilst explicitely discouraging it in favor of git stuff.
David Kastrup [Wed, 19 May 2010 21:44:56 +0000 (15:44 -0600)]
Don't hardcode a limited set of markup signatures.
Remove the hardcoded limitations of markup signatures. This patch is
moving toward a unified interface for music functions, markup functions,
and user functions.
Colin Campbell [Wed, 19 May 2010 19:24:40 +0000 (13:24 -0600)]
Web: reorganise Introduction - Easier editing
re-arranged LPT, Frescobaldi & Denemo
added pointer to Usage Text editor support for Emacs & vim
re-organised "Other programs can export"
added "Algorithmic code generators
Graham Percival [Sun, 16 May 2010 22:37:17 +0000 (23:37 +0100)]
Web: rename/move to create Intro->Reviews
1) old Introduction-> Testimonials ==> the right-hand div in
Introduction->Reviews.
2) old Community->Publications "what others wrote" ==> left-hand
div in Introduction->Reviews.
3) global "s/Testimonials/Reviews/g" in introduction.itely.
Patrick McCarty [Sat, 8 May 2010 20:42:31 +0000 (13:42 -0700)]
Build: Bump Fontconfig minimum version.
LilyPond currently uses an interface from Fontconfig that was
obsoleted in Fontconfig 2.3.96. To prepare for a code cleanup (in
the next commit), bump Fontconfig to 2.4.0, the next stable
release following 2.3.96.
Mark Polesky [Fri, 7 May 2010 23:56:26 +0000 (16:56 -0700)]
Doc & scm/: Music-functions and type-predicates.
- Clean up:
NR 5.6 "Using music functions"
EL 2.1 "Music functions"
- In Extending 2.1, move `Void functions' to end of section,
so `Functions without arguments' comes first.
- Use a consistent indentation format for music functions.
- Make some minor formatting/wording changes.
- Categorize predicates in type-p-name-alist.
- Create type-predicates-doc-string to document
type-p-name-alist automatically.
- Add notation appendix `Predefined type predicates' to
include type-predicates-doc-string.
- Show predicate name instead of "unknown" in
type-check error message (provided by Neil Puttock).
- Make `color?' predicate more specific.
Mark Polesky [Fri, 7 May 2010 21:18:36 +0000 (14:18 -0700)]
Doc: LM: Reformat ly code.
- Use barchecks for multi-measure examples.
- Specify first duration of every measure/line.
- Quote unquoted \clef strings (eg., \clef "treble").
- Change "\TimeKey" to "\keyTime".
- Change "\new Staff << ... >>" to "\new Staff { ... }"
for single-voice staves.
- Remove redundant durations and excess indents.
- Minor edits to some examples in content/formatting
for clarity.
Carl Sorensen [Thu, 6 May 2010 20:44:44 +0000 (14:44 -0600)]
Fix 1075: Flags too narrow
Move feta-flags to feta-noteheads subfont, since it uses the
value of black_notehead_width, which is created when the standard
quarter note head character is created.