[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lilypond.org/website vs lilypond.org/ [was: Minor errors ofthe websi
Re: lilypond.org/website vs lilypond.org/ [was: Minor errors ofthe website]
Sat, 16 Feb 2013 11:56:06 -0000
"Colin Hall" <address@hidden> wrote in message
Felix Janda writes:
Ok, just to collect some stuff:
It seems like that actually most things are in the /website directory on
the server. For instance when going to lilypond.org/pdf Apache shows the
index of /website/pdf (but one is not redirected).
Actually grepping the source for "http://lilypond.org/[^wd]" doesn't
give too many results:
Most are http://lilypond.org/~graham and http://lilypond.org/test, which
seem to be actually on the root of the server. Also /gub and /vc are
only at the root. /search doesn't seem to exist
(Documentation/topdocs/README.texi). There are different robots.txt in /
So the Apache trickery seems to be to have shorter links, i.e.
http://lilypond.org/sponsoring.html instead of
That doesn't work to well with relative links, though.
Thanks for your diligent work in documenting these problems, Felix.
Having read back through this thread I think you are reporting two
problems with the website:
The lilypond website is not w3c compliant.
The lilypond website does not interoperate with the lynx web browser due
to ellipses in some intra-site links.
Is that a concise summary, Felix?
Phil has pointed out that fixing it is complicated (and probably also
So, devs and documentation authors, would you like me to accept this
(minor) bug report and create a tracker?
The tracker could be "document interoperabilty and standards compliance"
or it could be "fix the web site", you decide.
In the absence of any opinions I would opt for the former.
I would suggest 2 issues: 1) Fix website W3C compliance (which I can fix)
and 2) Fix website links (which I've discussed in the past with Graham, who
warned me off touching it. While it's mostly working, I wouldn't touch it).