The problem is that under Windows the case of the filename doesn't matter,
so unless you know that your site will be hosted on a Windows IIS server,
you should always use lowercase file and folder names without any spaces.
So in order the change the case, and have it stick, you would have to first
rename the file /folder to a different name, such as add a 1 to the name,
then renamed it a second time with the name you want.
Also if the remote site had the FP extensions, you should have open it
directly in FP, and then published to your local machine, not via the import
function.
I'm sorry Thomas, but that doesn't really answer my question.
It's not just the filenames that are now wrong, but the links in the 900
files. When FP changed the filename case, it didn't change the case of the
links, like you'd expect it to do. Rather than *creating* my web, FP
*destroyed* it. There's no way I'm going to hand edit those links, so I
need a tool or work-around to automate it, or some way to get FP to behave
itself.
Always using lowercase is easy to say, but not so easy in practice. Digital
cameras typically give you uppercase filenames, and some photo editors
default to mixed case or uppercase extensions. There's nothing wrong with
mixed- or upper-case filenames on web sites, as long as the links match the
filenames. I'd always use lowercase on URLs that people type, but for
internal files it really doesn't matter. FP really shouldn't be making that
decision for me, especially when it breaks everything in the process.
I used the import function because my ISP's personal web page server
doesn't have FP extensions. (And I have a dial-up connection. I'd rather
exchange files with the server once rather than 3 times, thank you very
much!).
