2009/4/13 buddycat <[email protected]>

>
> hector,
>
> further update:
>
> i was able to set both my internal and external encoding thanks to
> hongli lai at phusion passenger. he helped me with a wrapper for my
> local ruby that uses the encoding option. not suggesting that this is
> his preferred method though, but you don't seem to be able to pass
> ruby options any other way that i'm aware of in passenger's apache
> config.
>
> /usr/local/ruby1.9/bin/ruby_wrapper:
> #!/bin/bash
> exec /usr/local/ruby1.9/bin/ruby -E utf-8:utf-8 "$@"
>
> then in apache2.conf:
> PassengerRuby /usr/local/ruby1.9/bin/ruby_wrapper
>
> restart apache.
>
> in a controller:
> raise "#{Encoding.default_internal} #{Encoding.default_internal}"
>
> results in:
> utf-8 utf-8
>
> so all is good. for my app anyway. irb and script/console is a pain.
>
> unfortunately, after all this, my asp pages still get ascii encoded
> when brought in by net::http (after adding all the asp settings i can
> to convince it to use utf). also, more unfortunately, your assertion
> that if i have the default encodings set right (particularly
> default_internal which i do now), that it will silently and fautlessly
> convert my ascii page without error. no joy. got same utf encoding
> error that i started with.
>
> so...guess i am back to doing explicit encoding like you suggested or
> going back to iconv.
>
> all in all i have to say that ruby1.9 and rails2.3 and encoding and
> irb and compiling your own ruby and... are still very rough.
>
> ...gg
>

Do you have a test case that I can reproduce the issue that you're seeing?

Thanks,

-Conrad

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" 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/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to