Re: [Phpwiki-talk] xhtml-compliant wiki

[Tara S. <te...@cl...>]

Steve Wainstead wrote:


> I want PhpWiki to support Lynx, Emacs' w3 mode, and all browsers of all
> versions. It's just text. I think it's more important to focus on featu=
res
> like version control, XML dumps, and features like that... the layout
> should be uncluttered and simple. A Wiki, any Wiki, is about ease of us=
e
> and writing hypertext.


the "new" table-less approach is much more lynx-etc-friendly than the=20
"old" table-ridden layouts.


> Out of the box, PhpWiki should support all browsers. I think that xhtml
> output won't pose much trouble: if you properly add spaces in tags like
> <br />, the 4.x browsers don't care. (However, is that all 4.x browsers=
?)


it's not just <br />. It's also a question of closing tags, nesting=20
elements properly, and avoiding the use of what I call "presentational"=20
html.

old browsers shouldn't choke on <br />: the "/" is treated as an unknown=20
attribute and ignored (that happens because we leave a space; without a=20
space, some browsers may choke).


> So, out of the box: no Javascript, no fancy CSS. Please. We can pack in
> all we want though, and make it easy to enable. By all means, styleshee=
ts
> and Javascript only supported in Mozilla would be most welcome by me! :=
-)


the great idea of css is that it is frighteningly easy to edit. If you=20
give a css-only version of php-wiki, and I decide I want to use fancy=20
css that isn't supported by old browsers, it's very easy for me to=20
change it - so no problem with that.

The problem is when the (x)html itself isn't "100% clean" - see what I me=
an?

:)


Tara


--=20
Je r=E9ponds au mieux de mes connaissances
Climb to the Stars! - http://climbtothestars.org/
SpiroLattic - http://climbtothestars.org/spiro/
Pompeurs Associ=E9s - http://pompage.net/