Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

how to test a web page in MSWord


  • Please log in to reply

#1
davidmcb

davidmcb

    Member

  • Member
  • PipPip
  • 31 posts
I am a novice, trying to write my first web page, to be hosted on a web hosting site. Ultimately, I hope to build a real site with ecommerce, photo albumns, blog, etc. This is the beginning. I have written this pathetic scratch of code using Word 2003, but when I click on "display as a webpage", I just get back the source html, not a web page. Guidance? TVM David

<!--msword2003 does not seem to recognize these xhtml declarations. No problem, I will just comment them out-->


<!--
<!DOCTYPE html PUBLIC “-//W#C??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” />

</head>

<img src=”C:\Documents and Settings\David- Humble Boy\My Documents\My Pictures\2007_09_17\IMG_0081jpeg” alt=”Sunset over the valley” />

<body>
<center>

<title>Loveland-Lee Vineyards</title>

<h1>align=”center” Loveland-Lee Vineyards</h1>

<p>Loveland-Lee Vineyards is the name for our family’s project to preserve, enhance, and responsibly develop a lovely patch of Napa Valley hill country. This site is under construction while the owner finishes erosion control winterization and other tasks. Please visit again in a few weeks. (Updated September 15, 2009)</p>
</center>
  • 0

Advertisements


#2
Wander

Wander

    Member

  • Member
  • PipPipPip
  • 205 posts
You could alternatively point your web browser to the .html document by typing it into the address bar.
  • 0

#3
Major Payne

Major Payne

    Retired Staff

  • Retired Staff
  • 5,307 posts
Your first major mistake is using MS Word. It is NOT a web page editor even if it saves docs in its so-called "HTML format". If it was in an html extension, any browser should have been able to display the page so commenting out the doc type is not the way to go. XHTML 1.0 is a lot more strict than the HTML 4.01 ones. You must try to be syntactically correct.

I would suggest dumping MS Word, don't even think about using FrontPage or Publisher to make your web pages. These are good picks...

Editors:

Free HTML Editors, Web Editors, and WYSIWYG Web Editors and Site Builders:
http://www.thefreeco...tml#htmleditors
HTML Editor Reviews - http://www.wdvl.com/Reviews/HTML/
Free Online Editor Tool: http://htmledit.squarefree.com/
Free Flash Website Builder (Online): http://www.wix.com/
PageBreeze (Free visual (WYSIWYG) and HTML tag/source modes): http://www.pagebreeze.com/
Notepad++ (Free source code editor and Notepad replacement that supports several languages): http://notepad-plus....net/uk/site.htm
Serif WebPlus SE: http://myrtc.blogspo...webplus-se.html

Download Trellian WebPage (Free): http://www.trellian....ge/download.htm

Mac users might want to download BBedit Lite, a more powerful, and free mac text editor: http://www.barebones...bedit_lite.html

Free Mac Web Design Software: http://web-design.lo...Design_Software

Free HTML Editors for Macintosh: http://webdesign.abo...tedmac.-0cZ.htm


This information should help you do a better page...

How to Make a Webpage:

Full Web Building Tutorials: http://www.w3schools.com/
Beginner's HTML Tutorial: http://www.htmlbasix.com/
How to Create a Webpage: http://www.make-a-web-site.com/
So You Want To Set Up Your First Site, Huh?: http://www.htmlgoodi...cle.php/3479561
http://www.w3schools...ite/default.asp

How to Start / Create Your Own Website: The Beginner's A-Z Guide: http://www.thesitewi...rtwebsite.shtml
So, you want to make a Web Page!: http://www.pagetutor...utor/index.html
Getting started with HTML: http://www.w3.org/MarkUp/Guide/
Creating your first website – Part 1: Setting up your site and project files (Adobe CS3/4): http://www.adobe.com...ebsite_pt1.html

Tableless Web Design: http://en.wikipedia....less_web_design

CSS Tutorials:

http://www.w3schools...Css/default.asp
http://www.csstutorial.net/
http://www.echoecho.com/css.htm
http://www.html.net/tutorials/css/
http://www.w3.org/St...es/011/firstcss

http://htmldog.com/guides/cssbeginner/
http://www.davesite....webstation/css/
http://www.htmlcodet...amsupp_193.html

Images, Tables, and Mysterious Gaps: https://developer.mo...Mysterious_Gaps

I also suggest using the w3c.org's validator's to check your coding:

http://jigsaw.w3.org...lidate-by-input
http://validator.w3....lidate_by_input
  • 0

#4
davidmcb

davidmcb

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
<Thanks, I will dig into your recommendations!/>
  • 0

#5
Major Payne

Major Payne

    Retired Staff

  • Retired Staff
  • 5,307 posts
You're welcome. Post back if you have problems with this related topic. Good luck.
  • 0

#6
davidmcb

davidmcb

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
OK, I am working on this but not making progress. I got Notepad++ and reentered my little page. I went to an HTML loose declaration because I was not sure which tags might be deprecated.

The big problem is that the validator chokes on letters and symbols, like quotation makes in my code. How can that be. Some of the lines are copied from Liz Castro's latest book. makes no sense to me. Below is my page of code and below that the validator's output. Clues welcome. Thx
-------------------------------------------
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR...ml4/loose.dtd">


<html>
<head>

<meta http-equiv=”content-type”
content=”text/html; charset=utf-8” />

</head>

<img src=”C:\Documents and Settings\David- Humble Boy\My Documents\My Pictures\2007_09_17\IMG_0081jpeg” alt=”Sunset over the valley” />

<body>
<center>

<title>Loveland-Lee Vineyards</title>

<h1>align=”center” Loveland-Lee Vineyards</h1>

<p>Loveland-Lee Vineyards is the name for our family’s project to preserve, enhance, and responsibly develop a lovely patch of Napa Valley hill country. This site is under construction while the owner finishes erosion control winterization and other tasks. Please visit again in a few weeks. (Updated September 15, 2009)</p>
</center>








</body>
</html>



--------------------------

Validation Output: 20 Errors
Line 7, Column 18: an attribute value must be a literal unless it contains only name characters
<meta http-equiv=”content-type”✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 7, Column 18: character "”" is not allowed in the value of attribute "HTTP-EQUIV"
<meta http-equiv=”content-type”✉
It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.
Line 8, Column 9: an attribute value must be a literal unless it contains only name characters
content=”text/html; charset=utf-8” />✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 8, Column 29: Attribute "CHARSET" is not a valid attribute. Did you mean "charset"?
content=”text/html; charset=utf-8” />✉
You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.
Line 8, Column 34: an attribute value must be a literal unless it contains only name characters
content=”text/html; charset=utf-8” />✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 8, Column 36: NET-enabling start-tag requires SHORTTAG YES
content=”text/html; charset=utf-8” />✉
The sequence <FOO /> 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 <FOO (with an implied '>'). 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.
Line 8, Column 37: character data is not allowed here
content=”text/html; charset=utf-8” />✉
You have used character data somewhere it is not permitted to appear. Mistakes that can cause this error include:

•putting text directly in the body of the document without wrapping it in a container element (such as a <p>aragraph</p>), or
•forgetting to quote an attribute value (where characters such as "%" and "/" are common, but cannot appear without surrounding quotes), or
•using XHTML-style self-closing tags (such as <meta ... />) in HTML 4.01 or earlier. To fix, remove the extra slash ('/') character. For more information about the reasons for this, see Empty elements in SGML, HTML, XML, and XHTML.
Line 10, Column 7: end tag for "HEAD" which is not finished
</head>✉
Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists (ul, ol, dl) require list items (li, or dt, dd), and so on.
Line 12, Column 10: an attribute value must be a literal unless it contains only name characters
<img src=”C:\Documents and Settings\David- Humble Boy\My Documents\My Pictures\2✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 12, Column 28: "AND" is not a member of a group specified for any attribute
<img src=”C:\Documents and Settings\David- Humble Boy\My Documents\My Pictures\2✉
Line 12, Column 36: "SETTINGS" is not a member of a group specified for any attribute
<img src=”C:\Documents and Settings\David- Humble Boy\My Documents\My Pictures\2✉
Line 12, Column 51: "HUMBLE" is not a member of a group specified for any attribute
…ocuments and Settings\David- Humble Boy\My Documents\My Pictures\2007_09_17\I✉
Line 12, Column 54: "BOY" is not a member of a group specified for any attribute
…ments and Settings\David- Humble Boy\My Documents\My Pictures\2007_09_17\IMG_✉
Line 12, Column 67: "DOCUMENTS" is not a member of a group specified for any attribute
…tings\David- Humble Boy\My Documents\My Pictures\2007_09_17\IMG_0081jpeg” alt✉
Line 12, Column 79: "PICTURES" is not a member of a group specified for any attribute
… Humble Boy\My Documents\My Pictures\2007_09_17\IMG_0081jpeg” alt=”Sunset ove✉
Line 12, Column 109: an attribute value must be a literal unless it contains only name characters
…ctures\2007_09_17\IMG_0081jpeg” alt=”Sunset over the valley” />✉
You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.
Line 12, Column 122: "OVER" is not a member of a group specified for any attribute
…9_17\IMG_0081jpeg” alt=”Sunset over the valley” />✉
Line 12, Column 126: "THE" is not a member of a group specified for any attribute
…\IMG_0081jpeg” alt=”Sunset over the valley” />✉
Line 12, Column 132: "VALLEY" is not a member of a group specified for any attribute
…081jpeg” alt=”Sunset over the valley” />✉
Line 12, Column 134: NET-enabling start-tag requires SHORTTAG YES
…1jpeg” alt=”Sunset over the valley” />✉
The sequence <FOO /> 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 <FOO (with an implied '>'). 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.
Line 14, Column 6: document type does not allow element "BODY" here
<body>✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
Line 17, Column 7: document type does not allow element "TITLE" here
<title>Loveland-Lee Vineyards</title>✉
The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).
  • 0

#7
Major Payne

Major Payne

    Retired Staff

  • Retired Staff
  • 5,307 posts
Lots of those errors are from characters your editor uses. They are probably not UTF-8, but ANSI and the character set you have is incorrect. Some editors use characters that are not to be used on web pages.

The shorttag errors are because you are ending non-closing tags with an XHTML 1.0 doctype closing. Remove the space and the "/" symbol for those. Your doctype is just a plain HTML 4.01 Transitional. Once you remove these XHTML 1.0 closing s, the other errors should disappear from the image tags.

Have to run. Do those corrections and post back with results. Will be back in a few hours.
  • 0

#8
davidmcb

davidmcb

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
I suspected charset issues, but converted the text to UTF-8 in Notepad++ and declared UTF-8?? I will not be able to work more on this until tomorrow aftrnoon. Thanks very much!
  • 0

#9
Major Payne

Major Payne

    Retired Staff

  • Retired Staff
  • 5,307 posts
You're welcome. If you need some help on error correcting, post back.
  • 0

#10
davidmcb

davidmcb

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
I still could not get through the validator, but I have been busy and not able to devote time to this. I will soon. Thx
  • 0

#11
Major Payne

Major Payne

    Retired Staff

  • Retired Staff
  • 5,307 posts
:) Word really does a job to anything you want as an HTML page. Good luck with it. You may have to load the file into a proper HTML editor, if you haven't already, and use the Code Corrector (HTML Tidy) to fix the errors for you.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP