Given a pptx as input and specifying defaultRegularFont
makes no difference to the svg output for fonts that are not on the system – e.g. “MyCustomFont” nor for fonts that would be on the system – e.g. “Arial”.
Likewise, specifying fontSubstRules
makes no difference whatsoever for the svg output.
Your solution acts as this functionality has simply not been implemented – can you verify this is supposed to work for svg, i.e. change the font-family
for svg <text>
nodes.
@lumentric,
Thank you for contacting free support. We are sorry that you encountered this problem. Please share the following additional files and information:
- sample presentation file
- code example to reproduce the problem you described
- output SVG file
- Node.js version you used
- Aspose.Slides Cloud SDK for Node.js version you used
Before I waste any more time on this, can you confirm that the defaultRegularFont
and fontSubstRules
are supposed to work, as I wrote above:
can you verify this is supposed to work for svg, i.e. change the font-family for svg nodes.
@lumentric,
I will run some tests and get back to you soon. Thank you for your patience.
@lumentric,
I’ve reproduced the problem with the defaultRegularFont
and fontSubstRules
options when converting PowerPoint presentations to SVG images with Aspose.Slides Cloud SDK for Node.js. We apologize for any inconvenience caused.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): SLIDESCLOUD-2005
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@andrey.potapov Can you give any more details as to the status of this issue?
The handling of font-family in pptx to svg is completely erratic. I could open more issues describing this but as SLIDESCLOUD-2005 has Status : Blocked I’m not sure it would be of any use.
@lumentric,
Aspose.Slides Cloud API is based on the on-premise Aspose.Slides libraries. We found that the same problem exists in these libraries as well. Once we resolve these issues in those libraries, we’ll address them in the Aspose.Slides Cloud SDKs.