Edited log of the L.O.S.T. workshops: Basic HTML for Librarians presented by Pascal Calarco.
Pascal_Calarco says, "Hello everyone. Thank you all for coming to this Librarians' Online Support Team (L.O.S.T.) event. This month's workshop, as you all know, is "Basic HTML for Librarians." My name is Pascal Calarco, and I'll be your workshop leader for this session."
Pascal_Calarco says, "Here is a summary of what we'll be covering in this workshop. I'll like to mention now that we will be recording a copy of the entire workshop, and it will be available to you after we finish (we can e-mail you a copy), so you need not worry about taking extensive notes during the workshop."
Pascal_Calarco says, "Also, if, at any point in the workshop you'd like to ask a question, feel free to raise your hand with the raises hand' command, and ask your question using su' so you can be heard by everyone. If you have a detailed specific question, I'd ask if you could keep it until the end of the session, when I would be happy to help you. We've a lot of ground to cover, so let's start!"
Pascal_Calarco says, "I'd first like to give you some background on the World Wide Web, HTML, some of the standards that it is based on, and what tools you can use to create your own WWW documents. "
Pascal_Calarco says, "The World Wide Web, W3, as it is sometimes known, or WWW for short, I'm sure most of you are familiar with. It is a distributed Internet application that uses a number of standard protocols, including support for older protocols like telnet, gopher, and ftp [see http://www.w3.org for more information]. "
Pascal_Calarco says, "The defining characteristics of the WWW are several. First, it is cross-platform: meaning that the WWW is accessible across many different operating systems through "browsers" such as Netscape, NCSA Mosaic, and others. These browsers are available for Windows, Macintosh, and Unix operating systems."
Pascal_Calarco says, "Second, the WWW is distributed: HTML documents are stored on computers, or "hosts," as they are referred to, across the Internet. One only has to type the "address" of the host in one's browser to get to that site. There is no one central site for the WWW, but rather each document is located on individual machines. "
Pascal_Calarco says, "Third, the WWW is a graphical environment. By this I mean that it can support the display of images as well as text. As we will see, the WWW is quickly becoming a multimedia environment "
Pascal_Calarco says, "Finally, the WWW is a Hypertext environment. The word "hypertext" was first used by Ted Nelson, an early pioneer in the development of these systems. Nelson started a hypertext project called "Xanadu" back in 1960 [for more info, see http://www.aus.xanadu.com/xanadu/ ]. In Nelson's idea, the terms hypertext or hypermedia were meant to describe an environment of non-sequential texts or other media. Nelson's ideas, with some modification, have led to the development of today's WWW."
Pascal_Calarco says, "Now let's look at "HTML" itself."
Pascal_Calarco says, "HTML, as it is commonly referred to, is an acronym for HyperText Markup Language. HTML is a subset, or child, of a broader and more established, and internationally standardized markup language called SGML, or Standard Generalized Markup Language. Both SGML and HTML were designed to describe the structure of documents, not necessarily their appearance. Thus, HTML allows for such declarations as paragraphs, titles, and bodies of text. When you work with word processors that use such tools as style sheets, you are using something similar to HTML and SGML."
Pascal_Calarco says, "Are there any questions at this point?"
Pascal_Calarco says, "I'd like to mention something about HTML standards. You probably know that there are a number of official and de facto standards in the various flavors of HTML available today. The most common denominator standard, and the one that we are going to focus on today, is what is known as HTML 2.0 [for a technical discussion of the HTML 2.0 proposed standard, see http://www.w3.org/pub/WWW/MarkUp/html-spec/]. "
Pascal_Calarco says, "HTML 2.0 is pretty much a de facto standard today. All of the most popular browsers support HTML 2.0 as a base common denominator (with a few exceptions, notably America Online's WWW browser). All of the HTML tags you will learn about today will be HTML 2.0-supported. I'll focus on HTML tags in the next section."
Pascal_Calarco says, "The HTML 3.0, sometimes referred to as "HTML+," is another standard that is being developed. Most of the tags in this specification have yet to be formally adopted by those who produce WWW browsers, although in the future this specification will most likely be as widespread as HTML 2.0 is today."
Pascal_Calarco says, "There are also standards' developed by commercial vendors of WWW browsers, most notably the "Netscape extensions" to HTML. These HTML tags have not been formally adopted by international standards bodies, and are really proprietary extensions to the HTML standards."
Pascal_Calarco says, "How exactly does one write HTML? Well, there are a number of tools that you can use to create your own HTML pages."
Pascal_Calarco says, "First, there are the HTML editors and markup tools. Currently, for MS Windows, there are about 40 different software suites [see http://www.yahoo.com/Computers_and_Internet/Internet/]"
Pascal_Calarco says, "World_Wide_Web/HTML_Editors/Macintosh/]. Some of these tools are stand-alone applications, while others are "filters" for such word processors as MS Word 6.0. I personally use a freely-available version of "HTML Assistant Pro" [see http://cs.dal.ca/ftp/]"
Celeste raises hand.
Ringer says, "Celeste .. "
Pascal_Calarco says, "Yes, Celeste?"
Celeste speaks up, "By suites do you mean programs?"
Pascal_Calarco says, "Well, yes. "
Celeste nods.
Pascal_Calarco says, "Suites usually refer to a number of stand-alone tools
that can be used inconjunction with one another."
Ringer [to Pascal_Calarco]: do you mean things likle html editors.. and b
rowsers?
Pascal_Calarco says, "Like the Website product [by O'Reilly, I think]"
Ringer nods
Pascal_Calarco says, "It is a server as well as some HTML authoring tools."
Pascal_Calarco says, "And the new Netscape Gold edition is going to include
authoring tools along with the browser."
Pascal_Calarco says, "You certainly don't need any of these tools, but they offer helpful interfaces such as buttons for the various tags, links to WWW browsers, and other features that make HTML markup somewhat easier. "
Pascal_Calarco says, "In fact, all you really need to do HTML markup is a basic text editor or word processor. HTML documents produced in any of these tools need to be in ascii (plain text) format when they are put onto a WWW server (the host computer where they reside), so really any tool will do. "
LuAnn raises hand.
Pascal_Calarco says, "LuAnn?"
LuAnn speaks up, "is Netscape Gold publicly accessible?"
Pascal_Calarco says, "From what I last saw, they [Netscape] do offer a
pre-release "beta" package, but I believe the finished product will be
commercial-only. Something less than $100, but exactly what price, I'm
not sure."
Pascal_Calarco says, "It will be interesting to see how many people will be
willing to put $100 down for something that up until now, has been dominated
by shareware and or freeware products."
Pascal_Calarco says, "Most of the browsers have been shareware and many of the authoring
tools are, or have editions with disabled features that are free. Where Netscape is now doing
well is that many new computer systems come bundled with the commercial product."
Pascal_Calarco says, "Are there any other questions?"
Someone asks, "what kind of editor are you using?"
Pascal_Calarco says, "there are lots of choices. I used Notepad in Windows."
Ringer says, "the big think is to not use a word processor and save it "
Pascal_Calarco says, "That brings up a good point, Ringer."
Pascal_Calarco says, "You must always save your document as ascii text, no
matter which tool you use to create the document."
Pascal_Calarco says, "So, if you are using something like Word or
WordPerfect be sure to "Save As.." ascii (dos) text."
Pascal_Calarco says, "A good way to see what HTML documents look like is to save WWW pages on your hard drive and then look at their HTML source code."
Pascal_Calarco says, "On most browsers, to do this you would select "Save As..." under the "File" menu. You then have the choice to save the file as source code, or as an ascii document. Select "source code," as we'll want to see the HTML tags that constitute the document."
Pascal_Calarco says, "This is a great way to see the source code of what other people have done."
Pascal_Calarco says, "This way, if you see a neat page and would like to know what tags people have used to create that effect you can look at their document and "borrow" from it."
Pascal_Calarco says, "Creative plagarism? Well, not really, since they're all standard tags."
Pascal_Calarco says, "I mean standard in the sense that they are adopted either in one of the HTML official standards, or as proprietary tags."
Airick speaks up, "do you know if lynx has a 'source' option?"
Pascal_Calarco says, "I rarely to never use Lynx, I'm afraid."
Ringer says, "you can see the source by using the \ key"
Ringer says, "saving it might be a bit tricky."
Pascal_Calarco nods, "Thanks, Ringer."
Airick speaks up, "thanks, i've always wondered. now i know..."
Ringer says, "chose p for print and then there are save options "
Airick speaks up, "or just use my local terminal for a screen dump."
Pascal_Calarco says, "Now let's move on to the basic tags."
Common declarative tags in all documents:
Pascal_Calarco says, "If you refer to the handouts I provided, you'll see a summary of the basic tags. When looking at any HTML document in source code, you'll notice that they all seem to have some basic tags, no matter what their content is, or how relatively complex they otherwise are. What I'd like to do in this section is to introduce the tags, followed by an example in an HTML document that we will construct using those tags."
Pascal_Calarco says, "You'll also notice that most tags have beginning and endings, such as <HTML> and </HTML>. You can think of these as declarations like, I'd like to start an HTML document here, and then I'm ending my HTML document here.'"
Pascal_Calarco says, "Everything in between these declarations is then HTML code."
Pascal_Calarco says, "Other very common tags are <BODY> and </BODY>. This is where the bulk of your content of the document goes."
Pascal_Calarco says, "<TITLE>, </TITLE> and <HEAD>
</HEAD> are special,
specific, declarations."
Pascal_Calarco says, "There are only specific pieces of information that you
can put in between the <HEAD>...</HEAD> tags right now. For
example, the
<TITLE> declarations go in the <HEAD>, and things like
comments that do not
display when you view the document with your browser but are visible when you
look at the source."
Pascal_Calarco says, "Everything between the first <TITLE> and
the </TITLE> will appear in the top of your browser where it tells
you what the title of
the page you are on is."
Pascal_Calarco says, "Are people familiar with what I mean?"
Ringer says, "that is in the very top of the Netscape, right?"
Pascal_Calarco says, "For example, if you
http://moo.du.org:8888, you will see
something like Welcome to Diversity University"
Pascal_Calarco says, "Yes, at the top of Netscape"
Lynn shakes her head no -- she does not have netscape
Ringer says, "what about lynx?"
Pascal_Calarco says, "Lynx. A good question. I honestly don't know. Does
anyone know if a Lynx session shows the title?"
Airick speaks up, "it does in the upper right hand corner at all times.
standard for most text based browsers"
Pascal_Calarco says, "Sometimes when you are broswing sites, you'll find sites that only have the URL at the top. These are pages that do not have a <TITLE> </TITLE> defined."
Pascal_Calarco says, "There are also tags that are more concerned with strict formatting of the text, such as <P> (paragraph), and <BR> (line break). These are the equivalents to your paragraph and hard returns in a word processor. "
Pascal_Calarco says, "Let's see what some of this looks like so far with the tags we've used."
<HTML> <!-- The start of our document -->
<HEAD> <!-- We declare the Head to start here -->
<TITLE>L.O.S.T. Demonstration Web Page</TITLE>
<!-- Remember, the title will appear at the top of the screen in the browser -->
Here is some plain text without any tags associated with it. Let's
follow it with a paragraph. <P>
Here is the new paragraph, we'll end it with a line break. <BR>
</BODY> <!-- Finished with our body of the message -->
Pascal_Calarco says, "So, along with the tags I've explained, I've also used
comments liberally throughout. This is good style, if
you expect that other
people will be looking at your source code. A few comments can make an
otherwise imposing source document much more readable."
Rui saw comments work like <! this is a comment >
Airick raises hand
Cathy speaks up, "what kinds of things might be put in comments?"
Pascal_Calarco says, "Another useful tag, or really, set of tags, are the
headings tags. They are characterized with an "H"
followed by a
number from 1 to 6. H1 is the largest, while H6 is the smallest. I've
illustrated
their use in the sample HTML document included in the e-mailed handouts. [see
also
http://www.wp.com/PascalC/LOST_sample.html]"
Lynn raises hand.
Pascal_Calarco says, "Let's see an example of the use of headers in our
document."
<HTML> <!-- The start of our document -->
<TITLE>L.O.S.T. Demonstration Web Page</TITLE>
</HEAD> <!-- Then we declare the end of the Head portion of the
page -->
<H1>Here is an Example of a Header (the largest size)</H1>
Here is some plain text without any tags associated with it. Let's
follow it with a paragraph. <P>
Here is the new paragraph, we'll end it with a line break.<BR>
</BODY> <!-- Finished with our body of the message -->
</HTML> <!-- Declare the end of our HTML document -->
Pascal_Calarco says, "Now, you'll notice that our Header tag, <H1>, is
also complimented with an ending tag."
Cathy raise hand
Pascal_Calarco says, "These are the main tags that you'll find on almost all
Web pages. Are there any questions at this point?"
Pascal_Calarco says, "I'd now like to turn to some design issues in creating
Web pages."
Pascal_Calarco says, "Should you use the Netscape
extensions? This is a
question you'll want to ask yourself early in the development of your web
pages. Although the majority of browsers in use are Netscape browsers, not
all are. That means that if you use a tag that is only supported by
Netscape, users with an NCSA Mosaic browser may see your page quite different
(literally)! An excellent resource to consult is "The Bare Bones Guide to
HTML," the address to which I've provided in your e-mail handouts. This
Guide offers a comprehensive listing of the various tags that are either part
of one of the HTML standards, or have been developed by a proprietary company
like Netscape. This first decision should be impacted by my second point,
potential audience."
Pascal_Calarco says, "If you have a specific audience for your pages, you may
be able to judge the suitability of non-standard tags within your pages. For
example, if you are designing pages for your institution, and that
institution uses NCSA Mosaic as their installed browser, then you may or may
not want to use Netscape-only tags. "
Pascal_Calarco says, "Another example. If you know that a lot of your patrons
will be connecting to your Web site via text-only "lynx" connections, then
you'll want to supply text for any graphics that you include in your pages.
Lynx, for those of you who may not know, is a Unix-based text-only WWW
browser that allows people with non-graphical Internet connections to use the
WWW. It works similarly to the Hypertext Slate [htslate] that we'll be
looking at later. The tag for text in place of graphics is used in
conjunction with the tags for images. "
Pascal_Calarco says, "You'll also want to maintain common
conventions to your
pages. Apply a standard "footer" to the bottom of your pages, for example,
which attributes authorship, date of authorship, and perhaps a link back to
your institution's main Web page. By creating a consistent, familiar set of
Web pages, you'll not only be organizing data in familiar ways for users to
access, but you'll also be providing a distinctiveness to your pages that
separate it from other sites. Consistency, cohesion, and conventions."
Pascal_Calarco says, "Another design consideration that people familiar with
publishing or graphic design will note is the use of
whitespace on your
pages. What do I mean by this? Basically, avoid having your pages
overloaded with paragraph after paragraph of solid text. For some documents
this may be appropriate -- reports or detailed documentation, for example --
but for an opening page the sight of too much text is bewildering for the
user. Use tags such as
Pascal_Calarco says, "My next consideration I'd like to address is one that
concerns the testing of your pages. Because your pages will
generally be
accessible to many people outside of your institution as well, you must also
consider what your pages will look like with different models of Web
browsers. Especially if your are using non-standard tags, you will want to
see how differently your pages look with a browser that doesn't support those
tags. Generally, browsers that don't support a tag will skip over them. You
may want to experiment with using different tags to achieve a look and then
decide which tags you'd like to use, based on what looks best overall. "
Airick raise hand
Pascal_Calarco says, "Before I mentioned using text in place of images for
support for Lynx users."
Pascal_Calarco says, "The tag for that is <ALT="explanation of the
picture">"
Pascal_Calarco says, "Now, you'll see that these two examples have different
endings."
Pascal_Calarco says, "The first, ".gif", stands for Compuserve 'Graphic Inline
Format""
LuAnn raises hand.
Ringer [to Pascal_Calarco]: so jpegs are more effecient with netscape 2
but not with other browsers?"
Pascal_Calarco says, "This becomes an interesting political story. About
a year and a half
ago Compuserve, who owns the license to the GIF format, wanted to start
getting some money for its use and so it really was no longer 'shareware'"
Airick speaks up, "how would you suggest working with graphics or is that
later. i've been told that a graphic only loads once and then is simply
resused. exactly what goes on there?"
Ringer says, "John has a question..."
Pascal_Calarco says, "Are there any more questions at this point?"
Ringer says, "John wants to know how to embed a hyertext link in e-mail"
Pascal_Calarco says, "Let me show you an example of the inclusion of graphics,
text, and footers looks like."
<HTML> <P>
Here you can tell some information about your Library:
Jane Doe, Main Branch Librarian <P>
Last revised: February 26, 1996 <P>
</BODY></HTML>
Pascal_Calarco says, "Okay, I had to condense it to fit in the slide, but here
we can see the use of a graphic image that we have of the Library at the top
of the page (it could be a scanned in picture of the Library). The text
equivalent for those using Lynx is "A picture of the Library." This graphic
is followed by a header that announces some section information about this
page. "
Pascal_Calarco says, "A Lynx session would just display IMAGE."
Pascal_Calarco says, "Its a little more friendly if the user has some idea of
what is there that they can't see."
Pascal_Calarco says, "We then follow with some unordered information about the
Library. Towards the bottom of the page, we divide off the majority of the
material with a standard footer that tells us that Jane Doe authored the
page, and when it was last revised."
Pascal_Calarco says, "Are there any questions at this point?"
Pascal_Calarco says, "For those who would like, we can spend the rest of
the session creating some HTML documents here."
Lynn speaks up, "I have looked up sites on web slates before that showed all
the HTML tags. What causes that?"
Ringer says, "I think Pascal is almost finished
Pascal_Calarco says, "Yes. The idea now is to take what we've learned, and
begin to create our own pages."
Pascal_Calarco says, "People can also construct their HTML pages here using the
@HTMLEDIT tool"
Ringer says, "For those of you who came to orientation, i provided you with an
object to do that on. If you create your html there, it is viewable
with any standard web browser "
Pascal_Calarco says, "We'll be having a follow-up session March the 5th
at Noon and 8pm"
Pascal_Calarco says, "And you can drop in here at D.U. anytime."
The next line will start directly after!
</HTML> <!-- Declare the end of our HTML document -->
Pascal_Calarco says, "What browser do you use, Rui?"
Rui says, "netscape. the latest version (i lost count)"
Pascal_Calarco says, "The strict compliance for comments need the two dashes
also."
Pascal_Calarco says, "Airick?"
Airick speaks up, "is it important to write code for most browsers. restated,
do other browsers accept those commenting forms?"
Pascal_Calarco says, "any and all broswers that conform to HTML v1.0 (quite
old now) will accept comments "
Pascal_Calarco says, "As Far As I Know *grin*"
Airick speaks up, "i mean the "<! and ->" format"
Pascal_Calarco says, "Well, Netscape often forgives not strict compliance with
standards but all comments should be constructed with the <!--
and --> for best results."
Pascal_Calarco says, "Many people like to use comment fields for things like
authorship of the page, date last revised, or personal commentary about what the part of the
HTML is meant for at that point."
Pascal_Calarco says, "In an upcoming slide, I have an example of this last
use."
Pascal_Calarco says, "They are really just a place for people to insert
commentary, without affecting the document's look itself."
Pascal_Calarco says, "Lynn?"
Lynn speaks up, "You said that the sizes are in the handout. There is no
difference in my handout between the sizes. Is this because I am on a text
only VAX server?"
Pascal_Calarco says, "That is a good question."
Pascal_Calarco says, "The document that you have in the handout is an
HTML document."
Pascal_Calarco says, "This is the "source code""
Pascal_Calarco says, "These sizes will only become apparent when
viewed through a [graphical] WWW browser, like Netscape."
Lynn speaks up, "I am confused aabout the size thing"
Ringer says, "Well you are not using a viewer.. "
Pascal_Calarco says, "Right, we aren't."
Pascal_Calarco says, "I gave people a URL where this document can be viewed as
a WWW page."
Pascal_Calarco says, "If you have a graphical browser, and go to this
you'll see the difference in the size of the headers"
Ninja_Librarian says, "With a text-only browser, the headings will all be the
same size, right?"
Pascal_Calarco says, "Yes, that's right, Ninja_librarian."
Pascal_Calarco says, "Headings really are a graphical addition to HTML"
Pascal_Calarco says, "Other text feature tags, like bold text or italicized
text, while they may be there, also won't show up in a lynx session."
Pascal_Calarco says, "So, in the e-mail handouts, it isn't immediately
apparent that these tags show different font sizes but when we view the document through a
[graphical] browser, they become apparent."
Basic HTML for Librarians
<HEAD> <!-- We declare the Head to start here -->
<BODY> <!-- Now start the content of the page -->
The next line will start directly after!
Pascal_Calarco says, "Headers appear in bold text, to offset them from regular
text found in the body."
Pascal_Calarco says, "Cathy?"
Cathy speaks up, "is this bolding done automatically with the H1 etc
designation...?"
Pascal_Calarco says, "Bolding is part of all headings, yes."
Basic HTML for Librarians
3. Design Considerations
, which produces a solid line across the screen,
to break up sections of text. Where appropriate, you can also use lists to
organize dense and protracted sections of text. "
Pascal_Calarco says, "Airick?"
Airick speaks up, "if netscape sees a tag it doesn't know, will it ignore it
or still try to interpret it?"
Pascal_Calarco says, "Generally, browsers, Netscape included -- will ignore
tags that they don't recognize."
Pascal_Calarco says, "This ensures that unrecognized tags don't wind up
generating errors and crashing the browser."
Pascal_Calarco says, "So the page may look very different than the author
intended it to look if you are using a browser that does not support that
tag."
Cyd raises hand.
Pascal_Calarco says, "Cyd? "
Cyd speaks up, "when we talk of browsers ignoring tags they don't
understand, does that mean you will see the actual tag?"
Pascal_Calarco says, "No. That's an excellent point. Browsers that don't support say, the
Netscape extensions will generally just skip over them rather than try to
interpret them or display the source code it doesn't understand.
Ringer says, "so it recognizes the < as a tag.. and skips it?"
Pascal_Calarco says, "Yes."
Pascal_Calarco says, "You'll see the tag in the source code, but the way the
document looks will be as if the browser skip over it."
Pascal_Calarco says, "That's a good question, and I'm not sure if I can say
definitively what exactly happens technically. For instance, if it sees
the <!--, it knows a
comment is coming, but I'm not quite sure what happens if you try <hey,
try displaying this one!>"
Pascal_Calarco smiles
Pascal_Calarco says, "Something we can play around and experiment with."
Pascal_Calarco says, "Graphic tags are displayed as <IMG
SRC="image.gif"> or <IMG SRC="image.jpg">"
Pascal_Calarco says, ""image" being the filename of the image"
Pascal_Calarco says, "Each represents the two main graphic formats supported
by browsers on the WWW"
Pascal_Calarco says, "LuAnn?"
LuAnn speaks up, "which image format has the higher res?"
Pascal_Calarco says, "A great question."
Pascal_Calarco says, "Generally, the difference is not one so much of
resolution but of the size of the image"
Pascal_Calarco says, "With the second format, "JPG" a compression
algorithm is used to shrink the physical size (in bytes) of the image
down so that it is more quickly transferred."
Pascal_Calarco says, "JPG also has an advantage on the Inetrnet now"
in that Netscape has, with their Navigator 2.0 made the loading of JPGs
more efficient and thus, they transfer even more quickly."
Pascal_Calarco [to Ringer]: Yes.
Pascal_Calarco says, "so people have turned to JPG as the new freely-available
graphic format."
Pascal_Calarco says, "That's a long-winded answer to your question, I'm afraid
Ringer smiles.
Pascal_Calarco says, "If I understand you correctly, the graphic is "Cached.""
Airick nods.
Pascal_Calarco says, "What I mean by that is that browsers such as
Netscape will reserve a
certain amount of disk space and memory in order to speed up the
transfer of heavily visited pages during a particular session."
Pascal_Calarco says, "So, say you start on someone's home page and they have a
picture of themselves. Then you go to a subsequent page. Then you'd
like to go back to that initial page."
Pascal_Calarco says, "Depending on the size of your cache (which is set under
the preferences menu) Netscape will still have that image in memory, so it
won't have to re-transfer it."
Pascal_Calarco says, "Does that make sense?"
Airick speaks up, "that answers my ? thanks"
Pascal_Calarco finally looks up from the steaming keyboard
Ringer says, "John would like to know how to put things in tabular format"
Pascal_Calarco says, "Tables, I'm afraid, I didn't plan to cover
tonight. Its somewhat more involved than I wanted to get."
Ringer says, "i was given a web page that a helped with color and tables "
Pascal_Calarco says, "We could certainly do a session where we could focus on
the newer abilities"
Pascal_Calarco smiles
Jeanne says, "that would be great"
Pascal_Calarco nods
Pascal_Calarco says, "Ah, that's another important one!"
Pascal_Calarco says, "Now, if I take your meaning correctly, you'd like to
embed a hyperlink in an e-mail message, right?"
Pascal_Calarco says, "I *think* this is possible in Netscape 2.0's mailer that
comes with the browser. *But*, in order for this conceivably to work,
the person
receiving it would need to view their mail in Netscape 2.0 as well."
Pascal_Calarco says, "Perhaps some of you have viewed Network Newsgroups
(USENET) using a browser?"
Ringer thinks we need to get back to web pages though.
Pascal_Calarco says, "We're kind of straying from our topic here."
Pascal_Calarco says, "We can discuss this after the session proper."
Basic HTML for Librarians
Inclusion of Graphics, Text, and Footers
<HEAD><TITLE>L.O.S.T. Demonstration Page</TITLE>
</HEAD>
<BODY>
<IMG SRC="library.gif" ALT="A picture of the Library">
<H1>Your Main Branch Library<H1>/
<UL> <!-- Let's start a list for this -->
</UL> <!-- Don't forget to close the unordered list -->
<HR> <!-- A solid line across the page --> <P>
Pascal_Calarco grins.
Pascal_Calarco says, "I know we've gone through quite a bit today, but
this is really just a start for people."
Pascal_Calarco says, "The thing is now to start your explorations and
experimenting with these tags."
Ringer [to Lynn]: that is the mcmuse server that is used, not html per se"
Pascal_Calarco nods.