Html errors

HTML & CSS
1

I am validating my new site. I get some errors but not sure how to correct them.

Line 20, Column 80: Bad value text/html; charset=ISO-8859-1 for attribute content on element meta: iso-8859-1 is not a preferred encoding name. The preferred label for this encoding is windows-1252.
<head><meta http-equiv=“Content-Type” content=“text/html; charset=ISO-8859-1” />

Line 279, Column 111: End tag br.

lorum ibusm</br> lorum ibusmlorum ibusm</h5>

Line 226, Column 50: No space between attributes.

				&lt;a href="http://www.google.com target="_blank""&gt;

:email:
Error Line 226, Column 56: Quote " in attribute name. Probable cause: Matching quote missing somewhere earlier.

				&lt;a href="http://www.google.com target="_blank""&gt;

:email:
Error Line 226, Column 57: Quote " in attribute name. Probable cause: Matching quote missing somewhere earlier.

				&lt;a href="http://www.google.com target="_blank""&gt;

:email:
Warning Line 226, Column 58: Attribute _blank"" is not serializable as XML 1.0.

				&lt;a href="http://www.google.com target="_blank""&gt;

:email:
Error Line 226, Column 58: Bad value http://www.google.com target= for attribute href on element a: Whitespace in host component. Use %20 in place of spaces.

				&lt;a href="http://www.google.com target="_blank""&gt;

Syntax of IRI reference:
Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.

Error Line 226, Column 58: Attribute _blank"" not allowed on element a at this point.

				&lt;a href="http://www.google.com target="_blank[B]"[/B]"&gt;

Attributes for element a:
Global attributes
href
target
download
rel
hreflang
type

2

You need an extra quote here:

<a href="http://www.google.com[COLOR="#FF0000"]"[/COLOR] target="_blank">

Also, target=“” is deprecated and should ideally be avoided. It depends on what doctype you are using whether you will get a warning for it or not, though.

3

I do not understand why i get _blank""> in my html there is no double quote.

What is wrong with<br/>

Is this okay to use ?, as i get an error : meta http-equiv=“Content-Type” content=“text/html; charset=ISO-8859-1” />

4

okay, what could i use instead of target=“_blank” ? What is wrong with my <br> tag ?

5

One more question. Is it ok to upload a site to another domain for testing out errors- or could it harm SEO in someway ?

6

What is wrong with my <br> tag ?

exactly! you have </br>

also I would check the source code that’s generating your HTML, or maybe the data you are using. My theory is, it generates only an HREF. Target is a different attribute. So, if I am correct whats happening is you are sending this string : ‘http://www.google.com target=“_blank”’ which is being placed in ‘href=“$yourString”’ … and thus ‘href=“http://www.google.com target=”_blank""’

perhaps the string you send should look like : ‘href=“http://www.google.com target=”_blank’ but you wuld have to check both your data and your generating source

7

Sorry, but do sure what you mean by “data and your generating source”

8

Nothing. When you use a target attribute you reduce the options available to your visitors. If they want to open a link in a new tab or window then they will right click on the link and select the appropriate option for where they want to open the link. If you use that attribute then you reduce their choices on where to open it from three to two unless they know how to override your obsolete code in their browser.

You should be trying to make things easier for people visiting your site - not harder. When you make things harder for your visitors by reducing their choices they will leave your site and go somewhere that lets them choose to do things the way they want.

Trying to dictate where links open was something done back in the 20th century along with placing hit counters on the page and various other things that make a site today appear very ameteurish or extremely dated.

9

Thanks for your reply. I will not use target then. The reason why i want to use it, is i am afraid they will never find back to my page, If they click on 10 pages on the other site. They wil have to hit back a couple of times.

10

The question then would be, do you really need those external links? Why are you sending them to other sites?

11

yes, really do did to link to that page :confused:

<head><meta http-equiv=“Content-Type” content=“text/html; charset=ISO-8859-1” /> what wrong here ?

12

Because “_blanl” etc. are deprecated now, if you really want to have it, you could use JS instead.

<head><meta http-equiv=“Content-Type” content=“text/html; charset=ISO-8859-1” /> what wrong here ?

I don’t see a problem with it. It’s not an error. Personally, I prefer charset=utf-8

13

It’d probably help if I could see the code itself, for those other errors though it seems like there might be a mismatch occurring.

However, the ISO-8859-1 message might be just a “warning” in the Validator; ISO-8859-1 and windows-1252 are very similar encodings and the browser might assume the latter hence the error. Though you’d probably be better with declaring UTF-8. Also you could have forced the Validator to use: ISO-8859-1 if you really wanted though it’s not usually done.

14

Robert, could you write what you are using with utf-8, btw it is a danish site does that mean anything ?

Is there a way to post link to my site, without google can see it ? would really like to show the site, and the problems i have. But i dont want it to show up when somebody google the site.

15

Probably the best solution is to save the file as UTF-8 itself, and use UTF-8 as the charset value since the document will be written using the Danish alphabet and some letters may have diacritic signs.

Perhaps the web editor you were using wasn’t using the same encoding. UTF-8 can be used for all languages and is the recommended charset on the Internet.

I use the encoding declaration of the XML declaration on the first line of the page: <?xml version=“1.0” encoding=“UTF-8”?> though you may not want to.

I’d suspect you’d be better off using: <meta http-equiv=“Content-type” content=“text/html;charset=UTF-8” /> since you be likely to be serving the file as ‘text/html’.

16

my understanding is for HTML5 you can only use charset=utf-8, and should not use charset=ISO-8859-1

I read this just a few days ago, I don’t remember where…

17

[font=verdana]It really depends what character set your editor is using, but that is no different to earlier versions of HTML and isn’t specific to v5. If you are confident that your editor is saving in UTF-8 then it’s fine to use that. But if you’re not sure, it’s better to play it safe and use ISO-8859-1 or similar, and then you won’t run the risk of characters being wrongly encoded.

The W3C documentation giving examples of how to specify the charset says:
In each of the examples below, unless otherwise indicated, substitute the appropriate charset name for where you see “UTF-8”.
which I would take as good evidence that they don’t require you to use UTF-8.[/font]

18

What about on Tablets and other mobile devices ? I dont get, why in some cases it is not okay to use target_blank. Or is there some cases it is ok ? What about giving the user an option alert box ?

19

The target attribute was deleted from HTML in 1997 when it was decided that it is better to give your visitors a choice of where they want links to open. Even before then you could right click on a link to choose whether to open it in the same window or a new window. Now some browsers give the choice of same tab, new window in front, new window in the background, new tab in front, or new tab but keep the current one open. Specifying a target has the effect of removing one of those choices for those of your visitors who don’t know how to disable the target attribute completely in their browser.

An alert box is a tool for debugging JavaScript. In most browsers it displays a checkbox allowing all subsequent alerts to be turned off, in others it displays a checkbox to allow JavaScript to be completely turned off for the specific page. It should never be used on a live web page.

There are NO cases where using target are okay - if there were then the attribute wouldn’t have been deleted from HTML back in 1997. You should ALWAYS give your visitors the option of where to open pages and you do that by NOT specifying a target.

20

Deleted ? Is is still here in HTML5 http://www.w3.org/TR/html5/browsers.html#valid-browsing-context-name-or-keyword and http://www.w3.org/TR/2010/WD-html5-20100624/text-level-semantics.html#the-a-element

I still dont really understand why it is so bad. But it is valid html right ? It is just “your” opinion that it is not userfriendly, right ?