This is what I hate about Rails:
- New feature added to Rails 2.3.0RC1 allowing simple localisation by template naming convention – ie, if locale is set to :ja and an index.ja.html.erb file is present, that gets rendered in preference to any other index files. Cool!
- New feature doesn’t work properly and exhibits an insidious bug where it manages to set a wrong Content-type in the HTTP headers, causing all sorts of nasty, hard-to-troubleshoot problems
- Problem is reported
- Rails Core replies “wontfix”
The “fix” Josh suggests, needless to say, doesn’t fix anything.
That is utter bullshit. A major new feature of Rails 2.3.0, as reported in Ruby Inside and the Riding Rails blog itself, doesn’t work. Has no-one else tried it? Has anyone used this at all? Are me and the other commenters on this ticket the only 3 people in the world who ever tried to use this feature?
There is no fucking excuse in the world for Rails to silently be sending a wrong Content-Type, no matter what.
Tags: rails