Sietse Brouwer schreef:
Some bugs I found on the web page, four in total, but the fourth is hardly noticable at all for most people.

That's wonderful. Unfortunately, I'm also rather busy. Could you have go at fixing the (simple) bugs yourself ? The website is built in plain HTML, and you can check it out from

  https://savannah.gnu.org/cvs/?group=lilypond

as the

  newweb

module. Look for site/switch/ for the intro files.

Firstly, on the front page [http://lilypond.org/web]the text "http://lilypond.org .ca mirror" appears in a box that is not high enough. The top and the bottom of the text get cut off, leaving some illegible vertical lines.

This problem occurs under Windows XP, in Opera 8.54 and IE 6. It does not occur in Firefox 1.5 (no plugins).

Secondly, on the "About" page [http://lilypond.org/web/about/], the image of the Linux Audio Developers doesn't appear. It should be located at [http://www.linuxdj.com/audio/lad/graphics/ladbanner_50.gif], but it isn't.

should be fixed now.

Thirdly, in the "Introduction" section, it would be nice to have "Next" and "Previous" links between the "Why use LilyPond?", "Testimonials", "A short tour", and "Crash course" pages. I know they don't follow each other strictly speaking, but most people would want to read them in order. I know I read them in order, all four or so times -- months apart -- that I read the section.

the last link on the page is actually a Next pointer. Maybe it should have a different markup, eg.

  << Prev: Why use lily | Next: Crash course >>

Fourthly, the navigation links in the documentation have nifty rel="up" properties where applicable. This allows Opera, for instance, to use a keyboard shortcut to go up one level. However, at the first level under the top, the link to the Top has rel="start" instead of rel="top". It might be useful to give that link both properties, if possible. This is more of a feature suggestion, though, and a *very* minor one at that. But since I'm posting anyway....

which pages are you talking about now? Is that the documentation? Then it's really a texinfo problem/feature


--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to