New pages should be html5 or xhtml5, not the older obsolete stuff anymore. No browser out there needs us to generate anything old.
I'd make sure my pages are valid html or xhtml, the rest will sort itself out.
1:42 pm on Feb 5, 2014 (gmt 0)
And unless you are serving your pages as 'application/xml+xhtml', and you probably are not, you shouldn't be using XHTML either.
4:20 pm on Feb 5, 2014 (gmt 0)
and you probably are not
Speak for yourself: I do serve polyglot html5 as xml on any new project I do.
5:22 pm on Feb 5, 2014 (gmt 0)
swa66, most people do not.
5:27 pm on Feb 5, 2014 (gmt 0)
@swa66 Yes, I did at one time, too, but as @Fotiman pointed out, most people don't and I'd almost bet money @toplisek doesn't either.
2:43 pm on Feb 6, 2014 (gmt 0)
I have and issue that search engine reported me to use <meta http-equiv="content-type" content="text/html; charset=UTF-8"> as they have issue with queries and showing special characters.
6:51 pm on Feb 6, 2014 (gmt 0)
Both meta types are equivalent and work in all browsers. Looks like your search engine is the problem.
8:28 am on Feb 7, 2014 (gmt 0)
Will be mistake if I use both of them and all characters will be correctly seen? <meta http-equiv="content-type" content="text/html; charset=UTF-8"> will be seen by search engine and <meta charset="UTF-8"> for all other
3:52 pm on Feb 7, 2014 (gmt 0)
I don't think anything will break but it's duplicated effort.
What search engine is this?
5:04 pm on Feb 7, 2014 (gmt 0)
I'm sorry but it is hidden. What is actually wrong with search engine that characters are not working?