Any text that goes through an HTML filter (such as "Love & Money") loses the non-ASCII character (in this case "&" I'm assuming) in the output.

It would be great if Signwriter could parse for common HTML escape sequences and turn them back into text.

Comments

aacraig’s picture

aacraig CreditAttribution: aacraig commented
Category: feature » bug

On further investigation, I see that HTML entities are being parsed, so I'm not sure what's happening.

I have a font which does contain the "&" character, as it comes out in OpenOffice or GIMP in this font.

However, when the text is rendered in Signwriter, it doesn't appear. Adding "&" to the allowed non-ASCII list has no effect.

I can't attach the font as ttf files aren't allowed. However, it is the Bobel font which I found here: http://www.deviantart.com/download/50559674/Bobel_font_by_pitters.ttf