Weird HTML formatting problem

[waydwolf]

    I've been trying to do some editing of an old web page I saved from my former site and I've noticed that a lot of the pages aren't loading images right.

    So I check and I find that some of the files have a different case than the entry in the HTML.

    I go through every page in both Front Page and Netscape Composer, re-referencing every image by file name, and even checking the source to make sure case matches. whatever.jpg instead of whatever.JPG and so on.

    Instead of what I entered before saving and publishing however, the filenames seem to revert in the files as if the editors are renaming them by some weird self-correction rule.

    Ignoring Netscape Composer, I do some experimenting with Front Page and find that in some instances, I can change a file extension case in the source even and when I go back to that page after saving and checking the image properties, it has gone back to all uppercase, i.e., .JPG.

    And yet in other images, I can change it to all upper and it changes itself back.

    Anyone have an idea of what is going on? I'm about ready to re-build from scratch in Notepad. I'd prefer WYSIWYG but I haven't seen this level of insanely counterproductive "features" since HoTMetaL Pro.

 

 

[firephoto]

I think those programs do go through and resave your files in the way they think they need to be to work right. Composer probably has a setting somewhere to turn this off. My experience with microsoft and html is that they have strive to make sure that it's saved in the way they want it and not the way you want it. It could have to do with the programs wanting to "publish" the files too. I usually just edit the html with something and make sure it just saves the html file where I want then I upload with WSFTP.
Macromedia has some nice aps for some $$$. I've used Dreamweaver and it will do just about anything you want too do.