Bjoern wrote: > Hi, > > my apologies for that very basic question. I have heard from many > people that unicode worked well for them, but I have been unable to > find any definite information on how it works (with Rails).
Make sure the DB encoding and the appropriate header in the generated HTML are both set to UTF-8 (or UTF-16, I suppose, but I've never tried that). > I gather > that as long as I don't do anything but pass the Strings along, it > will probably work (that's what people said anyway). Yes. > And there is > ActiveSupport::Multibyte > > But what about external libraries? For example I want to access some > web services and parse JSON data. Will the JSON parser work correctly > if there are unicode Strings in the result? I don't see why not, but you could always test and see. [...] > I would prefer to use Ruby 1.9.1 to avoid the issue completely, but I > still have problems getting proper documentation for the STDLIB. Try http://www.ruby-doc.org . Ruby 1.9 is still problematic in terms of compatibility -- I understand that Rails works well with it, but many gems and plugins do not. > > Bj�rn Best, -- Marnen Laibow-Koser http://www.marnen.org mar...@marnen.org -- Posted via http://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 rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
