We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Custom fonts not working word to pdf convertion

Hi,

We are evaluating the ASPOSE Word module to use for our client. As per requirement, we need to convert word document (using Jameel Noori Nastaleeq font) to pdf. But due to some reasons when we tried to use the custom font system is generating the empty pdf file. We have reviewed the forum and found two solutions but those not work. Can you please guide how can we fix this issue so that we can complete our POC and share recommendations with our client. below is the sample code using in asp.net web app.

string dir = “D:\reports\”;
string inputfile = dir + “report.doc”;
string outputfile = dir + “output.pdf”;
///aspose convertor
var document = new Aspose.Words.Document(dir + “report.doc”);
PdfSaveOptions options = new PdfSaveOptions();
options.EmbedFullFonts = true;

        FontSettings fontSettings = new FontSettings();
        fontSettings.SetFontsFolder(@"D:\\reports\\", false);
        //// Set font settings
        document.FontSettings = fontSettings;
      
        document.Save(outputfile);

Thanks

@usman123

Thanks for your inquiry. Please ZIP and attach the following resources here for testing.

  • Input Word document.
  • Font file you are using in the document.
  • Ms Word generated PDF file showing the desired output.

We will then investigate the issue on our end and provide you more information.

P.S. If your file size is big then you may upload the ZIP file to Dropbox or any other file hosting service and share the download link here for testing.

@mannanfazil
Below is your required info.

files.zip (9.3 MB)

@usman123

Thanks for your inquiry. 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-17811 . You will be notified via this forum thread once this issue is resolved.

We apologize for your inconvenience.

thank you @mannanfazil for your confirmation and looking forward your response.

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