On my MacBook Air, while typing a phrase including “quick look” I found that those two words were capitalised. I corrected to lowercase and immediately saw a popup offering me “Quick Look”. I made a few repeats and found it happened every time.
I spent some time RTFM’ing and found references to project settings autocomplete list but that was empty. In general settings, capitalisation is checked as is ‘only suggest completions from custom auto-complete lists’ but I have never made such a list. There was also a suggestion that it could be coming from some system setting - but no, it doesn’t.
I’ve no idea why ‘quick look’ should ever have merited capitals and I can edit my thoughts to avoid using that group of words, but I’d still like to kill that offering by Scrivener to avoid having to stop typing to kill the popup.
Thank you RuffPub. I hadn’t seen this in any other application but Scrivener. I just checked further and it does the same thing in Apple Notes but not in Pages, nor in LibreOffice or any other application where I’ve tried typing ‘quick look’.
I had looked in the Text Replacements under Keyboard settings but there is nothing there.
I have prevented it, though, by editing ‘Input sources’ and deselecting ‘Capitalise words automatically’.
But I fail to understand why the combination of those two words should trigger the capitalisation. I certainly never specified it.
But it’s not a problem unique to Scrivener. Thanks.
Perhaps because “Quick Look” is part of Apple terminology—it’s the system by which, for instance, you can view a document or image by simply selecting it in Finder and tapping the Spacebar. Scrivener makes use of it for e.g. displaying Scapple boards.
So maybe it’s TextKit simply getting it wrong… does it do it in TextEdit? If so, TextKit is where the problem lies. Pages uses a different, proprietary text engine, so is not a good comparison; I don’t know about Notes.app.
Hi Mark. I didn’t know that Quick Look was part of Apple terminology. That probably explains it. Although I’m using a MacBook, it’s the first time in a long life that I’ve gone on the dark side - my desktop of preference is linux with a W10 machine for those few apps that don’t play too well with Linux.
I got a new portable after ten years without one and bought Mac because of family connections. I like being able to work on a modern portable but I don’t use any Apple apps. I’ve installed applications that I know and with which I’m familiar.
For the same reasons, I hadn’t heard of TextEdit. But I found it and, yes, the same problem is there too.
So, I’ve eliminated it by unchecking the ‘Capitalise words automatically’ but then it doesn’t capitalise the first word of a sentence in those two Apple apps. But Scrivener and LibreOffice take care of that - so all’s good on the working side.
I suppose TextKit is TextEdit’s text engine and not able to be modified by us users?
You can’t modify TextEdit, but it’s Apple’s showcase for the TextKit text engine on which Scrivener and many other apps are built or make use of. So, if you find something weird like this in Scrivener, TextEdit is the first place to test whether it’s a Scrivener problem or not.
To us Mac-users that refers to Windows!
I have spell checking, etc. turned off; I do all that post-compile in my word processor.
