Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Apparently 0.6.2 has a call to force_encoding, which is not around in 1.8.7.
- Loading branch information
Apparently 0.6.2 has a call to force_encoding, which is not around in 1.8.7.
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💩, their master should be already handling it, but we may need another release fixing the problem.
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/me nods
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like
i18n
0.6.4 was released on the same day as this patch, which fixed the problem on 1.8.7.The same day, 641a27d was applied to the 3-2-stable branch. How come this change didn’t make it into the 3.2.13 release?
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The release branch has it in it: https://github.com/rails/rails/commits/3-2-13
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👎
I coded a project using Rails 3.2.11 with I18n 0.6.4, now I can't upgrade to Rails 3.2.13 because it is forcing I18n 0.6.1 wich expects an array of translations, but I18n 0.6.4 save just a string. All my project has just the first char at translated strings.
197b9f4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dlibanori use 3-2-stable