Topic: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Just something to think about:

Ian Hickson, a member of the Mozilla.org Browser Standards Compliance QA team and an invited expert in the W3C CSS Working Group, explains why XHTML should not be sent as text/html: http://hixie.ch/advocacy/xhtml

Abstract
--------

A number of problems resulting from the use of the text/html MIME type
in conjunction with XHTML content are discussed. It is suggested that
XHTML delivered as text/html is broken and XHTML delivered as text/xml
is risky, so authors intending their work for public consumption
should stick to HTML 4.01, and authors who wish to use XHTML should
deliver their markup as application/xhtml+xml.

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

http://punbb.org/forums/viewtopic.php?id=7486
among other discussions that have been had tongue
So yeah, there are advantages to XHTML 1.0 Strict while still serving it as text/html

3

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Read that article a long time ago. I disagreed with it then and still do. Version 1.3 has gone the opposite direction. Its been running perfectly as application/xhtml+xml and even text/xml with the aid of content negotiation (there will be a content negotiation extension). Since custom templates can now be used the end user can change the doctype for a particular style to whatever they wish. Since the markup is valid xhtml 1.0 strict an html 4.01 Strict doctype should also work without difficulty.

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Paul wrote:

Since custom templates can now be used the end user can change the doctype for a particular style to whatever they wish. Since the markup is valid xhtml 1.0 strict an html 4.01 Strict doctype should also work without difficulty.

Aha. If there is nothing in the PHP guts of Pun that gets in the way of that, that's cool then. Thanks for the info.

5 (edited by Miles 2006-04-12 05:49)

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Does PunBB 1.3 provide protection against a user breaking a page with invalid markup?

6

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Miles wrote:

Does PunBB 1.3 provide protection against a user breaking a page with invalid markup?

Well a user can't use markup anywhere so the problem shouldn't arise, if it does then it means there is a bug in parser.php. There is nothing to stop style designers, people writing extensions or administrators coming up with rubbish markup though. There is no difference between 1.2 and 1.3 in that respect.

7 (edited by Smartys 2006-04-12 12:29)

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Paul: He means like what he did

[b]invalid [i]markup[/b]?[/i]

Where the tags aren't nested properly

8

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

Well if thats possible it means that parser.php is not fully doing its job. What if anything is happening to parser.php is not my department ($buck = 'passed').

Re: Change the labelling that Pun applies to pages as XHTML to HTML 4.01..

The improper nesting problem will hopefully be dealt with.

"Programming is like sex: one mistake and you have to support it for the rest of your life."