File: messages.html

package info (click to toggle)
hsc 0.916-2
links: PTS
area: main
in suites: hamm, slink
size: 2,584 kB
ctags: 2,277
sloc: ansic: 17,375; makefile: 396
file content (501 lines) | stat: -rw-r--r-- 27,624 bytes
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE>hsc - Messages</TITLE>
<LINK REV="owns" TITLE="Thomas Aglassinger" HREF="mailto:agi@giga.or.at">
<LINK REL="Next" HREF="envvar.html">
<LINK REL="Copyright" HREF="copy.html">
<LINK REL="Previous" HREF="fileargs.html">
<META name="ROBOTS" content="NOINDEX, NOFOLLOW">
</HEAD>
<BODY>
<A HREF="index.html"><IMG SRC="image/main.gif" ALT="Contents" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<IMG SRC="image/noindex.gif" ALT="-----" ALIGN="middle" WIDTH="70" HEIGHT="16">
<A HREF="copy.html"><IMG SRC="image/copy.gif" ALT="Copyright" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="index.html"><IMG SRC="image/back.gif" ALT="Up" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="fileargs.html"><IMG SRC="image/prev.gif" ALT="Previous" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<A HREF="envvar.html"><IMG SRC="image/next.gif" ALT="Next" ALIGN="middle" WIDTH="70" HEIGHT="16"></A>
<HR>
<P ALIGN="right"><I>What happened to the attitude you used to have at school<BR>What happened to the attitude when you broke all the rules</I><BR>
(The Farm, "Groovy Train")
</P>
<H1>Messages</H1>
<P><KBD>Hsc</KBD> is able to produce lots of different warnings and errors
when parsing hsc-sources. The are divided into several classes, and
there is a possibility to filter out specific messages or whole
message classes. There are also possibilities to change the appearance
of messages and redirect them to a file, making it easy to integrate
<KBD>hsc</KBD> into existing developer environments.</P>
<P>[ <A HREF="#message.1">1-10</A>
| <A HREF="#message.11">11-20</A>
| <A HREF="#message.21">21-30</A>
| <A HREF="#message.31">31-40</A>
| <A HREF="#message.41">41-50</A>
| <A HREF="#message.51">51-60</A>
| <A HREF="#message.61">61-70</A>
| <A HREF="#message.71">71-80</A>
| <A HREF="#message.71">81-..</A>
]
</P>
<H2><A NAME="elements">Message Elements</A></H2>
For example, a typical message could be:

<PRE>hugo.hsc (17,23): Warning 11: unknown tag &lt;SEPP&gt;</PRE>
with being..<UL>
<LI>..<CODE>hugo.hsc</CODE> the name of the input file that caused the message.
<LI>..<CODE>17</CODE> and <CODE>23</CODE> the position
in input file. 17 denotes the line, and 23 the column of the
item that caused the message
<LI>..<CODE>Warning</CODE> the message class. There are several other
messages classes: <A HREF="messages.html#msg_note">Note</A>, <A HREF="messages.html#msg_style">Bad-style</A>, <A HREF="messages.html#msg_port">Portability-problem</A>, <A HREF="messages.html#msg_err">Error</A> or <A HREF="messages.html#msg_ferr">Fatal error</A>.
See below for details about those message classes.
<LI>..<CODE>11</CODE> the number of the message. You can use this to
quickly find the description of the message (see below) or to
suppress it in further runs using <A HREF="options.html#ignore"><KBD>IGNORE</KBD></A>.
<LI>..<CODE>unknown tag &lt;SEPP&gt;</CODE> the message text, which describes what
went wrong.
</UL>
<H2><A NAME="classes">Message Classes</A></H2>
<P><STRONG><A NAME="msg_note">Note</A></STRONG> is a message only for the
user's information. It can be suppressed using <CODE><A HREF="options.html#ignore">IGNORE</A></CODE>.</P>
<P><STRONG><A NAME="msg_style">Bad-style</A></STRONG> informs the user
that his although legal html-code includes constructs that indicate a
bad style. It can be suppressed using <CODE><A HREF="options.html#ignore">IGNORE</A></CODE>.</P>
<P><STRONG><A NAME="msg_port">Portability-problem</A></STRONG> informs
the user that his although legal html-code includes constructs can
lead to problems on old or buggy browsers. It can be suppressed using
<CODE><A HREF="options.html#ignore">IGNORE</A></CODE>.</P>
<P><STRONG><A NAME="msg_warn">Warning</A></STRONG> tells you that your
source includes some problematic parts, that can lead to problems with
several browsers. It can be suppressed using <CODE><A HREF="options.html#ignore">IGNORE</A></CODE>.</P>
<P><STRONG><A NAME="msg_err">Error</A></STRONG> indicates that there
is something wrong with your html-source. Conversion will continue,
but no output will written be written after finishing it.</P>
<P><STRONG><A NAME="msg_ferr">Fatal error</A></STRONG> tells you that something
terrible has happened and there is no way to continue the conversion.
No output will be written.</P>
<P>There is also another class called <STRONG>internal error
messages</STRONG>, which are used by <KBD>hsc</KBD> to report that something
unexpected happened. To find out more about this, look at the chapter
about ``<A HREF="bugs.html">Known Bugs, Problems And Limitations</A>''.</P>
<H2><A NAME="options">Message Options</A></H2>
There are several CLI options to modify the behavior of <KBD>hsc</KBD>'s
messages:
<UL>
<LI><A HREF="options.html#ignore"><KBD>IGNORE</KBD></A> can be used to suppress single messages or whole
message classes, if you are not interested in them
<LI><KBD><A HREF="options.html#msgformat">MSGFORMAT</A></KBD>
specifies the appearance of messages, for example concerning the
sequence of the elements described before.
<LI><KBD><A HREF="options.html#msgformat">MSGFILE</A></KBD> can be used to
redirect messages into a file, from where they can be processed
for example by some message parser that controls your editor
<LI><KBD><A HREF="options.html#msgformat">MSGANSI</A></KBD> tells
<KBD>hsc</KBD> to insert a few ANSI escape sequences to make messages easier to
read. This only makes sense if you refuse use a message browser as
suggested above, and only let them show up on the screen.
</UL>
<HR>
<H2><A NAME="list">List Of Messages</A></H2>
Below you can find a list of messages that can show up when processing
hsc sources. Most of them also include a short explanation what could
have caused the problem and how to fix it.
However, this is not a html-tutorial. Fully
understanding these messages requires some experience from the user.
<DL>
<DT><A NAME="message.1"><STRONG>warning
1: unable to open project-file</STRONG></A><DD>
The project-file specified could not been open. This indicates
no problem, if you specified a project-file using <A HREF="options.html#prjfile"><KBD>PRJFILE</KBD></A>
the first time; it will be created automatically after the
html-object has successfully been processed.
<DT><A NAME="message.2"><STRONG>fatal error
2: project-file corrupt</STRONG></A><DD>
The data found in the project file are not of the required
form. Most likely, the file-format-version is outdated.
Remove the old file, <KBD>hsc</KBD> will create a new one next time it
is invoked.
<DT><A NAME="message.3"><STRONG>fatal error
3: unexpected end of file</STRONG></A><DD>
There are still characters to be read from input, but the file
already ends; <KBD>hsc</KBD> tells you what it still expects to come.
<DT><A NAME="message.4"><STRONG>fatal error
4: error reading <I>file</I></STRONG></A><DD>
On attempting to read from an input file, an error has occured. This
usually is on a hardware level, and can only be fix by one of those
tools to validate and repair a disk structure common on every
platform.
<DT><STRONG>message 5:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.6"><STRONG>fatal error
6: can not open <I>file</I> for input</STRONG></A><DD>
An input file could not be opened. A more detailed description that
tells you why is displayed, too.
<DT><A NAME="message.7"><STRONG>note
7: stripped tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
Notifies user that a tag has been removed. This usually happens
because the user requested this with one of the CLI-options.
<DT><STRONG>message 8:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.9"><STRONG>bad style
9: expected heading <CODE>&lt;Hx&gt;</CODE></STRONG></A><DD>
A heading should not be more than one level below the heading
which preceded it. That is, an <CODE>&lt;H3&gt;</CODE> element should not
follow an <CODE>&lt;H1&gt;</CODE> element directly. The first heading
showing up in a document should be <CODE>&lt;H1&gt;</CODE>.
<DT><A NAME="message.10"><STRONG>bad style
10: "click here" syndrome detected</STRONG></A><DD>
A keyword defined with the special attribute <CODE>HSC.CLICK-HERE</CODE>
has been found within the text inside an anchor specification.<P>
Ok, now again in English: you used some term like "Click here" inside
the text describing a link. This is very clumsy and should be avoided;
see <A HREF="http://www.cs.cmu.edu/~tilt/cgh/index.html#linktext">Composing
Good HTML</A> for details.
<DT><A NAME="message.11"><STRONG>error
11: unknown tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
You refered to an unknown tag or macro.
<DT><A NAME="message.12"><STRONG>error
12: tag &lt;<I>tag</I>&gt; occured too often</STRONG></A><DD>
A tag that is expected to occure only once appeared at least twice.
Remove all unneccessary occurences of the tag.
<DT><A NAME="message.13"><STRONG>error
13: unmatched end-tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
You called a end-tag without using the corresponding start-tag
before.
<DT><A NAME="message.14"><STRONG>warning
14: illegal end-tag nesting</STRONG></A><DD>
A end-tag appeared where a different end-tag was expected to
appear before. Example: instead of
<PRE>
&lt;B&gt;&lt;I&gt;bold and italic&lt;/B&gt;&lt;/I&gt;
</PRE>
you should write
<PRE>
&lt;B&gt;&lt;I&gt;bold and italic&lt;/I&gt;&lt;/B&gt;
</PRE>
Note the different location of <CODE>&lt;/I&gt;</CODE> in both cases.
<DT><A NAME="message.15"><STRONG>warning
15: required tag &lt;<I>tag</I>&gt; missing</STRONG></A><DD>
A tag that is required for every document is missing.
<DT><A NAME="message.16"><STRONG>warning
16: end-tag &lt;<I>tag</I>&gt; missing</STRONG></A><DD>
You called an start-tag, but didn't end it. Insert the required
end-tag.
<DT><A NAME="message.17"><STRONG>error
17: unknown tag modifier <I>/modifier</I></STRONG></A><DD>
You have used an unknown <A HREF="macro/flag.html">modifier</A>
to define the characteristics of an tag or macro.
<DT><A NAME="message.18"><STRONG>warning
18: unknown entity</STRONG></A><DD>
You used an entity, that <KBD>hsc</KBD> doesn't know. This can happen if you
made a typo, or the entity has not been defined within
<I>hsc.prefs</I>.
<DT><A NAME="message.19"><STRONG>warning
19: ";" expected after entity</STRONG></A><DD>
Entities require a semicolon (``<CODE>;</CODE>'') to end them. For instance, if you try
to use ``<CODE>&amp;uuml</CODE>'' instead of
``<CODE>&amp;uuml<STRONG>;</STRONG></CODE>'' (to get an
``<CODE>&uuml;</CODE>'', this message will show up. Simply append the
``<CODE>;</CODE>'' to fix it.
<DT><A NAME="message.20"><STRONG>error
20: unknown attribute <I>attrib</I></STRONG></A><DD>
You tried to access an attribute which has not been defined before.
<DT><A NAME="message.21"><STRONG>warning
21: path to URI not found: <I>file</I></STRONG></A><DD>
An attribute refers to a local resource (like another document or
image) that doesn't exist. Common reasons for that are typos, a
case-sensitive file system or indeed a missing file.
<DT><A NAME="message.22"><STRONG>warning
22: argument without quote</STRONG></A><DD>
You passed a value to an attribute, but did not embed it into single
or double quotes. This can lead to problems with older browsers.
<DT><A NAME="message.23"><STRONG>error
23: empty reference to attribute <I>attrib</I></STRONG></A><DD>
An attribute refers to an attribute that has been defined, but no
value has been set for. Usually, you try to refer to an attribute
inside a macro, that no value has been passed to within the call
of the macro.
<DT><A NAME="message.24"><STRONG>warning
24: attribute option ``<I>option</I>'' not allowed in this context</STRONG></A><DD>
You have used an <A HREF="macro/attrib.html#modifier">option</A>
to define the characteristics of an attribute, which is not allowed to
appear at this location.
<DT><A NAME="message.25"><STRONG>bad style
25: <CODE>&lt;BLINK&gt;</CODE> sucks</STRONG></A><DD>
Some browser support the non-html-tag <CODE>&lt;BLINK&gt;</CODE>. It is used
to make text blinking, which annoys many users. Additionally, most
of them don't know how to configure their browser that it doesn't
blink, so you really should avoid it.
<DT><A NAME="message.26"><STRONG>error
26: default value for attribute <I>attrib</I> already set</STRONG></A><DD>
You tried to assign more than one default value within an attribute declaration.
For instance, like in
<PRE>
    &lt;$define HUGO:string="hugo"="or sepp?"&gt;
</PRE>
Remove the part corresponding to ``<CODE>="or sepp?"</CODE>''.
<DT><A NAME="message.27"><STRONG>error
27: attempt to modify constant attribute <I>attrib</I></STRONG></A><DD>
You tried to assign a new value to an attribute declared as constant.
That is, the <A HREF="macro/attrib.html#modifier">attribute option</A>
<CODE>/CONST</CODE> has been specified when defining it earlier.
<DT><A NAME="message.28"><STRONG>fatal error
28: no content within current context</STRONG></A><DD>
You tried to call <A HREF="features/spctags.html#content"><CODE>&lt;$content&gt;</CODE></A> outside any container macro.
<DT><A NAME="message.29"><STRONG>error
29: tag &lt;A&gt; without HREF or NAME</STRONG></A><DD>
An anchor tag has been specified without one of the required attributes
<CODE>HREF</CODE> or <CODE>NAME</CODE>.
<DT><A NAME="message.30"><STRONG>error
30: unmatched "&gt;"</STRONG></A><DD>
A "greater than" sign appeared inside the text. You should write
"<CODE>&amp;gt;</CODE>" instead. This can also happen, if you made
an error calling a tag, and <KBD>hsc</KBD>'s parser couln't recover.
<DT><A NAME="message.31"><STRONG>error
31: expected "<I>element_expected</I>", found "<I>element_found</I>"</STRONG></A><DD>
A syntax element did not occur where it has been expected.
<DT><STRONG>message 32:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.33"><STRONG>warning
33: linefeed found inside string</STRONG></A><DD>
<DT><STRONG>message 34:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.35"><STRONG>error
35: unknown value <I>value</I> for enumerator attribute <I>attrib</I></STRONG></A><DD>
You tried to set an enumerator to a value it doesn't support.
<DT><A NAME="message.36"><STRONG>warning
36: server relative URI to <I>uri</I></STRONG></A><DD>
<P>An URI-attribute started with a slash (``<CODE>/</CODE>'') (like for example
``<CODE>/image/next.png</CODE>''), denoting a so called server relative URI.
This is a really braindead concept, which might help to save a few
bytes in your html-object, but will make your documents unreadable
if stored on your local disk, as they depend on a specific server
structure.</P>
<P>Normally, <KBD>hsc</KBD> is unable to validate links or obtain image sizes
of data referenced using server relative URIs because of reasons that
should be obvious to everyone.</P>
<P>If you because of some obscure reasons (or simply stupidity) insist
on using URIs of such kind, you can set the CLI option <A HREF="options.html#serverdir"><KBD>SERVERDIR</KBD></A>
to specifiy the root directory for server relative URIs.</P>
<DT><A NAME="message.37"><STRONG>warning
37: tag &lt;<I>tag</I>&gt; is obsolete</STRONG></A><DD>
The tag was defined within some old html-version, but should
not be used any more (eg. <CODE>&lt;LISTING&gt;</CODE>).
<DT><A NAME="message.38"><STRONG>warning
38: tag &lt;<I>tag</I>&gt; is only used by jerks</STRONG></A><DD>
This tag is no legal html-tag and is only supported by special
browsers.
<DT><A NAME="message.39"><STRONG>error
39: <I>custom user message</I></STRONG></A><DD>
This text and class of this message can be controlled by the
user using <A HREF="features/spctags.html#message"><CODE>&lt;$message&gt;</CODE></A>.
<DT><A NAME="message.40"><STRONG>fatal error
40: can not open preferences file</STRONG></A><DD>
The file <I>hsc.prefs</I> could not be found at any of the
<A HREF="features/prefs.html#search">expected locations</A>.
<DT><A NAME="message.41"><STRONG>warning
41: unknown environment variable ``<I>envvar</I>''</STRONG></A><DD>
The function <A HREF="features/expressions.html#getenv"><CODE>GetEnv()</CODE></A>
could not access the environment variable specified an returned an
empty value.
<DT><A NAME="message.42"><STRONG>error
42: missing value for attribute <I>attrib</I></STRONG></A><DD>
Non-boolean attributes require an value set.
<DT><A NAME="message.43"><STRONG>error
43: unknown attribute option <I>option</I></STRONG></A><DD>
You defined a new attribute, but used an
<A HREF="macro/attrib.html#modifier">option</A> that is unknown.
<DT><A NAME="message.44"><STRONG>error
44: required attribute <I>attrib</I> missing</STRONG></A><DD>
An attribute that is required has not been set within the call
of a tag or macro.
<DT><A NAME="message.45"><STRONG>warning
45: unexpected value for attribute <I>attrib</I>: expected ``<I>value</I>'', found ``<I>value</I>''</STRONG></A><DD>
This message can show up if you have specified <A HREF="options.html#getsize"><KBD>GETSIZE</KBD></A> when invoking <KBD>hsc</KBD>,
and have set the attribute <CODE>WIDTH</CODE> and/or <CODE>HEIGHT</CODE> by
hand. It denotes that the values you have used differ from those <KBD>hsc</KBD> has
evaluated from the image data.
<DT><A NAME="message.46"><STRONG>note
46: replaced <I>char</I> by <I>entity</I></STRONG></A><DD>
Informs you that a special character (non-7-bit-ASCII) has been replaced
by it's corresponding entity.
<DT><A NAME="message.47"><STRONG>error
47: illegal white space</STRONG></A><DD>
A white space occurred at a place where it was not supposed to.
<DT><A NAME="message.48"><STRONG>portability problem
48: line feed inside sgml-comment</STRONG></A><DD>
<DT><A NAME="message.49"><STRONG>portability problem
49: "&gt;" inside sgml-comment</STRONG></A><DD>
<DT><A NAME="message.50"><STRONG>portability problem
50: sgml-comment ends inside quotes</STRONG></A><DD>
The messages#48 to #50 point out problems that are known bugs of
several browsers. A general comment on sgml-comments: Try to avoid
them, use the <A HREF="features/spctags.html#comments"><CODE>&lt;* <I>comment</I> *&gt;</CODE></A>
tag instead.
<DT><A NAME="message.51"><STRONG>warning
51: no entry for document "<I>document</I>" in project data to check id <I>id</I></STRONG></A><DD>
This message is active only if you specified a project file when
invoking <KBD>hsc</KBD> using the option <A HREF="options.html#prjfile"><KBD>PRJFILE</KBD></A>. It tells you that a
reference to an ID inside another document could not be checked
because the document linked to is not mentioned in the project file.
<P>Usually, this happens when you did not process the above mentioned
document with a project file specified before. Do not worry about that
too much, after processing all documents of your project at least
once, this message usually does not show up any more.</P>
If it still is there, then you are refering to documents that are part
of none or another project using another project-file; if so, there is
no work-around for this case.
<DT><STRONG>message 52:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.53"><STRONG>error
53: unmatched conditional <CODE>&lt;$else|$elseif&gt;</CODE></STRONG></A><DD>
An <CODE>&lt;$else&gt;</CODE> tag has been at an unexptected position. Usually,
a single preceding <CODE>&lt;$if&gt;</CODE> has two or more corresponding <CODE>&lt;$else&gt;</CODE>
tags assigned.
<DT><A NAME="message.54"><STRONG>warning
54: calling external command returned <I>value</I></STRONG></A><DD>
You have invoked a shell-command using <A HREF="features/exec.html"><CODE>&lt;$exec&gt;</CODE></A> and it returned a
value unequal to zero, which usually denotes an error while processing
the command. For error analysis, look at the output that the command
(hopefully) has made.
<DT><A NAME="message.55"><STRONG>warning
55: text outside sgml-comment context</STRONG></A><DD>
This message often shows up, if you are not using an even number of
hypens (``<CODE>-</CODE>'') as delimters inside your source. For example,
<PRE>&lt;!--------&gt;</PRE>
(8 hyphens) works fine, whereas
<PRE>&lt;!---------&gt;</PRE>
(9 hyphens) will cause problems.
<DT><STRONG>message 56:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.57"><STRONG>error
57: no start tag for end tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
An end tag has been detected without it's corresponding start tag
occuring before.
<DT><A NAME="message.58"><STRONG>portability problem
58: icon-entity <I>entity</I> found</STRONG></A><DD>
Icon-entities are not (yet) widely supported.
<DT><A NAME="message.59"><STRONG>warning
59: redefined tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
You have just redefined a tag or macro that has already been
declared before. The previous declaration will be thrown away.
<DT><A NAME="message.60"><STRONG>error
60: tag &lt;<I>tag</I>&gt; must be inside tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
Before you are allowed to use the first tag, the second tag has to
occure before. Example: <CODE>&lt;INPUT&gt;</CODE> may only occure
inside <CODE>&lt;FORM&gt;</CODE>.
<DT><A NAME="message.61"><STRONG>error
61: tag &lt;<I>tag</I>&gt; not allowed within tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
A tag occurs inside another tag that does not allow this. For example,
you can't recursively use <CODE>&lt;A&gt;</CODE> inside <CODE>&lt;A&gt;</CODE>.
<DT><A NAME="message.62"><STRONG>error
62: no attributes allowed for end-tags</STRONG></A><DD>
You tried to pass values to a end-tag or macro. If you need an attribute
for a end-macro only, you still have to define and pass it within the
start-macro; the end-macro will have access to all these attributes
and its values.
<DT><A NAME="message.63"><STRONG>warning
63: redefinition of attribute <I>attrib</I></STRONG></A><DD>
You redefined an alredy existing attribute. If this occures during
the definition of a new macro, you just tried to give two arguments the
same name.
<DT><A NAME="message.64"><STRONG>error
64: illegal attribute identifier "<I>attribute_name</I>"</STRONG></A><DD>
You have tried to use an attribute name which contains characters not
allowed for that. Legal characters for attribute names are letters, digits,
underscore (``<CODE>_</CODE>''), period (``<CODE>.</CODE>'') and hyphen (``<CODE>-</CODE>'').
<DT><A NAME="message.65"><STRONG>error
65: unknown binary operator "<I>operator</I>"</STRONG></A><DD>
Within an <A HREF="features/expressions.html">expression</A>,
you have used an binary operator that is not
one of those mentioned in the
<A HREF="features/expressions.html#operators">list of operators</A>.
<DT><A NAME="message.66"><STRONG>error
66: illegal end-tag</STRONG></A><DD>
You tried to use a simple tag as a container, for example <CODE>&lt;/IMG&gt;</CODE>
<DT><A NAME="message.67"><STRONG>bad style
67: recommended tag &lt;<I>tag</I>&gt; missing</STRONG></A><DD>
A tag that ought to appear is missing.
<DT><A NAME="message.68"><STRONG>note
68: unknown filetype</STRONG></A><DD>
<KBD>hsc</KBD> could not <A HREF="features/getsize.html">determine the size</A>
of a link destination.
<DT><A NAME="message.69"><STRONG>error
69: illegal entity definition</STRONG></A><DD>
Somethings wrong with a <A HREF="features/prefs.html#defent"><CODE>&lt;$defent&gt;</CODE></A> or <A HREF="features/prefs.html#deficon"><CODE>&lt;$deficon&gt;</CODE></A> call.
<DT><A NAME="message.70"><STRONG>warning
70: can not strip special tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
You have tried to strip one of <KBD>hsc</KBD>'s
<A HREF="features/spctags.html">special tags</A> using the CLI-option
<A HREF="options.html#striptags"><KBD>STRIPTAGS</KBD></A>. This does not make much sense, because all these tags
will not show up in the output anyway.
<DT><A NAME="message.71"><STRONG>error
71: illegal numeric value <I>value</I> for attribute <I>attrib</I>/entity</STRONG></A><DD>
A numeric value must only consist of digits. Only integer values are
allowed, therefor even a period (``<CODE>.</CODE>'') must not be used.
<DT><A NAME="message.72"><STRONG>warning
72: illegal color value</STRONG></A><DD>
A color value must fit the template ``<CODE>#rrggbb</CODE>''
or be one of the values declared in the special attribute
<A HREF="features/spcattr.html#colornames"><CODE>HSC.COLOR-NAMES</CODE></A>
defined in <I>hsc.prefs</I>
<DT><STRONG>message 73:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.74"><STRONG>warning
74: unknown id <I>id</I></STRONG></A><DD>
You forgot to specify the ID mentioned using <CODE>&lt;A NAME=..&gt;</CODE>,
or just made a typo.
<DT><A NAME="message.75"><STRONG>warning
75: local id <I>id</I> already declared</STRONG></A><DD>
You tried to redefine an ID that has already been declared before within
the current document.
<DT><A NAME="message.76"><STRONG>bad style
76: frames are disgusting</STRONG></A><DD>
This message should need no comment; anyway, read
<A HREF="http://www.useit.com/alertbox/9612.html">Why Frames Suck (Most of the Time)</A>
or
<A HREF="http://www.ummed.edu/pub/i/ijosh/frames/">Why Frames Suck</A>
for more details.
<DT><A NAME="message.77"><STRONG>note
77: replacing icon-entity</STRONG></A><DD>
A icon-entity has been found is was replaced by an <CODE>&lt;IMG&gt;</CODE>.
This message will only show up if you have passed the CLI option
<A HREF="options.html#iconbase"><KBD>ICONBASE</KBD></A>.
<DT><A NAME="message.78"><STRONG>bad style
78: succeeding white space for tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
See below.
<DT><A NAME="message.79"><STRONG>portability problem
79: preceding white space for end tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
These two messages point out that instead of (read the underscore (``<CODE>_</CODE>''))
as a blank)
<BLOCKQUOTE>
<CODE>&lt;STRONG&gt;</CODE>__important__<CODE>&lt;/STRONG&gt;</CODE>
</BLOCKQUOTE>
you better should use
<BLOCKQUOTE>
<CODE>&lt;STRONG&gt;</CODE>important<CODE>&lt;/STRONG&gt;</CODE>
</BLOCKQUOTE>
<P>It only affects tags like <CODE>&lt;A&gt;</CODE>, <CODE>&lt;TITLE&gt;</CODE>, headings and
physical/locigal styles.</P>
<P>This message might seem unreasonable, as according to the
specifications for html-readers such white spaces should be skipped.
However, some browsers fail to do so.
<DT><STRONG>message 80:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.81"><STRONG>warning
81: value for attribute <I>attrib</I> requires quotes</STRONG></A><DD>
If a attribute value contains any characters other then letters,
digits, period (``<CODE>.</CODE>'') or hyphen (``<CODE>-</CODE>''), it needs to be quoted.
<DT><A NAME="message.82"><STRONG>note
82: changed quotes for attribute <I>attrib</I> from [<I>style</I>] to [<I>style</I>]</STRONG></A><DD>
The quote style has been changed for a specific attribute.
This message will only show up if you have passed the CLI option
<A HREF="options.html#quotestyle"><KBD>QUOTESTYLE</KBD></A>.
<DT><STRONG>message 83:</STRONG><DD>Unused or undocumented.
<DT><A NAME="message.84"><STRONG>warning
84: unknown attribute <I>attrib</I> for tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
A tag call contains an unknown attribute, which was not defined with
the corresponding <A HREF="features/prefs.html#deftag"><CODE>&lt;$deftag&gt;</CODE></A>. This does not denote a serious problem,
as html provides a vast selection of esoteric attributes and browsers
usually ignore unknown attributes, but you should confirm you did not
make a typo.
<DT><A NAME="message.85"><STRONG>error
85: unknown attribute <I>attrib</I> for tag &lt;<I>tag</I>&gt;</STRONG></A><DD>
A macro call contains an unknown attribute, which was not defined
with the corresponding <A HREF="macro/macros.html"><CODE>&lt;$macro&gt;</CODE></A>. As it would not make sense to
pass unknown attributes to macros, this is considered an error.
Look at the macro declaration which attribute you meant.
</DL>
</BODY></HTML>