Anyone have a workaround for this >4 year old problem with Autocorrect?

Apple's auto-correct is, shall we say, less than ideal and for some unknown reason never seems to improve. The only workaround I know if is to turn off Apple's spelling and grammar correction and use a third-party utility such as Grammarly, which has it's own sometime annoying issues but at least seems to know how to spell simple things like "at" and "these" which Apple's spelling system often flags as incorrect. You can try Grammarly for free and see if it does better.

Regards.

I've never experienced any problems like this and at the risk of stating the obvious and likely something you've explored, there is this:

❝When autocorrection is on, misspelled words are detected and automatically corrected as you type.

On your Mac, choose Apple menu  > System Settings, then click Keyboard  in the sidebar. (You may need to scroll down.)

Go to Text Input, then click Edit.

Turn on “Correct spelling automatically,” then click Done.

Note: To have the first word of a sentence and proper nouns (such as names of people and places) automatically capitalized as you type, turn on “Capitalize words automatically.”❞

Get typing suggestions and correct mistakes on Mac - Apple Support

🤷🏽‍♂️

D.I. I can confirm the behavior the OP reports. Type "The Bible" into TextEdit (or any other app) and it does indeed automatically change it to "the Bible" even when it's the first two words in a sentence and when "Capitalize words automatically" is turned on. I've experienced multiple such glitches with Apple's auto-correct, even to it claiming that the word "it" is misspelled, and that's with a brand-new system starting from scratch, not using Migration Assistant. I've reported these bugs to Apple engineering multiple times but it's never improved.

Regards.

Yeah, not doubting the experience at all, I just have never had these issues.

I'll be following this and wondering what the common factor is (?) in the systems of the folks who do have the problem.

Cheers(!) to hoping it gets resolved. 🙂

No idea. As I said, this happens even with a brand-new Mac running the latest version of Sequoia, and having set it up fresh so it wasn't bringing over a corruption of some sort, such as the contents of ~/Library/Spelling, from an older Mac. I first reported this sort of issue to Engineering three years ago but with no results. So if anyone has a solution other than the workaround I mentioned above, I'd be very happy to hear it.

I don't see it in an .RTF file type.

I changed the grammar/spelling settings a bit too and no change. Correct spelling was automatically checked.

I might have grammarly installed.

I tried single space and double space after a period.

There is a plain text file type that can be used instead of RTF.

I use RTF because it is more compatible with MS word.

Well, what do you know?! I do also see this behavior indeed!

I've a fresh install of Sequoia 15.2 on an external drive, and lo and behold, there is that bug!

Feedback sent. 👍🏽