XHTML reference?

zanima me, ce kdo pozna kak XHTML reference manual (nekaj v stilu php manuala recimo) v PDF ali se raje CHM?

(<torej opis vseh tagov..., kje se jih da uporabljat, kje ne - lep primer za to je, da mores npr. select tag dat v <p> ali <div> v formu v xhtml strict)
TIA

Specifikacija na w3c ja najvec kar bos nasel:
http://www.w3.org/TR/xhtml1/
sicer je pa izsel nacrt za xhtml 2 in bi bilo mogoce najboljse da zacnes kar pri tem:
http://www.w3.org/TR/xhtml2/

A tako? Nisem imel cajta prestudirat tole o xhtml 2, zdi se mi pa da bo standard prinesel dosti novega v primerjavi z xhtml1.1 (se vedno govorim na podlagi netemeljitega branja).
Moje izkusnje z xhtml-om niso bile pozitivne, zato sem tudi takoj predlagal xhtml 2, vendar pa kot vidim, bo potrebno se kar nekaj casa pocakati.

Aha, tako sem tudi sam mislil in bil navdusen ob branju enega clanka kjer se je govorilo kako je xhtml kompatibilen z vecino browserjev, vendar pa edino ob pogoju da je well formed. Vse lepo in prav, dokler nisem prisel do procesa validacije, ki mi je kar naprej nasteval errorje.
Potem mi je koncno uspelo narediti well formed xhtml, a glej ga zlomka; netskejp je spet kodo prikaozoval po svoje oz. narobe.

Ja, no, OK, vendar pa v cem je potem poanta? Za kaj sploh potem rabimo xhtml?

in se tole:
I'm not sure that I think neater is the word I would choose. The standards body prefers to call it well-formed. The advantages of XHTML are many, although they may not be obvious at first.

Really, XHTML is little more than HTML 4, but with strict enforcement of the SGML tag-style markup, which we all know as XML. Simply put, HTML is broken by nature. It is not well-formed, and thus it is not DOM friendly, not data friendly, and as we all surely know, not browser friendly.

XML, on the other hand, is completely DOM friendly. Though still in its infancy, it is also quite browser-friendly. And who wouldn't agree that XML is extremely data friendly? All this is made possible by using a simple set of syntactical rules, and enforcing them strictly.

So, by merging HTML and XML, you get a data document (which is what HTML was always intended to be) that represents document markup, and does so without breaking its ability to be treated as data.

So what we end up with is a much neater document (to use your word) that browsers, or other apps, can read without complex, bug-ridden parsers, making browser compatibility far more tangible than the mess we have today. But it doesn't stop there...

For instance, in an XHTML document where you provide the latest headlines, I can make an XML parsing script that pulls only the headlines I want from your page.

Or if I have three sources that provide XML feeds of data (RSS blogs, maybe?) I can directly include their XML (unedited) into my XHTML document and apply my CSS or XSL to format it, eliminating the need for all the server-intensive code that would normally be used to translate three independant data sources into one consistent HTML document.

Or, lets say I have an web page where everything pretty much stays the same, but one line of text will change daily. Using HTML, that would mean setting up markers in the file (using comments) to identify what section to edit, as well as an irritating search algorythm. Or worse, some over-zealous developer will get the department to move the whole thing to a PHP or ASP or (insert app-server here) enabled web server to run the whole thing as a script for one line of text to change! But with XHTML, a single script could easily identify that line using a tag's ID attribute, and alter its contents, and even do all this over FTP in one swift automated motion.

All this just scratches the surface of what makes XHTML a good idea...

moj source je vsaj XHTML 1.0 Transitional, če ne že Strict!

xml je čist nekej drugega... in bi blo boljs odpret drugo temo... sicer smo pa glede xhtmlja že vse povedal.. right ? ;)


XMLje men tko... nerodn :) ne maram ga kej preveč... čeprov ga bom zdejel ponucal za en projekt.....

dnaps: točno tako... kot sem že reku... men se zdi ful neroden... so mi flat-text DB bolj pri srcu..