I was looking into this because I notice it on certain browsers (Edge on Windows, for instance), but not others. I def think it's a UTF error of sorts, but I'm not sure what is wrong.
I can try upgrading the site to a beta of their "new release" 2.1, but I'm a bit worried to do that just for this. I'll keep looking into it to see if we can come up with a solution.