changes?

Re: changes?

2012-02-02 3:24, Michael wrote:

> I was taking an HTML class and I recall my code being valid. My teacher
> marked me down because he stated it was invalid.
>
> I checked and indeed now it does show an error, but back in December, I
> didn't see this. Unless I made a mistake with the file I sent, something
> has changed.
> Did it?

I don't think there has been any significant change in this respect. 
Error messages like this have been reported in the www-validator list at 
least in 2005 and in 2007, suggesting that the validator has enforced 
the SGML comment syntax, which tends to confuse people.

> This was the line that caused it to be invalid:
>
> Error /Line 327, Column 31/: invalid comment declaration: found name
> start character outside comment but inside comment declaration
>
> |<!--Ceci n'est pas une table--*v*raisment!	|

The second occurrence of "--" terminates the comment, and then the 
letter "v" is what the message says: a name start character (a letter) 
outside comment but inside comment declaration.

In practical terms, a comment should start with "<!--" and end with 
"-->" so that there is no "--" pair between them.

The formal rule is more complicated. What we commonly call "comment" is 
formally "comment declaration", starting with "<!" and ending with ">", 
containing any number of "comments" between them, and nothing else, 
except whitespace. A "comment", in this terminology, starts and ends 
with "--". Reference: ISO 8879, clause 10.3.

It is a bit of a mystery to me why the validator says "name start 
character" here. It isn't relevant that the character is a name start 
character, or a name character, or a "*" character, or whatever. The 
relevant thing is that it is a non-whitespace character outside comment 
but inside comment declaration.

Yucca

Probelms with Persits

Re: Probelms with Persits

2012-02-05 23:55, Jens R. Rasmussen wrote:

> I have a page http://www.vinvenner.dk/adm16.asp which is validated
> positively, no errors found.

No,
http://validator.w3.org/check?verbose=1&uri=http%3A%2F%2Fwww.vinvenner.dk%2Fadm16.asp
fails to run validation, because the www.vinvenner.dk server responds 
with 500 Internal Server Error.

If I copy and paste the content as received by a browser, the validator 
reports 19 errors.

> When I include an upload from Persists however I get 19 “meaningless”
> error messages.

Apparently you have now modified http://www.vinvenner.dk/adm16.asp from 
the content that gave no validation errors.

The validation errors are caused by the presence of the <div 
id="indholdbar"> element (or, rather, start of it - it lacks an end 
tag). The element contains legacy HTML markup that does not conform to 
the declared document type XHTML 1.0 Strict. The document ends with that 
partial element, causing further validation errors (lack of </body> and 
</html> tags).

Either modify the generation of <div id="indholdbar"> so that the result 
conforms to XHTML 1.0, or change the overall markup (including the 
DOCTYPE) to HTML 4.01 Transitional.

Yucca

a more elegant fail on a kindlegen mobipocket pagebreak command

Re: a more elegant fail on a kindlegen mobipocket pagebreak command

Bowerbird <at> aol.com, 2012-02-09 00:28 -0500:

> >   <mbp:pagebreak />
> it's the kindlegen command to throw a pagebreak
> when creating a mobipocket file (for the kindle)...

Wonderful.

If you're able to, try <mbp:pagebreak></mbp:pagebreak>

Browsers don't pay any attention to "/>" in HTML pages. If you want to use
that syntax you need to use XHTML and namespaces.

> here's an example file with the offending outrage:
> >    http://zenmagiclove.com/prapr-reg.html
> and the same file, without the devil pagebreaks:
> >    http://zenmagiclove.com/prapr-vme.html
> 
> now of course your validator should _raise_a_flag_
> when it encounters such a monstrosity, but lately,
> it has been choking completely, which is not good.

Choking how? You mean reporting "Element mbp:pagebreak not allowed as child
of element div in this context. (Suppressing further errors from this
subtree."?

> perhaps you could cause it to fail more elegantly?

How?

The validator has a conforming HTML5 parser that parses markup in the same
way browser parsers do (in fact its the same parser used in Firefox).

When you feed http://zenmagiclove.com/prapr-reg.html to a browser, this is
what you end up with in the DOM:

  http://software.hixie.ch/utilities/js/live-dom-viewer/?%3Cdiv%20id%3Dchunk8%3E%E2%86%A9%0A%3Chr%3E%3Cmbp%3Apagebreak%20%2F%3E%E2%86%A9%0A%E2%86%A9%0A%3Ca%20id%3D%22table_of_contents%22%3E%3C%2Fa%3E%E2%86%A9%0A%3Cp%20style%3D%22text-align%3Aright%3B%22%3E%E2%86%A9%0A%3Ca%20href%3D%23pride_and_prejudice%3E%26lt%3B-%3C%2Fa%3E%20%26nbsp%3B%20%26nbsp%3B%20%E2%86%A9%0A%3Ca%20href%3D%23pride_and_prejudice%3E-c-%3C%2Fa%3E%20%26nbsp%3B%20%26nbsp%3B%20%E2%86%A9%0A%3Ca%20href%3D%23chapter_1%3E-%26gt%3B%3C%2Fa%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2Fp%3E%E2%86%A9%0A%3C%2Fdiv%3E%E2%86%A9%0A

  http://goo.gl/4KdTV

DIV id="chunk8"
| #text: ↩
| HR
| MBP:PAGEBREAK
| | #text: ↩ ↩
| | A id="table_of_contents"
| | #text: ↩
| | P style="text-align:right;"
| | #text: ↩
| | A href="#pride_and_prejudice"
| | #text: <-
| | #text:     ↩
| | A href="#pride_and_prejudice"
| | #text: -c-
| | #text:     ↩
| | A href="#chapter_1"
| | #text: ->
| | #text:     
| | #text: ↩

That is, everything after the <mbp:pagebreak /> is made a child node of
that mbp:pagebreak element. That's because HTML parsers don't pay any
attention to XML-isms like "/>" (self-closing tag syntax). So browsers
don't see that as an empty element -- they see it as a element with a start
tag but no end tag.

The validator is doing the right thing here by trying to alert you to
something that is seriously broken in your source. If you're serving your
content at HTML and want to make sure it's going to work the way you
intend, don't use <mbp:pagebreak />. Otherwise use XHTML5 and namespaces.

  --Mike

--

-- 
Michael[tm] Smith
http://people.w3.org/mike/+

python library for markup validation soap service

py_w3c is python package for markup validation using w3c soap service. 
Supports all three methods of validation: url, file or fragment.
http://pypi.python.org/pypi/py_w3c/0.1.0
Kazbek

Add Subject Here: new equipment

NOTE: Whenever possible, give the address of the document you were checking..

I am very happy with the way things have gone. Punctuality, friendliness and competence.

However, I would question passing your Company to an associate or friend due to the way your complaints
service ignored my complaint about your mobile service and did not give me feedback on my remarks with
regard to the said complaint. 

I feel the mobile service has been questionable, especially with regard to some of the bills I have received
(the amount)  and as explained, the attitude of some of your staff. They make things personal, which is
fine, but does not sit comfortably with the passing on of a Company to other people.

I hope this was of help.

Regards

Jane Austwick
27, LS17 8BD

Tel: 0113 2888832

Sent from my BlackBerry smartphone from Virgin Media

Add Subject Here

Re: Add Subject Here

2012-02-13 13:29, Thomas Bryder Steffensen wrote:

> Don't realy get this error:
>
> /Line 124, Column 257/: non SGML character number 3
>
> |…t og individuelt grafisk design.<br />**Flash og CMS-udvikling har helt fra sta…|
>
> It seems that the word "Flash" embedded in a span-tag causes the error
> ... Does this simply mean that we can't write Flash???’

No, the error message is accurate, though perhaps a bit difficult to 
interpret. It says that the document contains the character U+0003, 
which is not permitted in HTML. That character is displayed between the 
asterisks in a sense, though being a control character, it does not have 
a glyph. Browsers may display it e.g. as a small box containing the 
digits 0003. Removing the character should fix the problem.

> LINK:
> http://validator.w3.org/check?uri=http%3A%2F%2Fwww.in-demand.dk%2F&charset=%28detect+automatically%29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.2

The page validates now, so I suppose you already fixed the problem.

Yucca