we're using send_data and setting the charset=UTF-8 in the header. i'm assuming its correct b/c it looks fine when I force my editor to open the file in UTF-8. The real issue here is getting all editors to open the file as UTF-8 under their default settings (most editors just try to guess the encoding by default). Sounds like a BOM may be what I'm looking for. Just have to figure out how to add one to the file in Ruby. =P
On Nov 6, 10:54 am, "John Bresnik" <[EMAIL PROTECTED]> wrote: > ah ok - but the save text is sending a UTF8 stream ? Also I don't > think BOMs are permitted in data streams by unicode but I might have > that wrong.. > > On 11/6/07, Chris Abad <[EMAIL PROTECTED]> wrote: > > > We have Unicode working properly on the site already. Displays online > > just fine. The database is setup properly, the encoding is setup > > properly, etc. We're just trying to figure out the best way to > > implement this "save text" function. > > > On Nov 6, 1:03 am, "John Bresnik" <[EMAIL PROTECTED]> wrote: > > > It's tricky because everything has to be lined up properly - your > > > mysql tables have to be utf8 [they default to 'latin1'], your reverse > > > proxy has to be speaking utf8 and of course your app does as well.. > > > >http://wiki.rubyonrails.com/rails/pages/HowToUseUnicodeStrings > > > > Setting the encoding in an RTF file is really only a suggestion, i.e. > > > if the underlying encoding is different from what youre saying it is - > > > still won't work.. > > > > best suggestion - use UTF8 - unless you got a user that is still on > > > Windows 3.1 just abt every editor reads UTF8.. > > > > hope that helps. --~--~---------~--~----~------------~-------~--~----~ SD Ruby mailing list sdruby@googlegroups.com http://groups.google.com/group/sdruby -~----------~----~----~----~------~----~------~--~---
