5 ms·
The encoding issues bit me in a few places (especially with paperclip), and I have some hacky initializers running that monkeypatch a few libraries to behave we
by ludicast 16y ago
The encoding issues bit me in a few places (especially with paperclip), and I have some hacky initializers running that monkeypatch a few libraries to behave well enough.
- jcapote 16y agoI'm knee deep in encoding hell right, I'd love to hear more about how you patched it to work with 1.9.2
- edwardog 16y agoYou can fix most encoding problems with doing Encoding.default_internal = Encoding.default_external = "UTF-8" but as JEG states in http://blog.grayproductions.net/articles/ruby_19s_three_default_encodings http://blog.grayproductions.net/articles/ruby_19s_three_defa..., this throws warnings and may still not fix things. Encoding issues rank up there with Array.to_s pains when moving to 1.9
- jcapote 16y agoHa! Glad to know I'm not the only one hitting the Array.to_s surprise!
- wvanbergen 16y agoMy favorite issue in 1.9.2: "." is no longer included on the $LOAD_PATH.