.......
Anyway, by default Rails will set the encoding to UTF8 (just put
Rails.logger.debug "Kcode: #{$KCODE}" to confirm this is the case for
you). To see what encoding *is* working properly, just check the
$KCODE global from irb. Then set that accordingly in your
environment.rb and restart your app.
On May 3, 4:46 pm, 7stud -- <[email protected]> wrote:
> resh Mix wrote:
>
> > I think, it is same, because I have only ruby 1.8.7 installed.
>
> > $ ruby -v
> > ruby 1.8.7 (2008-08-11 patchlevel 72) [x86_64-linux]
>
> Ok. ruby 1.8.* doesn't understand multi-byte/unicode characters, like
> russian characters. ruby thinks that every character is an ascii
> character, where one byte equals one character. However, you aren't
> asking a ruby method to do anything with your string--you are calling an
> aspell method. Is there any reason to believe that aspell can recognize
> a character that is made up of several bytes?
>
> As for irb, personally I never use the command line interactive mode in
> any language because after a few times spending hours trying to figure
> out why the results in interactive mode were different than in a
> program, I determined that I would never waste time doing that again.
> The only output that matters is your program's output. Forget about
> what irb says and instead write a small example program when testing
> things out.
>
> If you write a small program, with the same content as irb, do you get
> true or false for your aspell calculations?
>
> --
> Posted viahttp://www.ruby-forum.com/.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
