Proofing tools (spell check, theasaurus, autocorrect)
One of the defining features of office down the years has been the proofing tools (i.e. Spell checker, theasaurus, autocorrect, grammar checker). I would love to see these come to Teams.
The way I envisage this working is as I'm typing a message the famous red/blue/green squigglies that we've all become familiar with should show up.
Most of all I'd like autocorrect (i.e. a spelling correction that I've used previously automatically gets applied as I type). Stretch goal for this, have a single set of autocorrects that work across all of Office 365, including the client apps.
Some people might think that such tools would not be applicable to a lightweight tool such as this (I would disagree, but everyone is different) so perhaps there should be the ability to toggle proofing tools on and off.
It should work across all Teams clients (i.e. desktop/mobile/web).
I must admit I'm not a user of Teams yet (although soon will be - our org is turning it on soon) so for all I know some of these things already exist - I somehow suspect that they don't all exist yet though. Most of all though I'd like the autocorrect feature and the red squigglies.
Hi everyone, the engineer working on this item has left the company and we’re working on replacing him. I wanted to give you that heads up because the work has paused, which extends our shipping date.
I really appreciate your patience as we work to get this back to actively worked on.
Teams should use the same spell checker as Word. That is, Teams should not flag words as misspelled that Word does not. Examples: outliers, comorbidities
We have just moved to O365 in my company. We use a lot of non-standard words in the aviation industry and would value this becoming a reality. The fact that Office spell-checks in English, whilst Teams spell-checks in English (US) [whatever that is] is a nuisance. Particularly when, as an Analyst, I analyse a lot. I notice that this site is spell-checking correctly in English as it didn't try to throw a Z into that last sentence.
This should be a feature already. It would be better if uses the same dictionary as other Office products.
Osvaldo Yariwake commented
@Suphatra have you any update to us about this topic please?
Edward L Jaquay commented
Please post ETA of the implentation of custom dictionary.
Is it me or something changed about a week ago? I am using Teams in French. I never noticed squiggles (or maybe there was but not a lot) but since about a week or so, spellcheck adds squiggles under any non-English word in Teams.
I did not find any way to disable the squiggles or change the language.
Being able to diversify your words is vital to capture your Teams attention. Applications in the Microsoft Office "Suite" have the thesaurus function.
Dmitri Lipetski commented
Just gave it a vote! Any status update? :)
Enrico; Don't be so lazy - just type using the Shift button and the letter "i". It's not that difficult.
now "i", in the sense of me, does not capitalize automatically
Adding my vote for this feature, any news?
Brad Mergenthaler commented
Autocorrect marks product intelliport as misspelled and suggested tortellini? - No add to dictionary option?
Are applications still open for this engineer? If nobody else wants the job, I'll apply - I can spell, I have good grammar and I can even code! And the fact that I can't change the spell-check language in Teams from US English to any other sort of English (ie. "Rest of the world" English) is a real pain. Would love to have it fixed please :)
Any progress on this?
Cosme Silva commented
I do want this feature available on Teams.
Jordan Smith commented
Any update on the progress of this? / The ability to add custom words to avoid it being flagged in the future.
William R Vaught commented
need to add words in to the Teams Custom Dictionary or attach it to an Office one
This is especially handy when you use "auto-correct" to expand acronyms, such as: plmk = Please let me know...
Would love to know the status of the replacing engineer - this feature is needed in Teams badly!
Jean Marc Berlandi commented
This is to me a standard requirement, I am surprised it is not yet available