Monday, March 30, 2009

Lead Post resume error

This Week Tasks - Balaji

Tasks

30/3/09

31/3/09

1/4/09

2/4/09

3/4/09

4/4/09

5/4/09

Total

Collect Email – PC Dealers

25

25

25

25

25

25

25

175

Collect Email – Part Time

10

10

10

10

10

10

10

70

Cold Calls – CPC

5

5

5

5

5

5

5

35

Cold calls – M4U

5

5

5

5

5

5

5

35

Send Emails

100

100

100

100

100

100

100

700

Directory Listings

5

5

5

5

5

5

5

35

Other Tasks

Set Up Many4indians Blog

Complete the Master Excel sheet

Finish the financial sheet

Finish the mahe tracking sheet

Integrate the PayPal with far minds site

Integrate the PayPal in CPC & M4U sites

Complete Lead SRS module

Complete Simho SRS Module

Complete Dynamic SRS Module

Tutorial for Price List in CPC

Dealers CPC sales Mailer Creation

www.manyforyou.com 136 Errors, 75 warning(s)

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Warning Unable to Determine Parse Mode!

    The validator can process documents either as XML (for document types such as XHTML, SVG, etc.) or SGML (for HTML 4.01 and prior versions). For this document, the information available was not sufficient to determine the parsing mode unambiguously, because:

    • the MIME Media Type (text/html) can be used for XML or SGML document types
    • No known Document Type could be detected
    • No XML declaration (e.g ) could be found at the beginning of the document.
    • No XML namespace (e.g ) could be found at the root of the document.

    As a default, the validator is falling back to SGML mode.

  2. Warning No DOCTYPE found! Checking with default HTML 4.01 Transitional Document Type.

    No DOCTYPE Declaration could be found or recognized in this document. This generally means that the document is not declaring its Document Type at the top. It can also mean that the DOCTYPE declaration contains a spelling error, or that it is not using the correct syntax.

    The document was checked using a default "fallback" Document Type Definition that closely resembles “HTML 4.01 Transitional”.

    Learn how to add a doctype to your document from our FAQ.

  3. Info No Character encoding declared at document level

    No character encoding information was found within the document, either in an HTML meta element or an XML declaration. It is often recommended to declare the character encoding in the document itself, especially if there is a chance that the document will be read from or saved to disk, CD, etc.

    See this tutorial on character encoding for techniques and explanations.

↑ Top

Validation Output: 136 Errors

  1. Error Line 2, Column 1: no document type declaration; implying ""
    <html>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  2. Warning Line 5, Column 70: NET-enabling start-tag requires SHORTTAG YES
    …t/style.css" rel="stylesheet" type="text/css" />

    The sequence can be interpreted in at least two different ways, depending on the DOCTYPE of the document. For HTML 4.01 Strict, the '/' terminates the tag '). However, since many browsers don't interpret it this way, even in the presence of an HTML 4.01 Strict DOCTYPE, it is best to avoid it completely in pure HTML documents and reserve its use solely for those written in XHTML.

  3. Error Line 6, Column 23: document type does not allow element "STYLE" here