Erm...no, sorry, that wouldn't help. Let me explain what that trick is about...it was a guess, first of all, because I don't have an Intel mac and I haven't seen many threads about Rosetta getting stuck like this.
Plist files are a universal way in which preferences and other app data are stored on Macs in a format based on XML (I think). This extends not just to preferences you set, but preferences one part of the system sets on behalf of another. Whenever a program is run for the first time, it creates the plists it will use based on templates internal to the application. Normally, life will be fine after this, and the app will refer to the plist as necessary. Occasionally, the plist file will become corrupt. This will lead to unpredictable or failed behavior when the app tries to use it. Unfortunately, OS X does not appear to be perfect at recognizing this situation for itself. In Tiger, for instance, a new feature was added in which, when a program crashes, you are given the option to delete preferences and re-start it.
However, a lot of times, it does not realize this problem, and you have to give it help. If you delete the file and restart the program in question, it will notice the file is not there, and then create a fresh (uncorrupted) copy of it. This solves a lot of miscellaneous problems in OS X....
But not yours, clearly. So back to square one.
