No worries Keith. I was just scratching my head out loud to let the previous posters know someone else was seeing something similar, and moving towards understanding how things are configured in 2.0.
I’m happy to work with Courier Final Draft since that is my ultimate font when exporting to Final Draft. Again, I was just scratching my head as to why I still had Courier in my existing docs, whereas new ones were using Courier Final Draft. I’ll just use Documents > Convert > Script Format to get them all looking the same (the spacing between lines is visibly tighter using Courier Final Draft).
As mentioned before, I completely removed all traces of the 1.54 and 2.0 installations (including preference files), and did a clean install of 2.0. But I am still not getting proper behavior with triple periods in Script Mode. I just looked at this again, but performed a more thorough test with the Auto-Correction Preferences.
I un-selected the first four Substitutions in Auto-Correction Preferences, and tested them individually. When I turn smart quotes on, I get smart quotes while typing, when turned off, no smart quotes. When I turn em-dashes on, I get an em-dash while typing, when turned off, no em-dash. However, when I turn ellipses on and off, the result is always ellipses. This time I looked more closely and observed that when “Replace triple periods with ellipses” is turned on, the ellipses appear instantly when I’ve typed the third period. When “Replace triple periods with ellipses” is turned off, the triple periods are still there after typing the third period – but as soon as I hit the space bar, there is a brief pause and then they convert to ellipses.
I then re-selected the first four Substitutions so that smart quotes, em-dashes, and ellipses would be used as substitutions – but would be disabled in Script Mode. This was the default setup from the 2.0 installation. With these all selected – no smart quotes or em-dashes are created – but triple periods convert into an ellipses (after I hit the space bar, followed by a brief pause).
So something is still amiss here in San Francisco. I wonder if anybody else can confirm this behavior on their installation, or whether it is unique to mine for some strange reason?