Thanks for the report. Yes, this is changed behaviour (in 4.60) and is a result of some Unicode handling I added. I'm not sure it is a (big) problem. As far as I can tell, the issue only occurs with the non-printable/special characters (ranging from 128 to 160).

I'll put this on the research list for the next update.

Thanks again for the report.

Ruud