Great job!! :cool:
Great job!! :cool:
Good work. :tup:
Well as usual, you can't expect to have something that's less outstanding than this FAQ from a brilliant HTML/XHTML expert like Tommy! I had the chance to see almost how long it took you to make this one and I can see it was amazing how fast you were able to accomplish it! this shows that you really master every tiny detail about Mark up stuff... Great FAQ buddy :tup:
Great post. People shouldn't forget about good old-fashioned html.
Great FAQ - one of the best posts I have ever seen. I definitely learned a few things here. Thanks!
Thanks, cracking explantion.
Tommy. You must have a massive hard on for all the acolades . You have done a fabulous job and I thank you also.
The section concerning "validation of mark and spell checking "concerned me a little.
We are all aware of using the spell check, some are great and others totally useless depending on content but,you say " invalid mark-up can confuse browsers, search engines and other user agents." The results you named and thanks.
Y'know I'm English. The way i spell certain words often varies considerably between English(UK) and English (USA). Do the search engines and browsers take this into consideration or to I need to start writing like a 'Yank'. I ask because most search engines and browsers are predominantly American are they not?
I used spell checking as an analogy, because for most professionals it is natural to make sure that there are no embarrassing typos before you publish anything. For some reason, web professionals don't seem to think it's equally natural to 'spell check' the markup.
Whether you use English or American spelling is up to you. The search engines as such don't care. They don't 'understand' what they are indexing. What it is about is the people using the search engines to find information. If a majority of them search for 'tires' and you have written 'tyres', your page may not be found.
If you want to reach the greatest number of people, you can try to use both spellings in your document. Either as in 'we sell quality tires (tyres) at low prices', or by using content negotiation to serve the page with UK or US spelling depending on the visitor's Accept-Language header.
Fy Fan du ar en duktig djavel. Synd att jag ar for lat att ta reda pa de ovriga svenska bokstaverna.
Tack for allt fran the baldchemist. ( en engelsman som kan diit sprak)Vi ses i sverige nan gang. Hej sa lange
A very useful one. Thanks a lot.
Great stuff. Some of us really NEED IT! Thanks Tommy.
Thanks for this beautiful article. I am very much impressed by this. The article is explaining the very basic to modern terms and things about the HTML with same lucidity.
Wow, that was great! I never knew the difference between <strong> and <b> and between <em> and <i>.
Here's a question: if you want to completely separate presentation and content, what would the appropriate way of making a piece of text bold in the midde of a paragraph where the semantic <strong> would not be appropriate? Adding a <b> would be purely presentational, therefore it would not work in this case-- <b> has the same overall purpose as something like <font size='4'>, right?.
No. There are certain typographical conventions that require that text be bolded or italicised without it carrying any additional semantic meaning. A frequently-cited example is that people tend to italicise the names of ships. Now, you could either <span class="ship">The Mary Rose</span> or <i>The Mary Rose</i> - but only one of those will remain italicised when CSS in unavailable.
Tommy can probably word this better than I have :)
Olly explained this very well, I think.Quote:
Originally Posted by mattalexx
STRONG implies strong semantic emphasis, not boldfacing.
B is suitable if there is a typographic convention to fall back upon, i.e., if the piece of text should stand out in some way even in non-CSS browsers.
If neither of those conditions apply, use a CLASS and define the styling with CSS.
As always, AutisticCuckoo, provides useful insight about the technologies we use every day but are not REALLY sure about the hows and whys...
Thank you AutisticCuckoo once again...
P.S. I only wished you didn't have to "shut down" your personal website. Your articles there were pretty fascinating...nice to continue providing for the rest of us in your personal time!
I think html still long will live :)
Great usefull information! Only one more item to add to the FAQ.
I'm such a newb that I think my html code is so awsome that I want to hide it so nobody else on the planet can rip off what they could do better from scratch in 15 minutes. How do I do that?:lol:
You are right, 'how do I stop others from viewing my markup' is a fairly common question for beginners. They've toiled with their design for days and don't want anyone to copy their singularly brilliant HTML.
I know you meant this in jest, but I think putting the answer into this FAQ may be a good idea.
A browser needs to 'see' the HTML, CSS and so on in order to display the page. If the browser can see it, so can people.
There are various ways to make it slightly more inconvenient to see the code, by obfuscation and a few other tricks, but all they do is slow thieves down for a few seconds. There is no cross-browser way of disabling 'view source', and there shouldn't be.
Content (text, images, etc.) is automatically copyrighted as soon as it is created. That doesn't prevent theft, but it gives you legal leverage to go after the thieves and seek compensation.
Hello Autistic Cuckoo,
Chris Pederick's Developer Toolbar for FireFox has this feature "View Generated Source". Enough said...
this is great dude!!!!!!!!!!!!!!!!!!!!!!!!! i knew a lot but hum...thought i did ..lol!!!nice!
I had a thick book to read when i was learning html in college and thought that i know everything about html... but jeez seeing this thread i think i have lot more to learn. Great post, its gonna keep me busy for a while.
somebody said it right: There is no end to gaining knowledge.
Thanks Tommy! Brilliant! Actually read it twice and I'm sure I will reference it in the future.