verticalScrollOnRight user settable.
/tmp/xmosaic.pid to
/tmp/Mosaic.pid. This is the final such change,
forever.
mailCommand resource is now totally obsolete.
sendmailCommand resource is now expected to point to
your system's sendmail binary; default is
/usr/lib/sendmail. Assumption is made that this
program accepts command-line arguments specifying addresses to
which message should be mailed, and accepts other headers and
message text from stdin.
X-URL is used to indicate the URL
of a mailed document to the recipient.
BASE directive is added to mailed HTML documents
to allow inlined images and relative hyperlinks to work on the
other end.
ISINDEX forms and text entry areas.
SELECT/OPTION handling.
>48 character) realm names.
ADDRESS tag in news articles.
ftp://username:password@host/ URLs (thanks to Larry
Masinter).
trackFullURLs set to
false (that option still doesn't work in all cases,
but at least it does something reasonable now).
FORM METHOD="POST" with optional
ENCTYPE="application/x-www-form-urlencoded".
TEXTAREA as described in the current
(11/2) HTML+ spec.
OPTIONs now work.
TMPDIR) is unusable.
MAXLENGTH attribute.
imageCacheSize can be set to the maximum image cache
size of your choice (in kbytes; default 2048) -- command line option
-ics also does this.
imageCacheSize. (This is a feature :-).
uncompressCommand and
gunzipCommand still control uncompression commands.
gunzipCommand is "gunzip -n -f", which requires a
recent version of gzip.
application/octet-stream, and any MIME type mapped
to magic viewer "mosaic-internal-dump").
TMPDIR -- fixed.
HREF instead of
SRC with IMG.
newwin directive.
INPUT elements of type RADIO
for fill-out forms as per HTML+ spec.
INPUT elements of type PASSWORD
for fill-out forms as per HTML+ spec.
INPUT elements of type OPTION
for option menus in fill-out forms (not in HTML+ spec yet).
image/*,
audio/*) for debatably broken CERN server.
~/.mosaicpid.
useDefaultExtensionMap, default true, can
be set to false to keep Mosaic from having any default
extension mappings. We strongly recommend that this
resource be left true; simply override as necessary. See
information on
extensions recognized by 2.0pre4 by default.
globalExtensionMap, default
"/usr/local/lib/mosaic/mime.types", can be set to the location
of the system-wide extension
map config file of your choice.
personalExtensionMap, default
".mime.types", can be set to the location of the personal extension map config file of your
choice -- the value of the environment variable
HOME is prepended to this.
.txt and .TXT are always treated the
same).
useDefaultTypeMap, default true, can be
set to false to keep Mosaic from having any default type
mappings. We strongly recommend that this resource be left
true; simply override as necessary. See information on MIME
types recognized by 2.0pre4 by default.
globalTypeMap, default
"/usr/local/lib/mosaic/mailcap", can be set to the location of
the system-wide mailcap (type map
config) file of your choice.
personalTypeMap, default ".mailcap", can
be set to the location of the personal mailcap file of your choice -- the
value of the environment variable HOME is
prepended to this.
copiousoutput, test, and
needsterminal aren't recognized either. We don't
know if these things are important or not
(needsterminal probably is but the others probably
aren't).
mosaic-internal-dump is used to tell Mosaic to
dump files of the corresponding type to disk (providing the
user with a dialog box to specify a filename). Normally this
"magic viewer" applies to all unrecognized types (including,
by default, application/octet-stream).
mosaic-internal-reference is used to tell Mosaic
that it has native handling capabilities for this datatype.
This should only be used for HDF and netCDF data files,
and only with versions of Mosaic that have native HDF support
compiled in. By default this "magic viewer" applies to
types application/x-hdf,
application/x-netcdf,
application/hdf, and
application/netcdf (the latter two aren't valid
MIME types at the moment, but should be someday).
In conjunction with NCSA HTTPd 1.0a2 and later, this means graphical overviews of distributed information spaces are now easily doable (a single image map can essentially point to lots of URLs scattered all across the Web). An example is here.
<BASE HREF="whatever"> to
allow specification of a "real" URL inside an HTML document.
(This is a convenient way to have WAIS server access not screw up
URLs of documents that normally exist in a hypermedia hierarchy,
or in any other instance where the same document, especially when
containing relative links, is served off of more than one
server.) An example is here -- the document is physically located at "http://hoohoo.ncsa.uiuc.edu/Mosaic/foobar.html" but the "real" URL is specified in the document source. Inlined links specified with relative URLs, and relative hyperlinks, work.
delayImageLoads can be set to true (or command-line
flag -dil) to cause inlined images to not be loaded
by default.
ISMAP images
reasonably in this context.
<IMG ALIGN=MIDDLE> is now supported.
The specfile itself consists of alternating lines of title and URL; a single line starting with two dashes ("--") between any two title/URL pairs counts as a separator. By default up to 80 things (title/URL pairs + separators) can be in a specfile; this can be increased in src/gui-menubar.c if you're crazy. An example specfile is distributed with the source code (but is not intended to be a default).
The developer who implemented this feature disagrees with its presence in the program; the contents of such a customizable menubar ought to be in a hypermedia page (so you can actually format, lay out, and explain the various hyperlinks) that in turn ought to be served to the network (so others can benefit from your organization of information).
gopher//mother.cs.bham.ac.uk:2070/.
It seems to work best with not too wide windows (otherwise the page get scaled down, and so the fonts will get smaller too) and it is best to use times font (you may prefer to select the small times font from the option menu before printing/saving in Postscript format).Documents that show up badly in Mosaic, will do so in the postscript. The output uses the placement calculated by the browser. It does not reformat the document. This implies amongs other things that no word wrapping is done.