Inserted SVG exporting to docx/pdf: Incorrect Textalign / Font-Style

Aspose.Words Product Family
1

Hello

I have 3 issues with an Inserted svg Image, (tested with output to docx/pdf Aspose 19.3):

  1. Text alignement is incorrect when using text.tspan in combination with text-anchor (File: font_placing.svg)

  2. Font embedded in svg file is not used, even though fully contained as base64 string
    @font-face {
    font-family: “Pacifico-Embedded”;
    src: url("data:application/font-ttf;charset=utf-8;base64,AEAAAARAQAABAAQR0RFRvQ09yUAAn+0AAACZkdQT1MOi…

  3. Font style not correct, even though truetype font-folder is explicitly declared (.SetFontsSources).

Can you please help me to find a workaround or to do a fix.
Thank you, Regards Stefan

Samplefiles_Aspose1903.zip (530.3 KB)
SampleProject_Aspose1903.zip (587.1 KB)

2

@bmpi

We have logged this problem in our issue tracking system as WORDSNET-18270. You will be notified via this forum thread once this issue is resolved.

We are working over other issues and will get back to you soon.

3

@bmpi

Regarding second and third issue, we are unable to reproduce these issues. Could you please share all fonts of Pacifico that are installed on your system? We will then investigate the issue and provide you more information on it.

4

The Fonts are included in Samplefiles_Aspose1903.zip
Fonts\Pacifico-Regular.ttf.

For Case 2) it is embedded as well as base64 encoded string in font_style.svg.

5

@bmpi

We have tested the scenario and have managed to reproduce the same issue at our side. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-18292. You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

6

The issues you have found earlier (filed as WORDSNET-18270) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by mudassir.raza

7

Still pending Issue: Fontstyle is not correct when rendering word (pdf is ok), even explicitly declared, but not installed on the system. Is there a workaround (except installing the font, which is in our case not applicable)? We just upgraded our license to java expecting a solution.

8

@bmpi

The issue WORDSNET-18292 has not resolved yet. It related to missing feature WORDSNET-18292 - Support of CSS3 @font-face Rule. We will inform you via this forum thread once this issue is resolved.

We apologize for your inconvenience.