The fact that this can introduce OCR bugs into your C code is hilarious, and this is diabolical:
#define one ( 4 - 3 )
#define eleven ( 3 + 4 + 4 )
Especially if your fax machine uses JBIG2 compression. See: https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i...
¹: http://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_...
Like, sure, maybe it's hard to tell apart a "1", "i", or "l" purely visually, but if you knew it was supposed to be code, I'd suspect one could significantly improve the recognition accuracy if the system just worked in the probability of each confusable option given the preceding (and following) text.
It's actually better for the compilation to fail than for the Clippy to make up something syntactically and compilation correct, but wrong.
edit: fixed link, copy paste fail dropped the ++