Apache OpenOffice (AOO) Bugzilla – Issue 7294
Produce W3C validated HTML and CSS code for the websites core
Last modified: 2010-08-25 12:36:00 UTC
As an Open Source project the website for OpenOffice.org should follow W3C's specifications for HTML and CSS. This can easily be validated by the HTML validator: http://validator.w3.org/ and by the CSS validator: http://jigsaw.w3.org/css-validator/validator-uri.html I hope this will be one of the main focus when the site will be updated generally. Only through open standards and specifications Open Source has the oppertunity to win so we should use them as much as possible.
Hi, Claus, Well, we would like to follow the standards; your suggestion is hardly new. Join the website project: http://website.openoffice.org/ best louis
Louis, I think part of the effort has to be done by CN in SC. Would you like to coordinate with support?
How later will this issue be resolved? We would like the world to use OASIS Open Office XML as the file format for exchanging office documents. But we lack to support the W3C specifications for our own website. The HTML code I create for the Danish native language project validates as HTML 4.01.
Don't forget to ensure W3 accessibility guidelines: http://bobby.watchfire.com/bobby/html/en/index.jsp
I strongly support the demand for a W3C valid website. Native-lang projects like da.openoffice.org have a had time validating the HTML-code for our N-L pages, because W3C's validation service returns several errors for the mainmenu etc. How can we help? or is this solely a supplier issue?
hi it's a supplier issue. But it's also the responsibility of each Project Lead to make sure his web pages conform as closely as possible to w3c standards. We are upgrding to a new platform for OOo that is pretty close to w3c standards. You are welcome to join the team; Cristian Driga is leading design. let me know directly if you are interested. You will have to sign an nda with collabnet. louis
The HTML for the DA.OpenOffice.org subproject is valid XHTML. I am not interested in signing a NDA, and the new site is now online. Following this link should help the developers get started with writing valid code: http://validator.w3.org/check?uri=http://www.openoffice.org Adding myself as cc: Adjusting summary. Reassigning to www component owner.
I just filed issue 41162 and issue 41163 If these two are fixed, then it is possible to create valid xhtml-transitional. Instead of the main-page, try the german-lang page which (apart from the above issues) already is valid xhtml. http://validator.w3.org/check?uri=http://de.openoffice.org da-project and the main site contain additional errors not influenced by the automatic additions.
The issue 41162 and issue 41163 are fixed and the de homepage passes the HTML validation without error. If someone is interested in filing subissues for CSS errors...
I removed the keyword 'accessibility' of this issue (issue 7294) because (external) queries use (blind) this keyword to evaluate the accessibility of the product (OOo) itself. Even if the validation conforming to w3c leads to improvements in accessibility: - this keyword should be reserved for the product and not the web site - this keyword should be reserved for issues concerning accessibility issues *and only accessibility issues*. Thank you for your understanding.
As of now: www.openoffice.org/branding/css/tigris.css is valid - http://jigsaw.w3.org/css-validator/validator?uri=www.openoffice.org%2Fbranding%2Fcss%2Ftigris.css&warning=1&profile=css2&usermedium=all www.openoffice.org/branding/css/inst.css is valid - http://jigsaw.w3.org/css-validator/validator?uri=www.openoffice.org%2Fbranding%2Fcss%2Finst.css&warning=1&profile=css2&usermedium=all www.openoffice.org/branding/css/print.css is valid - http://jigsaw.w3.org/css-validator/validator?uri=www.openoffice.org%2Fbranding%2Fcss%2Fprint.css&warning=1&profile=css2&usermedium=all I can also produce valid HTML for da-project. Therefore, this issue can either be resolved as fixed or used as a "pass the monkey" reminder for projects writing invalid HTML. Reassigning to louis since he is owner of the project webworks.
I'd like to close this as fixed and leave it in public memory for the fixes it demonstrates. will reference it from website project closing. thanks all. louis
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew
Created attachment 70507
Created attachment 71276
Created attachment 71335