search for: intertwingly

...gem to transform an array/hash that contains serialized ruby. Builder''s to_xs method seems to mangle serialized ruby though. I can get around this by encoding/decoding with base 64, but that doesn''t seem like a good path to follow. Builder is using this code for escaping: http://intertwingly.net/stories/2005/09/28/xchar.rb Any ideas on how to modify that, so serialized ruby will be escaped properly? Thanks, Matt

Can be done in a one step process or do I have to upgrade to 2.2 then 2.3? Thanks for the help. -- Posted via http://www.ruby-forum.com/.

...olumns in a database are simply plain text. That also tends to be the ''safe'' choice in most cases; treating markup as plain text will expose the markup. This , while suboptimal, at least is obvious. In the reverse case, what you have is silent data loss [6]. [6] http://www.intertwingly.net/blog/2004/05/28/detente If you want to put plain text in an RSS 1.0 or RSS 2.0 <description>, and you are using Builder 2.0 (you *are* using Builder 2.0, aren''t you?), then you need to add a .to_xs to escape the string. If you want to put plain text into an Atom <summary&...

I''m having trouble getting the specs to run for a plugin where I want to fix a bug. (I''ve actually already found and fixed the bug, but I don''t want to submit a fix without a test!) When I started the specs weren''t running, but it may be that I''m using Rails 2.3.3 and the plugin has been tested on 2.1 and earlier. I went through writing a spec for a