We are generating an SVG from a PDF in one of our use cases - the conversion works fine. However, an issue has come up when rendering the SVG file in Internet explorer (Chrome for instance, works fine). Inside the SVG file are embedded images and fonts - looks to be base64 encoded, etc. When rendering in IE, i get a console error “font-face failed OpenType embedding permission check. Permission must be Installable” - this is a security message suggesting that the fonts used may be proprietary and there could be legal issues, etc and is ONLY an apparent issue in Internet explorer. Alternatively, if we use the approach of PDF -> HTML we instead get images generated along with say a .woff file and the embedded style sheets use a relative path to these assets which seems to work fine.
My question is - can we when generating the svg, provide the same options for svg to generate these assets separately as the PDF -> HTML conversion does. What other options are we missing if any to bypass this issue?