XHTML Standards

spinner903 · Post by **spinner903** » Mon 27. Jun 2005, 09:38

I've searched around a little bit in the discussion forums and have found very little regarding XHTML validation. I'm a little distressed by this because XHTML Transitional is a MUST for my new site, which was going to be used with phpwcms, but I'm not sure if this is the best CMS for me. Are there any users or mods out there who have XHTML experience with phpwcms or would like to share any sites that validate?

Post by **Oliver Georgi** » Mon 27. Jun 2005, 10:57

I do not plan to ride the XHTML train. There is absolutely no need for it. Don't know why again and again this should be better than just HTML - it is doing exactly the same and phpwcms validates with 0 errors and 0 warnings if templates are OK.

Oliver

kipara · Post by **kipara** » Tue 28. Jun 2005, 12:24

I am developing a site with PHPWCMS that is XHTML transitional.

You have to hack things a little and you can not use (or rather: I don't want to use) the standard templates. I use custom layout with all code in the main block of the templates. All CSS-P, dropdown menu all CSS lists with javascript only for IEwin. I'll post the site when it goes live.

As for a discussion on HTML vs XHTML. Let's not go there...

Post by **Oliver Georgi** » Tue 28. Jun 2005, 12:30

good not to discuss it

Oliver

consistency · Post by **consistency** » Mon 11. Jul 2005, 09:49

hello

oliver, i disagree with you to not further discuss this, because ther IS a difference between html and xhtml.

css values are interpreted different.

Code: Select all

		width: 190px;
		padding-left: 10px;
		padding-right: 10px;

in html it is interpreded like that:
opera: full_width=190px (the 10px go to the inner side on both sides)
internet explorer: full_width=190px (the 10px go to the inner side on both sides)
firefox: full_width=210px (the 10px go to the outer side on both sides)

in xhtml
all browser interpret it (i think correct according to w3c) as 210px

HTML:

XHTML:

Test Page HTML:
http://www.consistency.at/download/phpw ... _html.html

Test Page XHTML:
http://www.consistency.at/download/phpw ... xhtml.html

so it should at least be some easy way to switch the doctype from the backend.

edit: of course everybody can hack it in the code, but it would be fine to integrate some switch for the backend. changeing so much in the source makes upgrading not easier

Post by **Oliver Georgi** » Mon 11. Jul 2005, 10:24

sorry but I would say:
padding is always inside - so it has to stay 190px in total. The opposite to padding is margin. Then it would bee OK. That's why I still use tables if possible.

And CSS problems are not based on HTML or XHTML. phpwcms will be HTML as is. Switch to XHTML will produce many site with non valid code. And now - if you do anything correct - there is NO warning and no ERROR with phpwcms (and all normal functions) in frontend.

Oliver

consistency · Post by **consistency** » Mon 11. Jul 2005, 11:02

And CSS problems are not based on HTML or XHTML. phpwcms will be HTML as is. Switch to XHTML will produce many site with non valid code.

clear what you mean, i am not talking to implement it right know. maybe for version 2.1 or 2.5 or whatever. the option to change the doctype in backgrond was ment as workaround. just with a warning that the system now produces not 100% percent valid code. but if i think about it as workaround its enough to change it in the source.

padding is always inside

yes it is inside, but the borders get extendet by it. its a browser thing. just compare my testfiles with different browser and you will see. in html they just interpet it different, in xhtml they all interpret it the same way(step in the right direction). i am happy if browser interpret the same way, of course it would be great if the do that with logic, but if not its ok too. the main thing is they do it the same way

and btw, i have not wanted to say that your cms produces wrong html

That's why I still use tables if possible.

i also used tables all the time, but i just tried the css desinging, and it works relativly good in html and very good in xhtml (what i experienced until now)

And CSS problems are not based on HTML or XHTML.

yes/no. in fact the browsers are the issue, if the would interpret all same, it would be much easier, but if the interpret things different in html but same in xhtml it is a html / xhtml problem (indirect).

i just wanted to tell, it was not meant offensive like "IMPLEMENT XHTML, INSTANTLY!",

Post by **Oliver Georgi** » Mon 11. Jul 2005, 11:13

main problem with xhtml which is just html

- new standard is in preparation. I will wait until xhtml2 is available and accepted web wide.

And everything is browser's thing.

xhtml is very strict. But really there is no advantage for normal websites. It's not my main problem right now

Oliver

gent · Post by **gent** » Mon 10. Oct 2005, 17:28

you checked out the new w3c-css validator?

all phpwcms-sites i saw, bring out errors and tons of warnings.

checkout and validate http://phpwcms.de
or http://www.phpwcms-docu.de/index.php?deutsche_version
or http://www.peperkorn-online.de/index.php?warum

ok, the html-errors are about bad templates, but the css-errors
you can get with a fresh install of the actual release.

i.e. the coursor:hand - error located in front.func.inc
sure i know its about the IEwin .. but its simple a error on the validator

and for me personally, as a safari-user, i dont like bad code on my own page only to fix the errors on a webbrowser i never use.

after installing a fresh release i go through front.func.inc and conf.template_default.inc to change the lot of " />" to ">"
thats the simplest error for writing HTML and not XHTML.
most errors are fixed, but the the bad function who writes the linebreaks of a simple-text-contentparts as a "<br />" direct into the database.
i have no idea how to fix this bug, and i live with really clean pages until i use linebrakes in simple-text-contentparts.

Post by **Oliver Georgi** » Mon 10. Oct 2005, 19:54

check current release - there you can change <br> to <div></div>.

And: W3C validator is very strict - so you will nearly always get warnings and bug informations. For me - the Firefox TIDY HTML Vallidator is my orientation.

Oliver