Typing two hyphens does create an em-dash - make sure you are using beta 3 if you are not already (available via the Beta Testing forum) and ensure that the option is checked in the Typography options in Preferences.
Full screen mode should start where you are in normal mode, not at the top. However, there was a bug in beta 2 whereby this didn’t always work, though this is fixed in beta 3. So please do make sure you are using beta 3.
I for one am glad Scrivener doesn’t have autocorrect-as-you-type… When I must use Word, that’s one of the first things I shut off.
I used to have it on, and found that my fingers learned that ‘teh’ and ‘adn’ and other such typos were acceptable words, which meant that everywhere except Word my typing suffered greatly. By about a week after I shut it off, my typing accuracy had improved dramatically.
That’s good. I’ve also found the same problem with abreviations. Like S.F. or S.F.P.D. things like that, when they come in the middle of the sentence are hard not to get the thing to capitalize the next word. I can turn off the auto feature, but it’s nice how in word, if I just backspace, the automatic fix goes away.
Anyway you can make this happen?
That gets more complicated - remember that Word has a hundred people working on it and is a lot more expensive. What you can do is just hit undo (cmd-z), which will undo the capitalisation. The annoying thing is that the letter will be selected (part of the undo mechanism), though, so you will have to move your cursor back to where you were, but Alt-Right will do that for you if you are typing in a new document.
I don’t actually use auto-capitalisation, but I did turn it on accidentally today and noticed the same thing as Seth – if I typed “e.g.”, it became “e.G.” – I could see how this could get old pretty fast for people that do use the feature. Obviously, people should just turn it off if they’re annoyed by it, but I’d still call it a bug. In most languages, shouldn’t capitalisation be dependent on a full-stop/period or question mark (or equivalents) followed by a space? Anyway, I don’t think anyone regards this as a priority by any stretch. Maybe kill the feature?
But then most people use “eg. rather than e.g.” these days (even though the latter is technically correct). This is just a one-off case that will throw up problems. The auto-caps feature really is very basic (if a space follows a word that had a full stop, question mark, exclamation mark or ellipses before it, the first letter of that word will get capitalized). Those who don’t like it can just kill it via the Preferences. I will look at this case, though, as your suggestion to look for whitespace between the punctuation and the word to be capitalised does make sense.
All the best,
In most circumstances (with my readers and Princeton and with many academic publishers), if I used eg. rather than e.g., I’d get corrected. I think it’s cumbersome and unecessary, but what I think doesn’t seem to matter in such cases. Not that I use the auto-caps feature. But I just wanted to point this out about using e.g., or i.e., and the like.