NOTE: This page is a .txt page on the Website and not an .htm page.

The HTML FRAG(ment)

  The Fragment probably gives more people problems than any other item.

  It must be *perfect* or it simply doesn't work. And it must be shown
somewhere, so that people can copy *Your* ring fragment onto their Web
page.

  Essentially, there are three ways to present the fragment to
prospective ring members. On your Webring page you can display the
fragment as follows:

  1. Surround the code with the HTML tag <XMP> and </XMP>.

  2. Change the < and > signs to their symbolic entity of &lt; and &gt;
throughout your code frag and it will display correctly on your Web page.

  3. Put you code on a "Text" Web page, such as this page, and it will
display exactly as you type it.

NOTE: The HTML tag </XMP> and </XMP> is supported in today's
browsers but is reportedly being phased out and will not be
supported in the future. It will be replaced with <PRE>,
which, as yet, DOES NOT WORK in Netscape 4x.

1. EXAMPLE of <XMP> code:

<XMP>
<!##--BEGIN AMERICA'S LAKES WEB RING CODE---------->
<A HREF="http://www.jackson-lake.com/lakewr.htm">AMERICA's LAKES Webring</A><BR>
This <A HREF="http://www.jackson-lake.com/lakewr.htm">America's Lakes WebRing</A> site is
owned by <A HREF="mailto:________________">______________</A>.<BR>
Click for the [ <A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=___&prev"
TARGET="_top">Previous Page</A> ]
[ <A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=____&next"
TARGET="_top">Next Page</A> ].........
</XMP>

  If you do the above, and place in on your HTML Web page, it will show
up correctly as *Code* which can be copied and pasted.

  The second method is to change all the < and > signs, which surround
HTML tags to their symbolic entities, which will also make it show up as
*Code* on your Web page.
The symbolic entity for < is &lt;
and 
the symbolic entity for > is &gt;
  Shown below is how your webring code would look with the symbolic
entities substituted for the < and > signs:
2. EXAMPLE:

&lt;!##--BEGIN AMERICA'S LAKES WEB RING CODE----------&lg;
&lt;A HREF="http://www.jackson-lake.com/lakewr.htm"&lg;AMERICA's LAKES Webring&lt;/A&lg;&lt;BR&lg;
This &lt;A HREF="http://www.jackson-lake.com/lakewr.htm"&lg;America's Lakes WebRing&lt;/A&lg; site is
owned by &lt;A HREF="mailto:________________"&lg;______________&lt;/A&lg;.&lt;BR&lg;
Click for the [ &lt;A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=___&prev"
TARGET="_top"&lg;Previous Page&lt;/A&lg; ]
[ &lt;A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=____&next"
TARGET="_top"&lg;Next Page&lt;/A&lg; ].........

  I prefer the change to "symbolic entity" because you can then
control line breaks so the code looks reasonable to the reader.
  If you use <XMP>, all of your Ring code becomes one big jumble
of code which is hard to decipher.

  The third way is to put a link on your Web page to the HTML frag,
which is on a separate page, and is also a *Text* page and *NOT* an
HTML page.
You would link to it this way:
<A HREF="fragment.txt">HTML Fragment</A><BR>
assuming that you named the Text page - fragment.txt - and launched
it up to your WEb site.
  Whatever you typed on the *Text* page will show up just as you
typed it, as your browser does not interpret a .txt page as HTML.
3. EXAMPLE:

<!##--BEGIN AMERICA'S LAKES WEB RING CODE---------->
<A HREF="http://www.jackson-lake.com/lakewr.htm">AMERICA's LAKES Webring</A><BR>
This <A HREF="http://www.jackson-lake.com/lakewr.htm">America's Lakes WebRing</A> site is
owned by <A HREF="mailto:________________">______________</A>.<BR>
Click for the [ <A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=___&prev"
TARGET="_top">Previous Page</A> ]
[ <A HREF="http://www.webring.org/cgi-bin/webring?ring=lakes50&id=____&next"
TARGET="_top">Next Page</A> ].........

  The above will show up on a text page with all the correct
HTML tags in place.