Why would anyone want to know? Well, to help stop them repeating them on
their sites.
Cross-Platform filename usage, the lowest common denominator
should be adopted: Name in lowercase, no name longer than 8 characters,
and refer to in lowercase. Also necessary to use filename
extensions, even if your native system doesn't need them,
3 characters long, except the homepage, which should always be called
index.html .
Don't trust applications that offer to write or amend your
pages for you: Ms FrontPage messed up the style of a test
page I asked it to alter a minor detail on, and added comments
to the effect of "Produced entirely by Microsoft FrontPage,
with no human intervention whatsoever. This page is the
exclusive property of the Microsoft Corp. Inc. Any infringer
of this property will be prosecuted to the full extent of
the law and then shot." So. Only give them copies.
<SUB> and <SUPER> Use the current <FONT>
size to work out their positioning: So different ways of nesting
<SUB> or <SUPER> with <FONT> produce different results.
This is important for Trademark symbols, the "AD" mark denoting the
Occidental calendar, chemical formula, &c.
Some time ago, my [home] Monitor blew up. These caused the following
problems:
I couldn't see what I was doing, or almost, I was operating a
mid-range, all-singing, all-dancing, highly graphical system, down a serial
link through a small LCD screen. (!)
I couldn't update these pages properly for that time being.
I was, tooling up for a job in the Computer Graphics Industry, but, while
I then had plenty of render time, I couldn't look at the results without a
journey to the nearest quiet internet café.
I appealed for a cheap working secondhand SVGA 11"-14" monitor,
preferably in the Swindon area. (My appeal was answered, though not through
the original medium.)
When learning CSS, I noticed comparisions with C, POV, and similar,
where the convention is to enclosed comments between /*.... */,
and one-line comments after //.... .
However, CSS only recongised /*.... */, and attempts to parse the
other. This isn't mentioned in the documentation, and caused
peculiar intermittant errors until I tracked it down.
