User blog comment:Rappy 4187/Technical Update: January 11, 2016/@comment-5973717-20160111235238/@comment-126761-20160112115745

I just checked, and we do have a technical ticket open about this. However, I am not sure that this is something we can fix - I think the issue may be on Chrome's side. (The characters display normally in Firefox, and we have relatively little control over how fonts render characters.)