Crashes instantly at the point of conversion. I gave it more than 20 .pdb files, all of which should have only plain ASCII (although if there is any formatting, I can't tell, because I can't open these files with anything other than plain text readers, which supply the title at the file start, but everything else is random text (assuming a compression scheme here).
This makes it pretty useless. It does the same thing on "View." It does the same exact thing whether dragged to the icon, to the dock, or using the open menu command or cmd-O. Once you click "select" it instantly and quietly dies. Even tried file and extension variations based on other comments... this is apparently not the cause. However, capitalizing PDB somehow makes it think the file is a text file, so it attempts to convert it INTO a pdb file, which does successfully create a file, but that's kind of useless, as the content looks even more trashed than the original, and since it warned me that there were illegal characters that would be skipped, I'm guessing a very large amount of "dead" was put into the newly created file, which cannot be read by anything available to me anyway for investigating...

Also note! It has a major HIG error... once launched, if you accidentally gave it a wrong file, hitting "cancel" does not get you out of the program... or the routine. You must either give it a destination, or cmd-opt-esc FORCE QUIT. Hitting cancel just re-opens the file save dialog box instantly... ad infinitum. At one point it even had two "Select Destination..." dialog boxes open at the same time... Wow!

Sad to give it a 1 in "value" but it doesn't work, so it has no value. I was so hoping to get something to open or translate these latest middle-finger salutes to the Mac community.

Using OSX 10.4.11 G4 1.2Ghz, 1.5GB, and more than 250GB of hard disc space... It's definitely not wanting for speed or space.

Please fix this, I would love to see it work, especially if it is unicode compliant, as well.

Argh! I love the app and use it daily but -- please, please -- I want the inverse of "ignore errors" -- it's not annoying, it's just ineptly helpful. Let it be more helpful, not ignored.

I want a list of what characters generate errors, so I can do back into the source doc and replace them!

Please, give us something that helps us identify what the problem characters are!

-- flags the unrecognized characters in a file?
-- lists them in a popup?
-- ideally, give us a column listing each unrecognized character and let us type in next to it a substitute and choose to make that permanent (and email it to you so you can build it into the next release)

Finding the danged problem characters is tedious. TextSoap doesn't do this either. You all should talk, either of you might implement this.

The only darned reason I wish I owned Microsoft Word is to be able to use its not-too-bad implementation of grep to find all non-ASCII characters for example.

I wish there were a window at all times so I could just drag and drop more than one file. I LOVE this app, and so far it works flawlessly for me on Mac OS 10.2.8. I can't find a good Windows ap to do this job at all. All either cost too much for my needs or don't install or work properly. I use the Windows machine at work and the Mac at home, so really - happy on the Mac anyway.

this new version is worse than before!! html conversion removed somehow.., and no longer support asia language!! useless for me now...

nice thanks. been looking for exactly this tool. thanks a lot dear developer!

OK, I found v3.1 on a backup, and it still works fine. Maybe it's a problem with having a G3, or having OSX 10.3.9. I found an old email for the developers I'll try.