Good catches Jon, can you submit this as Bug tickets (we have a website
category there). If you can divide them up into a few separate tickets
it'll make it easy for us web admins to split up the work.
Also note that anyone with CVS access is able and welcome to make
changes to the site - it's in the inkscape_web module. There's a page
with more detailed directions for updating the site on wiki. Rules are
similar to the normal inkscape module - check with other folks if you
want to do major changes, and use a branch if the change will take time
and risk breaking things, but for regular changes "patch first, then
On Wed, 10 Dec 2003, Jon A. Cruz wrote:
> I've noticed some problems on the website in regards to it's markup.
> The most visible problems showed up under Mozilla 1.0.2. I then went to
> validate the pages (at http://validator.w3.org) and found that there
> are actual problems.
> Whoever can make changes should probably go through and use validators
> and do some cleanup. In hand with those pointing out problems, the 3.2
> and 4.0 HTML references at http://www.htmlhelp.com are *very* useful,
> since among other things they are machine generated from the DTDs and
> include listing what tags/elements can contain others, and which can be
> contained. A *must* use for anyone doing web work. :-)
> Anyway, on to some specific problems:
> * The validator doesn't like the keywords meta tag for some reason.
> * Anchor tags can't contain H1 tags. Just swap and put the A's inside
> the H1's and all will be happy-happy
> * ALT attributes missing on images. It's polite to have them. :-D
> * List nestling broken. This is probably the main cause of the problems
> I was seeing.
> * Literal "<defs>" in the text, instead of "<defs>"
> On the list nestling, the problem is with UL's contained in other UL's.
> The validator complains because a UL can't contain another UL. However,
> it's legal to include a UL inside of a LI. So at the moment the last
> list entry is closed before opening a new UL. That closing </LI> tag
> should be moved to *after* the enclosed UL. Then all should be
> (I've gone ahead and sent this out to the list since these are subtle
> things that are easy to trip over and not be aware of, however once
> understood they're easy problems to avoid. Plus the two links up there
> are very useful)
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive? Does it
> help you create better code? SHARE THE LOVE, and help us help
> YOU! Click Here: http://sourceforge.net/donate/
> Inkscape-devel mailing list