[WEB4LIB] Re: Uploading graphics

[Dennis Moser]

Oh, boy. Before this gets TOO far:

What was meant as a gentle jibe at Windows users has gotten out of hand.
Here's the offending phrase that apparently started things...

"As for using upper case, you can usually tell who's using a Microsoft
product for serving their pages since they announce that one should NEVER
use upper case in file names. Use what makes sense...just keep it
well-organized. The real problem (on almost ANY platform...can't think of
any right away to the contrary) is having SPACES in the file names. (I did
see some in your directory/path names in your code...)"

There's nothing in there that's "incorrect" with regard to NT...nothing in
there that mentions any SPECIFIC Microsoft products. As for any subsequent
postings that might have contained erroroneous information about such
products, I cannot take credit.

Lighten up...my main point was that one's approach for naming MUST be
consistent. That isn't such a no-brainer as some would suggest. Those of us
who are daily immersed in code need to remember that there are some
neophytes on this list and what we take to be common sense may not be so
common.

What really matters is that Cathy Cox got her images to appear: she probably
needs to be looking at what caused her file name extensions to change, but
hey! that's for another discussion.

Sending a million "Mea culpas" to Redmond, I retreat while wishing Holiday
Cheer for all who participate (an Amazing Full Moon this morning!),

Dennis Moser, MILS, Web Librarian
John P. McGovern Historical Collections and Research Center
Houston Academy of Medicine-Texas Medical Center Library
1133 M. D. Anderson Blvd, Houston, TX 77030-2809
dennism at library.tmc.edu

-----Original Message-----
From: Dan Lester <dan at 84.com>
To: Multiple recipients of list <web4lib at webjunction.org>
Date: Wednesday, December 22, 1999 10:10 AM
Subject: [WEB4LIB] Re: Uploading graphics


>At 04:51 AM 12/22/99 -0800, Debra Lords wrote:
>>Actually, planning on case insensitivity is incorrect.  Depending
>>on the WebServer (not the OS of the box, but the WebServer
>>Engine), case sensitivity can be a factor.
>>
>>Compare:
>>http://www.cs.utah.edu/~bean/research.html
>>http://www.cs.utah.edu/~Bean/research.html
>>http://www.cs.utah.edu/~bean/Research.html
>
>No one said that you should plan on case insensitivity.  The message said
>that on MS's NT and IIS it was insensitive.  And that was said in response
>to a specific incorrect comment about NT.
>
>I think we're all in agreement that you should ALWAYS use lower case, NEVER
>use spaces in a file name, in order to maximize ease of access.
>
>My personal suggestion is that you never use underscores, as they're easily
>missed by the novice when they get hidden by the underlining in a link.  I
>also always use . (periods, dots) between parts of file names when I want
>to distinguish words for another reason.  They're much easier to type than
>an underscore or a hyphen.  o-)
>
>cheers
>
>dan
>
>--
>Good, Fast, and Cheap: Which two of the three would you like?
>Dan Lester, 3577 East Pecan, Boise, ID 83716 USA 208-383-0165
>dan at 84.com   http://www.84.com/  http://www.postcard.org/
>
>