I frequently put things like "this is <B>very<B> important" and then wonder why all the rest of the page is in bold! (The second <B> should have been </B> with a "/").
In the following contrived sequence
"Remember, <TT> this is <B>very</TT> important</B>",
the two "end tags" have been transposed. Whatever form of logic a browser attempts to apply, it won't ever display as intended!
Although the RiscOS filing system is not sensitive to the case (upper/lower) of the letters in filenames, the Unix filing system (or Unix look-alike) used by the web-server most definitely IS.For simplicity, I prefer to use lower-case throughout; this saves me having to remember which letters if any are in upper case!
Although the RiscOS filing system encodes the file-type separately from the filename, Unix-style filing systems expect an extension. WebPack - and TIMM at the other end - do a pretty intelligent job of associating the right extension with the right filetype, and even coping with truncated filenames-plus-extension; but they aren't 100% idiot-proof, and can still sometimes get fooled.To be fool-proof, I tend to restrict the leafname (excluding extension) to five characters maximum (possibly six for /gif or /zip extensions).
WebPack will only pack files within your "site" directory; it will NOT include any sub-directories. If your archiver (eg SparkFS or the read/write version of ArcFS) is still active (ImageFS operational), the archive will appear to be a directory.Before using WebPack, click menu over an archive icon. If the second item in the menu says
I'm never quite sure, but I suspect that WebPack may contain an internal list of filetypes and extensions that it is prepared to recognise: if this is true, and if you've got a fancy file which is not on the list, then either it might not get uploaded, or else it might be put on the site but with the "wrong" extension.
Disclaimer: I may be totally wrong on this!!
If you have <A HREF="page2.html"> (or <A HREF="./page2.html"> ),
they are relative URLs, and the page requested will be looked for in the "current directory"; this will normally be the directory that holds the page currently being displayed,
UNLESS your HTML-code includes an element of the form
<BASE HREF="http://www.domain/diry"> in which case it will use THAT to look for "page2.html" in!
If you have <A HREF="http://www.domain/diry/page2.html">,
then that is an absolute URL, and hard cheese if it isn't exactly correct!
Check (4) above: ensure all extensions are correct.
DOS systems have an additional potential problem arising from their limitation of three-character extensions (eg "htm" and "jpg").
Providing your extensions are "correct" (in the Unix sense), all other browsers are supposed to implement that regardless of any of their platform's operating-system's limitations.
If images are their problem:
Voyager/WebVoyage/ArcWeb can quite happily render SpriteFiles (indeed, it's less work for it, as no conversion is necessary and RiscOS will do the plotting); but if you've accidentally uploaded an unconverted SpriteFile to your web-site, it will be completely meaningless to any non-Acorn platform.If other Argonauts can't access it:
It may be connected with a small change you've made recently (possibly to a filename): I'm hypothesising a situation where one of you is accessing the actual file, and the other's browser is accessing a cached version of a file from a previous occasion. Disclaimer: the above is really clutching at straws!
WebGif2 (and spr2gif too for that matter) will only generate a transparent GIF if you specifically ask for it.
Menu on icon-bar telephone icon: Preferences => Web browser... and see what it says. ChangeFSI doesn't render transparent GIFs; so if this option is ON, un-tick it (and [Save]!)
Voyager/WebVoyage/ArcWeb does not render GIFs "on the fly" as they are being (down)loaded, but converts them (using gif2spr) into ordinary native SpriteFiles (regardless of whether they are interlaced or not), and then uses the system sprite-plotting routines to display them all in one hit.Try viewing your site with another browser: I think Fresco will render interlaced GIFs; otherwise pull the curtains and lock the door (so nobody can see you) and try Netscape.
John Alldred <firstname.lastname@example.org> 29/8/96