For those unaware "Grauniad" is a decades-old nickname for The Guardian, used particularly by satirical mag Private Eye in reference to its reputation at one time for typos and the like.<p><a href="https://wordhistories.net/2017/06/05/origin-of-grauniad/" rel="nofollow">https://wordhistories.net/2017/06/05/origin-of-grauniad/</a>
When I saw “13,000 regexes” I thought of the adage, “the plural of regex is regrets”.<p>But here it seems like a good choice to build on a battle-tested library of regrets, and it's clearly working well for them.<p>The demo looks slicker than the typical Grammarly/MS Word/native macOS grammar and spelling corrections, for those who missed it: <a href="https://www.youtube.com/watch?v=Yl0nb94N98k&feature=emb_imp_woyt" rel="nofollow">https://www.youtube.com/watch?v=Yl0nb94N98k&feature=emb_imp_...</a><p>And the ability to flag false positives, send suggestions back, and see metrics of how the system's being used is just awesome.
As a college student (nearly 20 years ago) I built a tool for our student newspaper that caught frequent violations of the Associated Press style guide. Later, working as a newsroom copy editor, I was shocked at how few tools there were available to enforce style. Really awesome to see this Typerighter tool do it right.
This is wonderful. I love to see technology enhancing experts' ability to do what they already do, but faster/more accurately.<p>Also, I'm a big fan of regex. I think -- probably thanks to jwz's famous quote -- a lot of younger programmers avoid them but they're fantastic for MATCHING. Using them in a Google sheet is a killer MVP to prove out something like this.
Relying on purely on regex misses so much context available from a document. I've been working on some tooling [1] in this space recently and a core epiphany was noting you can model written language as an AST and then reason about it in this form rather than opaque blocks of text (or flat, sequential text fragments as with Typerighter). An even better realisation was that others had already noted this too and built a mature ecosystem based on this concept [2].<p>[1]: <a href="https://github.com/place-labs/orthograph-err" rel="nofollow">https://github.com/place-labs/orthograph-err</a><p>[2]: <a href="https://textlint.github.io/" rel="nofollow">https://textlint.github.io/</a>
This project reminded me a proselint, which appears to be a similar style checker. Sadly, that project appears to have been inactive for at least three years.<p><a href="https://github.com/amperser/proselint" rel="nofollow">https://github.com/amperser/proselint</a>
I saw a journalist share Typerighter on Twitter and was intrigued, so I'm looking forward to reading this.<p>It's a bit surprising that the engineering blog appears to be embedded in the main site, though. I've worked at a news org in the past (admittedly much larger) and the engineering/meta blogs were entirely separated from the main news section. Obviously it doesn't make sense to reinvent your stack, but I'm surprised the surrounding site scaffolding isn't at least distinct to show this isn't primary news output.
Is there a link to a list of the style rules their checker tests for?<p>I've always felt automated checks + fixes for grammar and style are miles behind where they should be by now. Checking over and over e.g. long emails for problems before you send them is super time consuming, and that's not even considering help with tone and the overall message.
Funny, though I am unshocked that they have figured out a way to automatically generate cant.<p>What does make it interesting is if it were applied as a GPT-2/3 module, and let loose as a reddit comment bot to train a model for engagement and provocation. Editors are essentially model supervisors, and if the object is to provoke and flatter people to sell advertising, it seems more like a compute problem to distill this process into a business.<p>Human writers creating organic content aren't really necessary for that, and very soon we should be able to generate content and then attribute it to loyal personalities that we stand up as minor celebrities, not unlike the old Hollywood studio system from the early 20th century, where talent was well kept, but still very much kept.
Damn! That's the kind of thing my company could sell to its clients. And that's exactly what I'm going to tell my colleagues! Thanks a lot
“ The rule application service is written in Scala, a common choice for Guardian backends”<p>They even have a snippet of Scala code. I feel like HN must be the target audience
Software in the 21st century: to check a bunch of regex on a text you need: Grafana, APIs, services. Really? I'm surprised there is no k8s in here. /s