Quote:
Originally Posted by phossler
Thanks for the information. I had thought about a RegEx to replace 'a.m.' with just 'am' etc. but then i thought that if the 'a.m.' was at the end of a sentence, I'd only make things worse
|
All the variants of periods/no-periods + lowercase/uppercase AM/PM (and acronyms) were discussed in these topics:
They discussed lots of helpful regexes + edge-cases + tips on how to catch/fix/normalize these types of issues.
- - -
Side Note: And Kovid is right. It's a hard problem with no real solution.
Just
Right-Click > Ignore the red squigglies in these few cases + come up with a few regexes to check for the common edge-cases. Like:
Search: \b[APap]\.[Mm],
Search: \b[APap][Mm]\.,
which would check for a.m. + p.m. missing a period followed by a comma.
If you make use of
Saved Searches this can be as simple as a single run of a Group.
- - -
Side Note #2: If you want extreme details on "sentence-ending periods" and why you don't want to enable spellchecking periods at end of words... see my discussion in:
Sigil 1.9.10+ made that change, and I was
STRONGLY opposed to it. The amount of clutter and mess it introduced into the Spellcheck Lists was immense. Heavily outweighed by the handful of acronyms like "a.m." + "p.m." you'd have to check.
In
Post #21, I even showed graphs of "Sentence-Enders" vs. "Acronyms", where 0.2% hits were "corrected", but 99.8% hits were made much worse.