There are times in my WIP that I write a line like this:
Marvin— or was it now Vinny?— scanned the room.
This might be questionably grammatical, but I want to be able to leave the “s” after the dash uncapitalized. In MS word, it would be automatically capitalized, but I can use “undo” to permanently remove that capitalization. In Scrivener, on the other hand, “undo” only temporarily removes the capitalization, which reappears the moment I type something else. I want to be able to keep automatic capitalization on, but be able to remove this capitalization if I choose to.
Not sure if this is a bug or just a functionality thing, but I thought I’d report it!
I found this too, although in a different context. I’m a complete newbie to Scrivener, but I thought I’d try it out in the context of technical documentation. I love Scrivener so far - it really suits the way I think about documents - and I’m delighted to be able to contribute in some small way.
I found that:
Any embedded punctuation causes capitalisation of the following character (if it’s alpha).
Any end-of-word condition will cause an evaluation of the auto-capitalisation of the current sentence. This means that if you undo the auto-captialisation, it will be redone next time you end a word.
When you have multiple embedded punctuation marks, re-capitalisation occurs only after the last punctuation character.
An example:
Syntax: dbanalys2csv.py filename1 [filename2 ...]
Typing this results in undesirable (and incorrect!) capitalisation.
Not sure how to suggest fixing this, since incorporating memorisation of undo would no doubt be tricky. How about an annotation or format which indicates that the characters in that format are literal? This would also be useful for compilation/generation, since strings like the above are typically rendered in a different font-face than the bulk of the document’s text (e.g. Courier or some other monospaced font).
On a related point, undoing the auto-cap using Ctrl-Z leaves the cursor after the undone letter, not after the just-typed whitespace (or whatever). It should leave the cursor where it was.
Thanks for a great product, and I look forward to using Scrivener for some time to come.
I, too, am having issues with this.
I actually like auto-capitalization for the most part, but there are times when I want to be able to manually not capitalize.
I’d just like it to recognize, if I go back and uncapitalize, or arrow out of a word, or something that it shouldn’t need to capitalize.
I know it’s a small thing, and it likely wouldn’t be a make-or-break for me buying the program, but, since the point of beta is for the developer to learn about the issues that are bothering users, I thought it was worthwhile bringing up.
Thank you, GeoJunkie. It’s good to know that this has been recognized and is being dealt with. I wonder why that thread didn’t come up in my search for capitalization issues…
Anyway, I probably would already have been typing by the time Jaype had posted the acknowledgment of the issue; I think our posts are only a few minutes between.