Publishing bug with FTP servers - Spaces at end of file/folder names

Question

I'm sharing what I've found after lots of troubleshooting with my Mom's iWeb website. I originally came across this in the previous version of iWeb, and have seen it again in the current version.
For the sake of this example, she had an image gallery on her site. The image file she added to iWeb had a space at the of the filename, just before the file extension, something like "image name .jpg"
In the old version of iWeb (iWeb 08), we would publish the site to a folder on her computer, and it would generate a folder for each image in the gallery. These folders would hold the original image and thumbnail image. Each folder name was the image's filename, minus the extension. In this example, the folder name was "image name " with a space at the end, which is valid on the Mac OS X file system.
When we uploaded it to the FTP site (which happened to be GoDaddy) using a 3rd party FTP tool, certain images would always fail to upload. After much testing and troubleshooting with other FTP software, we found that the FTP server did not allow spaces at the end of folder names, and it automatically replaced them with underscores. So, we tried to upload a folder called "image name ", and ended up with one called "image name_". As a result, we couldn't upload any of the files that were supposed to be IN that folder, because it could not be found under it's intended name.
Fast forward to today, using iWeb 09. Now the software allows you to upload to a 3rd party FTP server, so we've stopped using the other FTP software and do it all in iWeb.
She added a new image to her gallery and tried to publish changes, and got the error: "There was an error communicating with the FTP server. Try again lager, or check with your service provider"
Once she removed the image, publishing worked again. It turned out the original image had a space at the end of the filename, just before the extension again. Once this space was removed, everything worked again.
Hopefully this helps somebody else down the road. If you have trouble with certain files, check them for spaces at the end, just before the extension. Perhaps in a future release, Apple could update the site publishing code to trim leading/trailing spaces from folder names.
If you've seen this before, or have any further questions/feedback for me, feel free to post a response. Thank you for reading.

Answer 1

It would be nice if Apple could make their error messages more descriptive of the actual problem so we have a better idea of how to solve it. I am "the mom" who had the problem B2Ben posted about.
The error message seemed to place blame on the ftp server or my ISP, consequently I wasted a lot of time with these people when it wasn't even remotely their fault.
As with most computer problems, I ended up learning a lot from it and it always helps with gaining confidence. This is my 20th year as a Mac user!.. yes, since 1989. I look forward to seeing what some of you have experienced with this same issue.
iMac GHZ PowerPC G$ Mac OS X (10.5.7)