playframework/Play20 — pull request #550 by jroper (2012-11-19 07:31:00+00:00)
Title: [#863] Fixed hashing of templates so that non UTF-8 are hashed consistently

The issue here is when the template contains non UTF-8 characters, for example, 0x96 (one of the "extended ascii" quotes). Previously, Play would read this in as UTF-8, and it would become some other valid UTF-8 character, then converting this back to bytes would yield a different byte array, and so a different hash. The end result was that in dev mode, Play would recompile the template on every single request.

Play only supports UTF-8 files, so the problem is the users, but this ensures that it gracefully handles it, rather than exhibiting the very confusing behaviour of always reloading.