URL fails in W3C HTML/XHTML Validation - validation

I use the URL below in my web page in href tag and unfortunatelly whole link fails in W3C HTML/XHTML Validation.
How do I solve this problem?
http://maps.google.co.uk/maps?q=N+Z&hl=en&hnear=ABC+N4+1,+Jamaica&t=m&z=16
My page includes:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
.
.
.

You'd have to encode the ampersand (&) in URLs with &.
So your URL should look like:
http://maps.google.co.uk/maps?q=N+Z&hl=en&hnear=ABC+N4+1,+Jamaica&t=m&z=1
See info in HTML 4.01, for example. Also there is web tool which checks for ambiguous ampersands: http://mothereff.in/ampersands

You should escape/encode the URL.

Related

Sublime Doctype HTML Snippet

Is there a way that this here below ↓↓↓ can be inserted as a snippet?
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title></title>
</head>
<body>
</body>
</html>
I tried using Preferences -> Key Bindings - User but quotation marks really matters.
You can create a new snippet via Tools -> New Snippet...
You can read more about creating and using snippets here.
FYI, the HTML5 doctype is probably more appropriate and much easier to remember, simply:
<!DOCTYPE html>
Just to spell it out, so you don't need to follow links:
After selecting Tools -> New Snippet..., modify its content to the following:
<snippet>
<content><![CDATA[
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>$0</title>
</head>
<body>
</body>
</html>
]]></content>
<tabTrigger>newpage</tabTrigger>
<scope>text.html</scope>
</snippet>
The $0 between the <title> tags indicates that your cursor will end up here after triggering the snippet. If you'd like to have multiple insertion points that you can Tab between them, use $1 as the first, $2 as the second, etc., using $0 as the final spot.
Save the snippet in your Packages/User directory (it should be the default when you hit save) as newpage.sublime-snippet. To test it, open a new file, set the syntax to HTML, type newpage, and hit Tab, and you should be all set.

understanding the hotlinking of images

i have one image which works fine if reloaded in browser or if you enter in browser and click enter it will load else it will show nothing i have checked locally as well and it is not working if kept in img tag but if that image is opened seperately inh browser and then page is opened it is showing..
this is the image url
http://iv1.lisimg.com/image/1440189/600full-chae--young-han.jpg
almost all img urls of listal.com is like that.
i have tried basic image loader
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Untitled Document</title>
</head>
<body><img src="http://iv1.lisimg.com/image/2359052/600full-kim-rossi-stuart.jpg" />
</body>
is this geographically targeted??/ or something like this?
please suggest

IE8 forcing document mode as IE7 standards

For my webapplication I am using IE8 as a standard browser.Sometimes the browser is setting Document mode as IE-7 Standards.
I have already tried Servlet Headers as IE=8,IE=edge and all other settings,also my DOCTYPE is also proper.
Does anyone knows why IE is forcing such behaviour ?
You can force IE to use compatibility mode with X-UA-Compatible Meta Tag:
IE 7:
<meta http-equiv="X-UA-Compatible" value="IE=7">
IE 8:
<meta http-equiv="X-UA-Compatible" value="IE=8">
IE 9:
<meta http-equiv="X-UA-Compatible" value="IE=9">
IE look also at the page DOCTYPE:
Standards View
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>This page is NOT Rendered in Compatibility View</title>
</head>
<body>
<h1>This page is NOT Compatibility View</h1>
</body>
</html>
Compatibility View
<html>
<head>
<title>This page is NOT Rendered in Compatibility View</title>
</head>
<body>
<h1>This page is NOT Compatibility View</h1>
</body>
</html>
Standards View
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>This page is NOT Rendered in Compatibility View</title>
</head>
<body>
<h1>This page is NOT Compatibility View</h1>
</body>
</html>
Compatibility View
<?xml version="1.0" encoding="UTF-8">
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>This page is NOT Rendered in Compatibility View</title>
</head>
<body>
<h1>This page is NOT Compatibility View</h1>
</body>
</html>
Note, that last example should load as standards view in XHTML mode. But Internet Explorer interprets that XML declaration as requiring compatibility view.
I resolved similar issue like this:
<meta http-equiv="X-UA-Compatible" content="IE=8,IE=9,IE=10,chrome=1" />
Take into account IE version should start from the lowest version.

HTML5: What is the "correct" behavior for validation of unregistered <meta> tags?

The following is valid 'HTML 4.01 Transitional' according to the W3 validator:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.or/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="revisit-after" content="30 days">
<meta name="DC.Title" content="Website title">
<title>Website title</title>
</head><body></body></html>
When transforming this code to HTML5, the meta-tag underwent some changes as documented here. Thus, the following should be valid HTML5:
<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
<meta name="revisit-after" content="30 days">
<meta name="DC.Title" content="Website title">
<title>Website title</title>
</head><body></body></html>
Except that it doesn't validate as apparently meta tags are supposed to be registered now.
Problem: The W3 documentation does not list restrictions on meta-tags as a new "feature" of HTML5, but they do not validate like they did previously in HTML 4.01 Transitional.
Update: While the official HTML4 documentation does indeed not restrict the field values of the name attribute, the HTML5 draft mentions the new restriction (unlike the "differences" guide). Some posters suggest to not use meta-tags at all based on SEO arguments, but there have been many public and internal uses of meta-tags for cache control, documentation and storage purposes. Should there not be a way to turn valid HTML4 code into valid HTML5 code without relying on millions of meta-parsers to rewrite themselves automagically?
Question: What should we do in practice?
In practice, just leave the meta tags as they are. Even if the validator complains, it doesn't make a single bit of difference to anyone using your website.

IE8 - Chinese Chars - Strict vs. Transitional Doctype

Redesigning a website I've moved from
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
doctype to
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
doctype.
My content-type meta tag is:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Unfortunately, in IE8, chinese characters now show up as blank squares.
Reverting to the transitional doctype solves the issue, as does adding the following directive:
<meta http-equiv="X-UA-Compatible" content="IE=7" />
Is there another way of solving it without sacrificing proper IE8 rendering?
Edit:
Here's a minimal example:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>片瓜片南語</body>
</html>
If I remove the doctype it displays ok

Resources