4 ms·
I suppose the problem is not perl being lied to, but storing unicode (utf-8?) in a field designated as latin-1. That’s bound to cause issues down the line.
by bouke 5y ago
I suppose the problem is not perl being lied to, but storing unicode (utf-8?) in a field designated as latin-1. That’s bound to cause issues down the line.
- Arch485 5y agoOh absolutely! Unfortunately we can't just change our databases text encoding... Luckily the database doesn't change any of the data, so it should be okay with some fixing.
- wiml 5y agoWell, the database was lying to Perl, perhaps. But I'm not sure the author's diagnosis is correct. The mangled text has only one "?", Which means that whatever software did the mangling knew that two-byte sequence represented a single character. Maybe whatever was reading from the database was(I'm assuming MySQL since 1990s vintage) using a non-Unicode-capable connection?