Wrong Content-Type when using localized templates

Strongly disagree with above "wontfix". The current behaviour is to half-work, with an incorrect content-type, causing insidious and confusing hard-to-troubleshoot errors. I spent a couple of hours tracking this nasty bug down before finally arriving here.

The "fix" is undocumented and obscure. The localised templates otherwise work, just silently include a completely wrong content-type. What excuse is there for that kind of hideous bug?

This ticket needs to be re-opened immediately.

Hmm, we had this issue too, but while I was investigating the issue it was fixed, for at least our case, in edge by another commit.

@hkstar: I would suggest you write some failing unit tests for Template#split, which is most probably where the problem lies.

Strongly disagree with "wontfix", too!

I also disagree with the "wontfix"- I've just run into this bug, and I most definitely have my locale loaded and set correctly. Other parts of the Rails I18n system are working fine, strings are being loaded from my locale file on other templates, etc... but anything that tries to load a localized view displays the above-described behavior. The correct (i.e., localized) view loads, is rendered, and is then sent down to the browser with a content-type of "#{locale}.html".

This also happens if you use a template filename such as edit.default.html.erb, the content-type in this case is set to edit.html, not text/html.

Changing to edit_default.html.erb or manually setting the correct content-type header prevents this problem but imposes a naming scheme on your templates or additional work.

Rails 2.3.5

It works for me with a more recent 2-3-stable but my workaround is to actually create empty locale files like this.

ja:
  activerecord: