

Woah, that’s fucked up. But LLMs have very different performance by language so I think Czech responses are largely based on Czech-language data (maybe with training dataset augmentation with auto-translated works, judging by the literally translated technical terms). And I don’t think this would happen in my country.

The thing is, if I don’t add a “good enough for searching” OCR layer, someone else will - AI scraper or legitimate user. That’s a cheap automatic operation. I’ll better do it myself and poison it in a way that won’t interfere with searching, like replacing some “are” with “aren’t”, such common words are rarely searched for. If there’s a chance AI will fall for the metadata and invisible layer contents, that will decrease the requirements for visible poisoning, which is necessary but annoying.
Some of the text is indeed justified so I could do the multi-column trick that seems like the best compromise. The gap can be as narrow as one space. Or larger if I can write a script to detect lines and connect the columns with gibberish. A human can use zoom or window positioning to view one column at a time. I don’t and will never have access to files the printouts are from (some are presumably in
.602format, others probably.doc), others are handwritten or typewritten, some have images glued on top or hand-traced; and Czech OCR is only about 99.5% reliable so as easier as it would make the endeavor, I can’t be sure to preserve everything if I try to convert them into editable documents as an in-between step.