*** Start of undeliverable message ***
Message:
999999999
From: [email protected]@INTERNET at SMTPCC
Date: 04/13/95 04:29AM
To: roberta alberding at OCCSPOST
*** Unknown message recipient ***
Subject:
Contents:
*** No message recipients ***
999999999
Text item:
2042
>Sorry if this is a silly question...
>
The only silly question is the one not asked.. =)
>Photoshop 3.0 on a Mac (and, i think, GifConverter) automatically add .GIF
>(all uppercase) to my gifs, so I figured that was the way the world "wants"
>them. I recently changed all my html doc's to match (from .gif to .GIF). Are
>you saying I need to change everything to lower case? What about .JPEG .jpeg
>.JPG and .jpg? Is there a FAQ or other reference to such "standards?"
I don't think that filenams are really 'standards' per se.
>
>I already upload everything to my UNIX host binary (not Mac), and they seem
>to work on everyone's platforms (that I know of...). But, where would I grab
>the new FileBuddy 3.0?
uppercase/lowercase really dosn't matter to the system that's using them,
unless it's a case-sensative environment. if your filename is .GIF then
make sure it's uppercase in the document... if it's .gif make sure it's
lowercase in the document.. everything else (including case) is handled by
the browser at the time the document is translated. Most of them have a
built-in case-handling system.
[email protected] -------------------------------+----------------------+
_ /| | If you _really_ want to see what I would | GAT(GCS) -d+ -p+ c++ |
\,o.O' | like to put here, finger [email protected] | l u+ e+(++) m@ s+/++ |
=(___)= +---------------------------------------------+ n---@ h++ f(+) !g |
U | Please send all mail through [email protected] | w++ t++(@) r- y? |
Prodigy? Are you kidding? -------------------+----- AOL: Just say NO!
--------------- Start RFC822 Headers ---------------
Received: by occshost.nlm.nih.gov (5.65+/1.3)
id 21803.AA; Thu, 13 Apr 95 04:29:05 GMT
Date: Thu, 13 Apr 95 04:29:05 GMT
From: [email protected]@occshost
Message-Id: <[email protected]>
Content-Length: 0
Apparently-To: <[email protected]>
--------------- End RFC822 Headers ---------------