After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 172488 - art.dot.gnome not standards compliant.
art.dot.gnome not standards compliant.
Status: RESOLVED FIXED
Product: website
Classification: Infrastructure
Component: art.gnome.org (obsolete)
current
Other Linux
: Normal normal
: ---
Assigned To: art.gnome.org maintainers
art.gnome.org maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-03 06:40 UTC by James
Modified: 2005-07-14 18:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fixes some xhtml compliance of the header/footer (1.48 KB, patch)
2005-04-03 06:46 UTC, James
committed Details | Review
directly inputs html instead of using print(), made more xhtml strict ready (<b> -> <strong>; <center> -> <div align="center"> (7.69 KB, patch)
2005-04-03 17:15 UTC, James
none Details | Review
made includes.inc.php xhtml compliant, and more xhtml strict ready (2.44 KB, patch)
2005-04-03 17:30 UTC, James
none Details | Review
in faq.php: added missing </li> tag, changed <p> to <br /><br /> (631 bytes, patch)
2005-04-03 18:30 UTC, James
none Details | Review
various xhtml compliance fixes. at least, most of the obvious ones. (23.02 KB, patch)
2005-04-03 23:48 UTC, James
committed Details | Review

Description James 2005-04-03 06:40:14 UTC
see http://validator.w3.org

I'll put some patches up real soon.
Comment 1 James 2005-04-03 06:46:02 UTC
Created attachment 39619 [details] [review]
fixes some xhtml compliance of the header/footer

I'm assuming the other stuff causing errors on the front page is in the
database.
Comment 2 Thomas Wood 2005-04-03 13:40:43 UTC
I fixed the <link> short tag error, but I don't think the <ul> tag needs to be
inside a <p> tag. I updated the copyright.php and it is now fully XHTML, which
shows the headers are too.

The rest of the stuff causing errors is mostly database. Html should not really
be in the database, so this needs to be removed and a proper parsing needs to be
done to allow formatting (like what is currently used for the comments). Once
that is done we can find the XHTML errors in the code more easily.
Comment 3 James 2005-04-03 17:15:59 UTC
Created attachment 39642 [details] [review]
directly inputs html instead of using print(), made more xhtml strict ready (<b> -> <strong>; <center> -> <div align="center">

another thing we could to do make finding errors more easily is seperate the
lines in the html output.  Also, if we escape php and output html directly, it
is supposed to be faster (but it's a lot easier to read, because you do not
have to escape quotes).
Comment 4 James 2005-04-03 17:30:32 UTC
Created attachment 39643 [details] [review]
made includes.inc.php xhtml compliant, and more xhtml strict ready
Comment 5 James 2005-04-03 18:30:25 UTC
Created attachment 39647 [details] [review]
in faq.php: added missing </li> tag, changed <p> to <br /><br />
Comment 6 James 2005-04-03 23:48:45 UTC
Created attachment 39658 [details] [review]
various xhtml compliance fixes.  at least, most of the obvious ones.

this patch includes 39643 & 39647.
Comment 7 Thomas Wood 2005-04-05 21:59:07 UTC
I have comitted patch 39658. I also did some other work and I think most, if not
all, pages are now XHTML compliant.

Next thing to do is to make sure all output from the database is parsed to html
properly. I renamed the parse_comment() function to html_parse_text(), which
should be used every time text is taken from the database.
Comment 8 Thomas Wood 2005-07-14 18:42:07 UTC
I think we're almost 100% standards compliant now, so marking as fixed.

This is now an ongoing objective as art.gnome.org is developed. However, feel free to re-open this bug 
with information on any new standards issues if they come to light.