You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
The Apple spellcheck engine does not recognize misspellings on UPPERCASE words in Pages, TextEdit, or FinalDraft software, which also uses the built-in spellcheck engine. This has been an ongoing issue for several years (since 2011, at least). When will Apple solve this issue? It's a HUGE problem when using FinalDraft.
MacBook Pro 13″, macOS 10.14
Those are considered to be acronyms, and not spell-checked.
If you want to do that, select the text and format it as uppercase.
Format > Font > Capitalization. All Caps
Otherwise, log feedback with Apple: Product Feedback - Apple
Those are considered to be acronyms, and not spell-checked.
If you want to do that, select the text and format it as uppercase.
Format > Font > Capitalization. All Caps
Otherwise, log feedback with Apple: Product Feedback - Apple
Apple participation in this user-to-user community is limited to moderation to ensure adherence to the terms of use agreement and to Community Specialists—Apple employees who monitor the discussions for posts with no replies within a reasonable time after posting a question. Their responses generally provide links to knowledge base articles likely to be useful in answering the question asked.
ALL Apple employee submissions here may be identified by the Apple logo included beside the name of the person posting, as can be seen in Joseph S's post here: collaboration - Apple Community
Regards,
Barry
PS: I would replace "Most" in MrHoffman's most recent post with "Almost all."
As it turns out, LibreOffice Writer has a spelling correction option to check uppercase words. Probably in MS Word too.
Sometimes, it pays to have the right tool for the job, rather than waiting for Apple or Final Draft to change things.
Feedback has been logged. This hack/workaround does not solve the FinalDraft issue AT ALL, and should not be necessary in either case. Yes, the developer has been made aware of this problem, and their hands are tied to Apple's spellcheck engine, so there's currently nothing they can do to fix it, other than maybe developing their own engine, which hopefully they will do.
Thanks for that VikingOSX, I am already aware of what you're sharing here. However, the solution to this issue should not be in finding workarounds or alternatives, but fixing the root of the problem, which is Apple's spellcheck engine. FinalDraft has been the "right tool" for two decades, and now it's broken. Apple and FD should work together to fix this.
Thanks, MrHoffman. I have been, and currently am in contact with FinalDraft's VP of Customer Support. That's how I got here. They've been aware of this issue for some time as well, and feel their hands have been tied (to Apple's spellcheck engine). It seems to me quite sloppy of Apple to not have resolved this, since it affects their software as well (Pages, TextEdit, etc) which I also use regularly. I hope Apple can work to resolve it at the source, instead of offering patch-hack workarounds.
Apple very deliberately did this many years ago, I've certainly long depended on uppercase being acronyms, and I'm very far from alone with those assumptions.
If you need uppercase spell-checked pending some hypothetical changes in some hypothetical future macOS release, use a different tool, or use the previously mentioned all-caps format.
wneary wrote:
Thank you again, MrHoffman. Are you an Apple representative, or employee?
I do not work for nor represent Apple.
Most folks here are other users, volunteers, and not folks that work for or at Apple.
The behavior reported in Pages and in Apple Spellcheck is longstanding.
Log feedback with FinalDraft, too.
Thank you again, MrHoffman. Are you an Apple representative, or employee?
Spellcheck UPPERCASE
