Smallish update, I'm doing some work on RFC-compliant header and parameter handling in my private fork at the moment. It will only work well on Ruby VMs with 1.9-compliant encoding handling, but should lead to a clean transition from the outside (ASCII-like byte soup) world to a UTF-8 environment.
It currently passes the additional multipart specs, and a bunch of others that aren't yet integrated into dispatch. I'll see how that works out and merge it and Pavel's changes into the active_support branch (and thus into main development) if it doesn't break more than the AS stuff already does ;-) This will eventually mean that merb is becoming incompatible or at least rough to use on <1.9 VMs, but IMO proper charset support is too good a thing to pass. -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=en.
