FreeLists / dokuwiki / [dokuwiki] Re: Isolated CSS and stricter XHTML compliance

[Max Khitrov <max@xxxxxxxxxxx>]

Christopher Arndt wrote:
> Do I understand correctly, that this is only an issue when you integrate
> DokuWiki with your site, i.e. your DokuWiki template includes HTML/PHP code
> from outside DokuWiki? Otherwise I couldn't understand how CSS from one page
> could interfere with another.

That's correct... I'm adding my own header and footer to the dokuwiki 
template and until I went through and prefixed all dokuwiki css rules 
with "div.dokuwiki " they interfered with content outside of the 
dokuwiki div.

> If you have made this changes on your site, why don't you make a patch to the
> standard template and share them?

I could do that, though like I said, it's nothing more then adding the 
dokuwiki context to each rule. I think it would be best if we first 
answer the question regarding stricter standards, because that will 
likely affect css as well. Once that is done, I would say instead of 
using the context modification for each item, use it only where really 
needed, and for the rest, give classes unique names.

> Standards are nice, but not purely for their own sake. What to you hope to
> accomplish by making DokuWiki HTML code XHTML strict compliant?

I was actually going for 1.1, but even with strict... Cleaner, more 
manageable code. That's the only real reason for stricter standards. 
More difficult to write in, but more rewarding in the end when you have 
to make changes and upgrade.

For example, the other software that I'm integrating is PunBB - a forum. 
That one is written using XHTML 1.0 Strict, but a change in doctype to 
1.1 didn't result in a single validation error. Not so with dokuwiki. 
Probably took longer to write, but saved me a lot of time when going to 
the next level.

- Max
--
DokuWiki mailing list - more info at
http://wiki.splitbrain.org/wiki:mailinglist