It appears that when an HTML document containing multiple SVG files which in turn contain embedded subsets of the same font is converted, the result is a PDF with non-unique embedded font names.
If you examine the PDF that's produced from the attached examples, you should see that the name "EncodeSansSC-Bold" appears twice, in two distinct embedded subsets, when listing the document's fonts.
This in turn causes the PDF to fail Adobe preflight checks because of the non-unique embedded font names.
An ideal resolution would be for Prince to identify when it's looking at multiple distinct subsets of the same embedded font in this scenario, and collapse them into a single embedded font in the resulting document, but failing that, as far as I'm aware there's no rule against having multiple, distinct embedded subsets of the same font under different names – it's really just the overlapping names in the resulting document that's the issue.
If you examine the PDF that's produced from the attached examples, you should see that the name "EncodeSansSC-Bold" appears twice, in two distinct embedded subsets, when listing the document's fonts.
This in turn causes the PDF to fail Adobe preflight checks because of the non-unique embedded font names.
An ideal resolution would be for Prince to identify when it's looking at multiple distinct subsets of the same embedded font in this scenario, and collapse them into a single embedded font in the resulting document, but failing that, as far as I'm aware there's no rule against having multiple, distinct embedded subsets of the same font under different names – it's really just the overlapping names in the resulting document that's the issue.
Edited by David J Prokopetz