Re: .bin files, NODOC/DOCURL, and icons?

[Earl Hood <ehood@hydra.acs.uci.edu>]

On January 25, 2002 at 02:20, Paul Thomas wrote:

> --0-1594952185-1011745224=:66661
> Content-Type: image/pjpeg; name="image.jpg"
> Content-Description: image.jpg
> Content-Disposition: inline; filename="image.jpg"
> Content-Transfer-Encoding: base64
> 
> and the jpg's are being saved as .bin files as such:
> 
> <p><a href="bin00008.bin" ><img src="bin00008.bin" alt="image/pjpeg"></a></p>
> <p><a href="bin00009.bin" ><img src="bin00009.bin" alt="image/pjpeg"></a></p>
> 
> Does Mhonarc not like: Content-Type: image/pjpeg?

image/pjpeg is currently not in the mime mapping table in
mhmimetypes.pl.  The mhexternal.pl filter falls back to
application/octet-stream for unknown types.

You could try the "usenameext" and "inlineexts" options the
mhexternal.pl filter to work around the problem.  Or, add an entry to
the hash table in mhmimetypes.pl.

BTW, what is a "PJPEG" file?  How is different from a regular JPEG
file?

> 2. I dug through the docs and finally found I could pub <NODOC> in
> my -rcfile and the default footer goes away. I haven't quite figured
> out how to replace it with my own footer using presumeabley <DOCURL>.
> Any tips on how to do this?

You would need to modify the the various *END resources for
each page type as listed in the Page Layout section to define your
own footer.  The DOCURL only changes the URL used in the default
DOC footer.  If you use <NODOC>, you have to roll your own footer.

Note, you can use DEFINEVAR to define your variable containing the
markup of your own custom footer, and then just reference the variable
in the *END page resources to avoid duplicated the footer markup in
multiple locations.

> 3. While I'm at it. Does anyone have any suggestions how in my
> Date Index (and perhaps Thread Index), I can have an icon indicating
> a viewable image file is contained in a particular email. The
> goal is to enable someone looking at the Date/Thread Index and at 
> a glance see what archived emails contain a viewable image file.

The closest you can get is using the ICONS resource with the $ICON$,
or $ICONURL$, resource variables.

--ewh