On Sat, Aug 2, 2014 at 9:33 PM, Michael Fischer <[email protected]> wrote: > On Sat, Aug 2, 2014 at 12:07 PM, Gary Grossman <[email protected]> > wrote: >> This might be one of those instances where it would be helpful for >> implementation to lead specification. Unicorn is one of the leading >> servers of its genre, if not the leader. If you supported a switch >> that made the encoding regime more sane, I think other popular servers >> like Thin and Passenger would swiftly follow and it might re-energize >> the discussion about getting encodings into the Rack spec once and >> for all, and give a base for experimentation and iteration for >> getting the encodings in the spec right. >> > > I agree with Gary here. It's often too easy to decide to preserve the > status quo because things work well enough -- and then, eventually, time > catches up with you and it no longer does.
Hi guys. Phusion Passenger author here. I would very much support standardization of encoding issues. Every now and then, a user submits a bug report on Phusion Passenger, mentioning an encoding problem. The user would say that the problem occurs on Phusion Passenger but not on Unicorn/Thin/etc. The Rack spec doesn't say anything about encodings so strictly speaking it's not "our fault", but it's still hard to tell users that it's "their fault" or "their framework's fault" based on this alone. It's also not a helpful answer: users often have no idea what to do about the issue. At this point, I don't really care what the standard is, as long as it's a sane standard that everybody can follow. In my opinion, following Encoding.default_external is not helpful. Most users have absolutely no idea how to configure Encoding.default_external, or even know that it exists. I've also never, ever seen anybody who does *not* want default_external to be UTF-8. If it's not set to UTF-8, then it's always by accident (e.g. the user not knowing that it depends on LC_CTYPE, that LC_CTYPE is set differently in the shell than from an init script, or even what LC_CTYPE is). -- Phusion | Web Application deployment, scaling, and monitoring solutions Web: http://www.phusion.nl/ E-mail: [email protected] Chamber of commerce no: 08173483 (The Netherlands)
