3 ms·
I'm not sure of the details. I vaguely recall there was a version mismatch with the provider's API, and at one point they were sending UTF-8 data when the heade
by orangecat 16y ago
I'm not sure of the details. I vaguely recall there was a version mismatch with the provider's API, and at one point they were sending UTF-8 data when the header said UTF-16, or vice versa.
- GFischer 16y agoI've had that problem before, it's not hard to fix if the provider helps (OTOH if the provider doesn't, I guess some hacks should do the trick as well). I'm not at the office so I don't have the code at hand.