This admittedly bizarre behaviour is caused by an obscure issue in one of the Unicode APIs.

I will add a fix/workaround for this in beta 2.

Thanks for the report!

Ruud