I think this is a bug in the way we handle unicode. Haven't had a chance to track it down though.
Screencast_09-08-2018_05_16_10_PM