W3C Validation Problems

[Mike]

http://www.calgarymike.com/content/fsbo.html

After having validated a couple of pages I'm completely stumped as to why I
get this message. I don't have a line counter in my program (Arachnophia)
and have counted manually, but I can't see a thing as to why I'm getting
this message.

Sorry, I am unable to validate this document because on lines 36, 44, 52,
60, 68, 75, 109, 126, 131, 144, 154, 160, 178, 244, 247, 257, 271, 287, 300,
320, 335, 357, 363, 369, 377, 385, 399, 435, 441, 446, 458 it contained one
or more bytes that I cannot interpret as utf-8 (in other words, the bytes
found are not valid values in the specified Character Encoding). Please
check both the content of the file and the character encoding indication.

Any help would be appreciated.

[Lorenz Haas]

Mike wrote:

Any help would be appreciated.

Well, after "without listing it with a real estate agent.�" you have a mad
character, I don't know which. Just remove it, and wow, you won't have
troubles anymore.

Lorenz

[Adrienne]

Gazing into my crystal ball I observed Lorenz Haas <ne**@lorenz-haas.de>
writing in news:42**********************@newsread4.arcor-online.net:

Mike wrote:

Any help would be appreciated.

Well, after "without listing it with a real estate agent.�" you have
a mad character, I don't know which. Just remove it, and wow, you won't
have troubles anymore.

Lorenz

Possible quotation marks (the ones with the curly cues), or trademark, or
some other character. Often a word processing environment will put these
in. IIRC, Dreamweaver puts in TM badly and causes this problem.

--
Adrienne Boswell
http://www.cavalcade-of-coding.info
Please respond to the group so others can share

[David Ross]

Mike wrote:

http://www.calgarymike.com/content/fsbo.html

After having validated a couple of pages I'm completely stumped as to why I
get this message. I don't have a line counter in my program (Arachnophia)
and have counted manually, but I can't see a thing as to why I'm getting
this message.

Sorry, I am unable to validate this document because on lines 36, 44, 52,
60, 68, 75, 109, 126, 131, 144, 154, 160, 178, 244, 247, 257, 271, 287, 300,
320, 335, 357, 363, 369, 377, 385, 399, 435, 441, 446, 458 it contained one
or more bytes that I cannot interpret as utf-8 (in other words, the bytes
found are not valid values in the specified Character Encoding). Please
check both the content of the file and the character encoding indication.

Any help would be appreciated.

When you get that message, above it is a box with the heading
"Revalidate With Options". Select the checkbox for Show Source and
then select the Revalidate button. You will then get the same
"Sorry, I am unable to validate this document" message. Underneath
that message will be a listing of your HTML with line numbers. The
lines indicated in the message will be replaced with
#### encoding problem on this line, not shown ####

You will have to compare that listing with the actual file on your
own computer. On your computer, the affected lines will contain
special characters that are not valid in the UTF-8 character set.
Replace those characters with the HTML 4.01 entity references. See
<URL:http://www.w3.org/TR/REC-html40/sgml/entities.html>. Use the
entity names with an ampersand (&) in front and a semi-colon (;) at
the end. Don't use the character references (the numeric form).
That is, for example, use &copy; for the circled-C copyright symbol
instead of ©.

--

David E. Ross
<URL:http://www.rossde.com/>

I use Mozilla as my Web browser because I want a browser that
complies with Web standards. See <URL:http://www.mozilla.org/>.

[Alan J. Flavell]

On Sat, 25 Jun 2005, Mike wrote:

http://www.calgarymike.com/content/fsbo.html

After having validated a couple of pages I'm completely stumped as
to why I get this message.
You're claiming to be encoded in utf-8, but in fact that's not so.

If I force iso-8859-1 as the encoding there are 408 syntax errors
reported. If I force windows-1252 then there are 406 syntax errors
reported. You appear to be using (or trying to use) XHTML/1.0
Appendix C without understanding XHTML. My recommendation would be to
use HTML/4.01 unless and until you have an overwhelming reason to use
XHTML and know how to use it.

My hunch is that this thing is probably encoded in the proprietary
windows-1252 encoding (best avoided), but with so many other syntax
errors present it's hard to focus on the detail.
Sorry, I am unable to validate this document because on lines 36,
44, 52, 60, 68, 75, 109, 126, 131, 144, 154, 160, 178, 244, 247,
257, 271, 287, 300, 320, 335, 357, 363, 369, 377, 385, 399, 435,
441, 446, 458 it contained one or more bytes that I cannot interpret
as utf-8 (in other words, the bytes found are not valid values in
the specified Character Encoding). Please check both the content of
the file and the character encoding indication.

Well, it told you exactly what was wrong and what to do. Unicode
security requirements make it a mandatory rule to reject documents
claiming to be utf-8 and failing to pass utf-8 sanity check, and I'd
say that is very wise. It's a bug in Mozilla/Firefox that it's
willing to have a try at displaying an invalid utf-8 document: it
ought to throw an alert first (before possibly offering to do a fixup
at the reader's own risk).

[Jim Moe]

Mike wrote:

http://www.calgarymike.com/content/fsbo.html

After having validated a couple of pages I'm completely stumped as to why I
get this message. I don't have a line counter in my program (Arachnophia)
and have counted manually, but I can't see a thing as to why I'm getting
this message.
I have that program and it is easy to add line numbers.
Sorry, I am unable to validate this document because on lines 36, 44, 52,
[...]
check both the content of the file and the character encoding indication.

As others have mentioned you have a spurious character at the end of
those lines. It is a #160 (hex a0), which would be "&nbsp;" if it were
escaped properly.
Those are the least of the validation problems. There are a vast number
of serious errors on that page. I have to admire browsers that can
coherently display such a mess. Use
<http://www.htmlhelp.com/tools/validator/> to see what I mean. It ignores
the encoding errors.

--
jmm dash list (at) sohnen-moe (dot) com
(Remove .AXSPAMGN for email)

[Andreas Prilop]

On Fri, 24 Jun 2005, David Ross wrote:

On your computer, the affected lines will contain
special characters that are not valid in the UTF-8 character set.
There is no such thing as a "UTF-8 character set".
Don't use the character references (the numeric form).
That is, for example, use &copy; for the circled-C copyright symbol
instead of ©.

You are clueless. Please read first
http://ppewww.ph.gla.ac.uk/~flavell/charset/
http://ppewww.ph.gla.ac.uk/~flavell/...checklist.html
http://www.cs.tut.fi/~jkorpela/chars.html
before you try to write your next posting.

--
Top-posting.
What's the most irritating thing on Usenet?