Rails Ruby on Rails

Comments and changes to this ticket

• 

  Santiago Pastorino February 2nd, 2011 @ 04:59 PM

  • State changed from “new” to “open”
  • Tag changed from “3.0, activesupport” to “30, activesupport”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:59 PM

  • State changed from “open” to “stale”

• You flagged this item as spam.
  

  Nick Wilson February 7th, 2011 @ 08:16 AM

  • State changed from “stale” to “open”

  [state:open]

  This is still a known issue with ruby 1.9.2 and Rails/ActiveSupport 3.0.3

  Ruby 1.9 in unicode mode will attempt to interpret the regular expression as unicode. To avoid this you need to pass the regular expression option "n" for "no encoding":

  = /[\x00-\x20%\x7F-\xFF]/

  Becomes:
  = /[\x00-\x20%\x7F-\xFF]/n

  Now we have our raw 8-bit encoding (the only thing Ruby 1.8 speaks) as intended:
  ruby-1.9.2-p136 :001 > ESCAPE_KEY_CHARS = /[\x00-\x20%\x7F-\xFF]/n.encoding
  => # <Encoding:ASCII-8BIT>