Describe the bug & what the expected behavior should be:
When exporting to SVG, certain characters are not escaped properly in <glyph> elements' unicode properties, leading to parse errors when trying to open the exported SVG in any software. For example, a " glyph will be exported as <glyph glyph-name="Quotation_mark" unicode=""" />, or a < glyph as <glyph glyph-name="Less-than_sign" unicode="<" />; neither are valid SVG and will fail to open in any SVG editor.
The SVG export routine should escape sensitive characters that are part of the SVG syntax; for instance, " should be escaped as ", and < as <.
Steps to reproduce the bug:
Export any font that provide glyphs for protected SVG characters as SVG.
Open the resulting SVG in any text editor; the protected characters are not escaped.
Describe the bug & what the expected behavior should be: When exporting to SVG, certain characters are not escaped properly in
<glyph>
elements'unicode
properties, leading to parse errors when trying to open the exported SVG in any software. For example, a"
glyph will be exported as<glyph glyph-name="Quotation_mark" unicode=""" />
, or a<
glyph as<glyph glyph-name="Less-than_sign" unicode="<" />
; neither are valid SVG and will fail to open in any SVG editor.The SVG export routine should escape sensitive characters that are part of the SVG syntax; for instance,
"
should be escaped as"
, and<
as<
.Steps to reproduce the bug: