I can't see this documented anywhere, other than as a passing comment in the bug tracker, so I figured I'd mention it here.
Last week I raised a ticket "<cfprocessingdirective> not implemented in CFScript", which observed that the generic CFScript equivalent of
<cfprocessingdirective>(which should be
cfprocessingdirective()) had not been implemented.
It has indeed not been implemented, but not due to any oversight, but because of this:
So - to be clear - we no longer need to explicitly tell the ColdFusion compiler what the character encoding of a source code file is... it'll work it out for itself. Like how other text-processing applications such as notepad.exe have been able to do for years.
So... a bit late to the party, but ColdFusion eventually got there.
I've given this a superficial test, and it seems to work, too. Cool.
And that's all.