Closed iainelder closed 1 year ago
You can do this with a custom vocabulary.
It probably would also be useful to ignore some of the well-known ones by default.
Thanks, @jdkato. I already use a custom vocabulary for spellchecking.
I don't see how it helps with the HeadingAcronyms rule.
Do I need to change a setting?
If you have a term, such as "JSON," in your accept.txt
it won't be reported by Microsoft.HeadingAcronyms
.
It works for me! Thanks.
Is there way to do this?
Some technical acryonyms and initialisms are better understood than the phrases they stand in for.
XML? JSON? SQL? Not even Microsoft spells these out. JSON is already pronounced as "jason" and SQL as "sequel".
As a workaround I can just disable this rule.
With an acceptance list it could help to keep uncommon jargon out of headers.