[ moin-Bugs-531617 ] no valid html/xhtml

"SourceForge.net" <[email protected]> Tue, 23 Dec 2003 05:32:32 -0800
Newsgroups	gmane.comp.web.wiki.moin.devel
Message-ID	<[email protected]>
Bugs item #531617, was opened at 2002-03-18 23:29
Message generated for change (Comment added) made by thomaswaldmann
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108482&aid=531617&group_id=8482

Category: None
Group: None
>Status: Closed
Resolution: Wont Fix
Priority: 6
Submitted By: Ronny Buchmann (rbla)
Assigned to: Nobody/Anonymous (nobody)
Summary: no valid html/xhtml

Initial Comment:
as everybody knows moinmoin doesn't produce valid html.
i consider this a bug. i have a patch for valid html
4.01 transitional code.
the patch is safe (i think) and doesnt change look,
with one exception: the search buttons cant have
attributes like images (hspace, border etc), only css
is allowed, but netscape 4.x doesnt understand it
right, so it looks a bit different (borders!).

please test and apply (at least the other chunks)

ronny

----------------------------------------------------------------------

>Comment By: Thomas Waldmann (thomaswaldmann)
Date: 2003-12-23 14:32

Message:
Logged In: YES 
user_id=100649

this is currently being adressed in branch moin--main--1.2,
together with themeing work and moving to css - most work
done by Bastian Blank.

some issues might not get fixed immediately as they are not
possible with the current parser.

but at least, I have already seen some pages validate at W3C
validator ;)


----------------------------------------------------------------------

Comment By: Ronny Buchmann (rbla)
Date: 2002-03-19 14:47

Message:
Logged In: YES 
user_id=91363

so heres the next patch: moinmoin-xhtml.1.patch

issues adressed:
* namespace for <html>
* elements and attributes only lowercase
* empty elements (br, hr, meta, img, input)
* empty attributes (nowrap, checked)
* all attribute values with quotes
i hope to have found all occurences

issues not adressed:
* no closing tag for <p>
 (is there some magic involved? i dont find my way through
the code here, but i assume it's easy for you, jÃ¼rgen)
* printing of xml header and dtd (trivial)


----------------------------------------------------------------------

Comment By: Ronny Buchmann (rbla)
Date: 2002-03-19 08:42

Message:
Logged In: YES 
user_id=91363

no, your change to Page.py isnt enough.
and i dont think it makes sense to use string.replace to
correct typos. (but if your going to actually use url() and
link_to(), then i dont have a problem)

and if you want xhtml, thats no problem.
i'll start making some diffs

----------------------------------------------------------------------

Comment By: JÃ¼rgen Hermann (jhermann)
Date: 2002-03-18 23:49

Message:
Logged In: YES 
user_id=39128

much easier to fix is at ONE place in url() and link_to()

the inline search forms will NOT be fixed, because they are 
how they are intentionally

for any remaining issues you might reopen the bug (do diffs 
against current CVS), but don't hold your breath; as we 
approach XHTML compliance and templating, the issue isn't 
worth any major effort on current code.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108482&aid=531617&group_id=8482


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click