Yup.
> I would think it wouldn't be too hard for the client to display a
> small bitmap instead of a bullet when it sees something like this in
> the link.
Because the Gopher communications module simply produces a HTML stream
(either tokenized or raw) that looks like:
<ul>
<li> <a href="gopher://blahblah/blah">An entry.</a>
<li> <a href="gopher://blahblah/blah">An entry.</a>
<li> <a href="gopher://blahblah/blah">An entry.</a>
</ul>
...or something similar. Yes, this could all be hacked so the Gopher
stuff is handled extra-special-different, but it would be much cleaner
to simply support the concept of arbitrary icons as bullets in
unnumbered lists. I think.
> As soon as you move out of gopher provided information, the problem
> becomes very murky, and an optional parameter like the one you
> suggest would probably be just about the only way to do it without a
> lot of headaches.
Cheers,
Marc
-- Marc Andreessen Software Development Group National Center for Supercomputing Applications marca@ncsa.uiuc.edu