Vote #71062
完了Ruby 1.9: [v1.3.0] Error: incompatible character encodings for it translation on Calendar page
0%
説明
After updating to 1.3.0 I continue to get the following error when I access the calendar page (it works if I change language to english):
ActionView::TemplateError (incompatible character encodings: UTF-8 and ASCII-8BIT) on line #13 of app/views/calendars/show.html.erb: 10: 11: 12:13: <%= link_to_previous_month(@year, @month) %> | <%= link_to_next_month(@year, @month) %> 14:
15: 16:
journals
Which version of Ruby (see [[SubmittingBugs]])?
--------------------------------------------------------------------------------
Sorry, my fault.
<pre>
About your application's environment
Ruby version 1.9.2 (i486-linux)
RubyGems version 1.3.7
Rack version 1.1.2
Rails version 2.3.14
Active Record version 2.3.14
Active Resource version 2.3.14
Action Mailer version 2.3.14
Active Support version 2.3.14
Edge Rails revision unknown
Application root /srv/www/applications/redmine
Environment production
Database adapter postgresql
Database schema version 20110902000000
About your Redmine plugins
Bulk Time Entry 0.5.0
Mylyn Connector plugin 2.7.5.stable
Redmine Checkout plugin 0.5
Redmine Time Tracker plugin 0.4
Timesheet Plugin 0.6.0
</pre>
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
I was able to reproduce. This should be fixed in r8210.
--------------------------------------------------------------------------------
I am having the same issue in WIKI pages, if the wiki link is constructed by UTF-8 characters, such as Chinese, the linked wiki page will result in error 500, and check the error log it has the incompatible issue on translation. For those pages with links in LATIN, they worked fine, even the contents are with UTF chars.
--------------------------------------------------------------------------------
Merged.
Leon, please open a separate issue if your problem still persists.
--------------------------------------------------------------------------------