Vashia2:TOC gets converted to link

Aspose.Words Product Family
1

Hi,
I am converting these doc files to PDF using the latest Aspose Words.
But the toc entries embedded in the document gets converted to Links in the rendered PDF.
But the office rendered PDF is fine.

CTS-5282.zip (72.6 KB)

2

@AjeshEMC

Thank you for your inquiry. We have reproduced this issue at our end. We have logged this issue WORDSNET-16276 for further investigation and resolution as soon as we have any further update we will inform you here.

We also suggest you to generate the PDF using EmbedFullFonts on a machine that have these fonts available. Please have a look at this sample code and share your feedback. Thank you for your cooperation.

//Load the documents
Document doc = new Document(dataDir + @"Vorlage.docx");

PdfSaveOptions pdfSaveOptions = new PdfSaveOptions();
pdfSaveOptions.SaveFormat = SaveFormat.Pdf;
pdfSaveOptions.EmbedFullFonts = true;

// Save document
doc.Save(dataDir + @"Vorlage_docx_PDF.pdf", pdfSaveOptions);
3

AsposePDF_trueEmbed.zip (744.7 KB)
Hi,
This is the output after using pdfSaveOptions.EmbedFullFonts = true
I dont see any difference in the renditions or fonts used in the renditions, other than the size difference between both the renditions is huge.
The output is still incorrect.
Can you please explain what is the significance of the EmbedFullFonts as true and false.

Regards,
Ankur Vashishtha

4

@AjeshEMC

Thank you for your feedback. We will also consider this scenario while detailed investigation.

EmbedFullFonts Property controls how fonts are embedded into the resulting PDF documents as if set to true then Complete Font File will be embedded into the output PDF and by default it is set to false and Subset Font File will be embedded into output PDF.

We have already logged this issue and attached here. We will update you here as soon as we have further more information. Thank you for your cooperation.

5

Thanks a lot.

6

Hi,
It is Aspose Java issue not .Net. Please correct it accordingly.

Regards,
Ankur Vashishtha

7

@AjeshEMC

Thank you for your feedback.

We have also reproduced this scenario in .NET and also logged this WORDSNET-16292 for JAVA platform.

Please also confirm “Klint for BKW”, “Klint Pro”, “Barcode3_9AL” fonts are Installed on your machine while generating the PDF file?. If yes then please share Font files with us here for further investigation.

Thank you for your cooperation

8

@AjeshEMC,

Please note that your ‘COP1.docx’ document uses the following fonts:

  • Barcode3_9AL
  • Klint Pro

And your ‘Vorlage.docx’ document uses the following font:

  • Klint for BKW

Please ZIP and upload these fonts files here for further testing. Thanks for your cooperation.

9

Hi @awais.hafeez
How do you know the fonts requirements for the following documents?
Neither the aspose rendition nor the office rendition pdf properties suggest the same.

Regards,
Ankur Vashishtha

10

@AjeshEMC,

You can use the following code to receive notification of missing Fonts and Font substitution during rendering to PDF.

Document doc = new Document("D:\\temp\\COP1.docx");
HandleDocumentWarnings callback = new HandleDocumentWarnings();
doc.setWarningCallback(callback);
doc.save("D:\\temp\\awjava-18.1.pdf");

And the code of class implementing the IWarningCallback interface is as follows:

static class HandleDocumentWarnings implements IWarningCallback {
    public void warning(WarningInfo info) {
        if (info.getWarningType() == WarningType.FONT_SUBSTITUTION) {
            System.out.println("Font substitution: " + info.getDescription());
        }
    }
}

Please also refer to the following article:
How to Receive Notification of Missing Fonts and Font Substitution during Rendering

11

Hi @awais.hafeez,
Thanks a lot. I have asked the customer to provide the same. Will reply as soon as the customer replies.

Regards,
Ankur Vashishtha

12

Hi awais,
Sorry for the delay. Please find the fonts attached.
BKW_Schriften.zip (1.4 MB)

Regards,
Ankur Vashishtha

13

@AjeshEMC,

We will inform you via this thread as soon as your issues are resolved.

14

The issues you have found earlier (filed as WORDSNET-16276) have been fixed in this Aspose.Words for .NET 18.3 update and this Aspose.Words for Java 18.3 update.