top | item 45719746 (no title) pcwelder | 4 months ago I ϲаn guаrаntее thаt thе ОСR ϲаn't rеаd thіs sеntеnсе ϲоrrесtlу. discuss order hn newest syntaxing|4 months ago What’s correct though? Even as a human, I read that “correctly”. Using weird representations of C doesn’t change the word? LudwigNagasena|4 months ago I would even say that OCR can rеаd the sеntеnсе ϲоrrесtlу, while a tokenizer can't. load replies (1) metalliqaz|4 months ago Yeah OCR would be much more likely to read that sentence the way a human would. bitdivision|4 months ago A lot of Cyrillic characters: https://apps.timwhitlock.info/unicode/inspect?s=I+%CF%B2%D0%... geysersam|4 months ago Really? How so? moduspol|4 months ago Looks like he’s using atypical “c” characters. load replies (1)
syntaxing|4 months ago What’s correct though? Even as a human, I read that “correctly”. Using weird representations of C doesn’t change the word? LudwigNagasena|4 months ago I would even say that OCR can rеаd the sеntеnсе ϲоrrесtlу, while a tokenizer can't. load replies (1) metalliqaz|4 months ago Yeah OCR would be much more likely to read that sentence the way a human would.
LudwigNagasena|4 months ago I would even say that OCR can rеаd the sеntеnсе ϲоrrесtlу, while a tokenizer can't. load replies (1)
metalliqaz|4 months ago Yeah OCR would be much more likely to read that sentence the way a human would.
bitdivision|4 months ago A lot of Cyrillic characters: https://apps.timwhitlock.info/unicode/inspect?s=I+%CF%B2%D0%...
geysersam|4 months ago Really? How so? moduspol|4 months ago Looks like he’s using atypical “c” characters. load replies (1)
syntaxing|4 months ago
LudwigNagasena|4 months ago
metalliqaz|4 months ago
bitdivision|4 months ago
geysersam|4 months ago
moduspol|4 months ago