just-for-funn Posted November 10, 2010 Report Posted November 10, 2010 Am vazut de multe multe ori ca se pune pe aproape toate siturile<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-gb" xml:lang="en-gb">Dar nam nici o idee de ce si cu ce ma avantajeaza daca pun si eu la mine pe site asta! Care ma puteti lamuri? Quote
Mish Posted November 10, 2010 Report Posted November 10, 2010 just-for-funn , ultimul avertisment:Daca mai vii cu titluri idioate iti iei ban 2 luni . Quote
ripoff Posted November 10, 2010 Report Posted November 10, 2010 When using xHTML, the first line in your document should look like this:<?xml version="1.0" encoding="iso-8859-1"?>This is to tell the browser what type of encoding to use when translating your pages into something that’s readable by humans and speech synthesizers.<!DOCTYPE>No, I’m not yelling at you by typing that in ALL CAPS. That is actually how it looks in the tag.The doctype specifies what type of document you are creating, and there are three different doctypes in xHTML…xHTML 1.0 Strict<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">If you look at the source code for practice1.htm, you’ll see that “strict” is what we’ve been using in the practice exercises. This is because I believe in learning things right the first time, without picking up bad habits along the way. This is also why I chose to teach xHTML while leaving HTML alone, because HTML is too lenient and allows people to pick up a lot of bad habits, which would only make it harder for you to make the switch to xHTML, once old-school HTML gets phased out completely.If you find it too difficult to work with xHTML “strict,” you may decide to use…xHTML 1.0 Transitional<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">The “transitional” doctype is more lenient because it allows you to use some of the more deprecated (outdated) HTML, while still having the control that xHTML gives you.Personally, I prefer “strict” when I’ll be writing all of the code for a page myself, but “transitional” can be useful when multiple people with less coding experience will be adding content to the site.xHTML 1.0 Frameset<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">I feel I would be negligent to omit this one, although I strongly recommend that you never use a frameset. They are horrible for search engines and horrible for accessibility, and there is never a need to use one.If you feel that a frameset is handy for adding navigation that will be the same on every page, you can do the same thing with “server-side includes.” With includes, you can update the content in one file, and it will be a part of every page where the include was inserted.I will explain how to use server-side includes in a future tutorial. For now, let’s continue with the anatomy of a web page.<html>This starts the actual document, as the xml and doctype declarations aren’t actually part of the document, but rather, they define the encoding on the page and what type of document it is.The <html> tag should include the xmlns attribute, which stands for “xml namespace”. It’s also good to include what direction (dir) the text is flowing, ltr meaning “left to right” and rtl meaning “right to left”, the latter of which is used for languages such as Hebrew or Arabic. Finally, the lang attribute will help browsers display text better, especially if it’s something other than English.A typical <html> tag that you can copy and paste into any xHTML web page that will be written in English:<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr" lang="en-US">Other “lang” values you can use are:en-GBen-AUes (Spanish)fr (French)it (Italian)pt (Portuguese)de (German)ru (Russian)ar (Arabic)zh (Chinese (Mandarin))he (Hebrew)ja (Japanese)ko (Korean)Why differentiate between “en-US”, “en-GB”, and “en-AU”? Because some aural screen readers will actually read in an American, British, or Australian accent, depending on which one you specify.(sursa ..some html manual) Quote
