Interesting post. I had not come across History Explorer before, so I went to the site and took a look around. It looks like a rather nifty document version backup/restore software.
I would suggest that the reason you have not had a response to your report of this "nasty & well hidden bug" is possibly because the software developers might not regard it as a bug at all. I recall that the DOS/Windows operating system did not used to accept as valid any characters that were (from memory) NOT in the ranges:
- Numeric: 0-9
- Alphabetic: A-Z
- Special characters: ().SPACE
(I'm sure someone in the DC forum reading this would be able to specify exactly what the filename validation criteria were and currently are.)
The OS is a bit more tolerant now, but even so a lot of software continues with the historic standard for filename validation criteria.
Not surprising therefore that filenames with things like double quotes (")and hash marks (#) still throw some of these applications into a fit.
I have tripped over this problem so many times over the years that my approach now is that it's better to err on the side of caution and avoid using anything but the LCM (Lowest Common Denominator) - i.e., the base filename standard.
"a few niggling issues"wraith808:
Would you mind providing your "review" of this product? I am thinking about buying a licece after reading this post, but I would like to know what you meant by "a few niggling issues".