Typophile

MS Word will not render with unicode 2665 included

BebopKid

This is really weird. I been struggling with this for a day and finally figured out my problem is centered on unicode 2665.

If I include unicode 2665 (heart) in my font, MS Word (or PowerPoint) will not render the font and insteads renders every glyph in Times New Roman. However, if I simply remove 2665 from the font MS Word renders my font perfectly.

The same font renders perfectly in MS Publisher, InkScape, and Gimp.

I have tried searching but can't find anyone who has had my particular issue with an unicode character.

I'm running Windows 7 64bit, Office 2010, FontForge 13:48 GMT 22-Feb-2011. Which is the latest stable FontForge version for 64-bit windows.

I have no idea what information from the font is needed to figure this out, so I'm just including the font sfd and ttf. (had to rename them to txt to upload)

If anyone can help, I'd be very greatful.

AttachmentSize
BebopKidManga.sfd_.txt285.56 KB
BebopKidManga.ttf_.txt72.36 KB
BebopKid

Accidentally posted the wrong sfd without the 2665 in it and don't know how to edit my post on this forum

Jason Campbell

this might be a dumb question, but is there anything particular about the u+2665 glyph, aside from it's unicode value? As in, is it the tallest or widest glyph?

Just fishing, but it's worth a thought.

Jason C

BebopKid

No, I have tried it with different glyph including a blank glyph.

It seems to have nothing to do with the glyph itself only the unicode value 2665. It also doesn't matter what the name of the glyph is. I can have it named "heart" and it works fine if it's another unicode number. But of course, I'd like the unicode map to be correct.

Captured from web.archive.org on 9 Aug 2014. view this capture