What happened to the attitude you used to have at school
What happened to the attitude when you broke all the rules
(The Farm, "Groovy Train")
[ 1-10 | 11-20 | 21-30 | 31-40 | 41-50 | 51-60 | 61-70 | 71-80 | 81-90 | 91-.. ]
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 an HTML tutorial. Fully understanding these messages requires some experience from the user.
MAXERR
/MAXMSG
. hsc will abort.
<Hx>
<H3>
element should not
follow an <H1>
element directly. The first heading
showing up in a document should be <H1>
.
HSC.CLICK-HERE
has been found
within the text inside an anchor specification. I.e. you used some term like
``Click here'' inside the text describing a link. This is very clumsy and
should be avoided; see Composing Good
HTML or the W3C
Recommendations for details.
<b><i>bold and italic</b></i>you should write
<b><i>bold and italic</i></b>Note the different location of
</I>
in both cases.
;
'') to end them. For instance, if you try
to use ``ü
'' instead of
``ü
'' (to get an
``ü
'', this message will show up. Simply append the
``;
'' to fix it.
<BLINK>
sucks<BLINK>
. 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.
<$define HUGO:string="hugo"="or sepp?">Remove the part corresponding to ``
="or sepp?"
''.
/CONST
has been specified when defining it earlier.
<$content>
outside any container macro.
HREF
or NAME
.
>
" instead. This can also happen, if you made
an error calling a tag, and hsc's parser couln't recover.
An URI-attribute started with a slash (``/
'') (like for example
``/image/next.png
''), 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.
Normally, hsc 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.
If you because of some obscure reasons (or simply stupidity) insist on using URIs of such kind, you can set the CLI option ServerDir to specifiy the root directory for server relative URIs.
<LISTING>
).
<$message>
.
GetEnv()
could not access the environment variable specified an returned an
empty value.
WIDTH
and/or HEIGHT
by
hand. It denotes that the values you have used differ from those hsc has
evaluated from the image data.
<* comment *>
tag instead.
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.
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.<$else|$elseif>
<$else>
tag has been at an unexpected position. Usually a
single preceding <$if>
has two or more corresponding
<$else>
tags assigned.
<$exec>
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.
-
'') as delimters inside your source. For example,
<!-------->(8 hyphens) works fine, whereas
<!--------->(9 hyphens) will cause problems.
<INPUT>
may only occur
inside <FORM>
.
<A>
inside <A>
.
_
''), period (``.
'') and hyphen (``-
'').
</IMG>
<$defent>
or <$deficon>
call.
.
'') must not be used.
#rrggbb
''
or be one of the values declared in the special attribute
HSC.COLOR-NAMES
defined in hsc.prefs
<A NAME=..>
,
or just made a typo.
<IMG>
.
This message will only show up if you have passed the CLI option
IconBase.
_
''))
as a blank)
you better should use<STRONG>
__important__</STRONG>
<STRONG>
important</STRONG>
It only affects tags like <A>
, <TITLE>
, headings and
physical/locigal styles.
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.
.
'') or hyphen (``-
''), it needs to be quoted.
<$deftag>
. 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.
<$macro>
. 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.
<$exec>
with REMOVE
enabled, the file
could not be deleted. This can happen if you for example declared macros
or opened container tags without closing them in the file created by
an external command and included it afterwards; hsc keeps a
lock on files that might need to be referred to later in messages.
<TAG />
in XHTML. Actually,
<TAG>
</TAG>
would be legal, too, but hsc doesn't support this,
both for technical reasons and because the first form is both equivalent and
shorter. The reason for not allowing the form <TAG/>
(note the missing
blank!) is mainly a technical one, apart from the fact that it should be avoided
so older browsers can deal with it. If you forget the closing slash in a tag
such as <br />
, hsc will complain about it with this message.
<img src="foo.gif" / alt="bar">
.
STYLE
attribute contained CSS specifications hsc could not
understand. There will usually be a message hinting at the reason (such as
``missing value'') displayed with this message.
STYLE
attributes into one, or if you specify
a width
or height
property while running hsc with
the GETSIZE
commandline option.
<$defent>
call was found that might not do what you wanted. Either you
specified a RPLC code for an entity with a numeric code >255, or you tried to
redefine an entity. Both may indeed be intended, in which case you should tell
hsc to ignore this warning.