BIÁNG character not rendering in PDF despite correct embedded font

CorrectFontEmbeddedButBiangMissing.pdf (2.8 MB)

CorrectFontsEmbedded.docx (3.7 MB)

We are converting a word document with the BIÁNG character embedded into PDF. However the BIÁNG character does not render correctly in the PDF despite it rendering correctly in the word document and the font appearing to be correctly embedded in the PDF.


The word document and the generated PDF are attached.
We are using the latest versions of Aspose. Any ideas what might be going wrong here?

@mkothe

  • Is the BIÁNG character missing only in specific PDF viewers, or is it consistently missing across all viewers?
  • Have you verified if the character is present in the embedded font subset within the PDF using a font inspection tool?
  • Are there any warnings or logs from Aspose during the DOCX to PDF conversion process?
  • Can you confirm whether the source DOCX uses a TrueType (TTF) or OpenType (OTF) font, and if that font explicitly supports the BIÁNG character?

Thanks for the quick follow up:

Is the BIÁNG character missing only in specific PDF viewers, or is it consistently missing across all viewers?
Consistently missing.

Have you verified if the character is present in the embedded font subset within the PDF using a font inspection tool?
I can’t check for a specific character, but the correct font is embedded (screenshot on ticket)

Are there any warnings or logs from Aspose during the DOCX to PDF conversion process?
No

Can you confirm whether the source DOCX uses a TrueType (TTF) or OpenType (OTF) font, and if that font explicitly supports the BIÁNG character?
*TTF And yes the TTF font supports the BIÁNG character *

I don’t know how to inspect the embedded font subset, but happy to try if someone can give us some pointers.

@mkothe

The user is reporting a specific rendering issue with the BIÁNG character during DOCX to PDF conversion using Aspose, where the character fails to display in the output PDF despite correct font embedding and no conversion errors. The user has provided follow-up details confirming consistent absence across viewers, use of TTF font, and absence of warnings, indicating a technical troubleshooting scenario requiring investigation into font subsetting or character support in Aspose.PDF.

Hi, the only response so far seems to be from an AI - is a human able to look into this?

@mkothe

The scenario looks related to Aspose.Words. We have moved this topic to the respective forum category where you will be assisted accordingly.

@mkothe The problem is not reproducible on my side using the latest 26.1 version of Aspose.Words. Here is the output produced on my side: out.pdf (39.2 KB)

As I can see you are using 25.8 version. Please try using the latest version and let us know if the problem still persists on your side.

@alexey.noskov thanks for this, we tried with version 26.1 and our setup and it didn’t work correctly. This makes me suspect we don’t have the settings configured correctly. Are you able to let me know what the configuration you used was for the conversion to PDF? Maybe a code snippet?

@mkothe I did not made any additional configuration. I converted your document to PDF using the following simple code:

Document doc = new Document(@"C:\Temp\in.docx");
doc.Save(@"C:\Temp\out.pdf");

Also, I tried converting the document without system fonts:

FontSettings.DefaultInstance.SetFontsSources(new FontSourceBase[] {  });
Document doc = new Document(@"C:\Temp\in.docx");
doc.Save(@"C:\Temp\out.pdf");

The result is the same, the document is rendered properly.

Could you please save the document as XPS using Aspose.Words and attach the resulting file here for our reference?

Hi @alexey.noskov , I created a little stripped down app to do what you did and it works just fine. So we are doing something in our more complex implementation that isn’t working - will dig into it more and let you know what we find.

1 Like

Hi @alexey.noskov ,

so it seems the word document supplied is different to the one we are creating in our process. The attached word document, which is much smaller, views fine in word but in a stripped down app does not seem to work at all. The font settings are set to the System Fonts and my system fonts include the SimSun-ExtG Regular which is standard (I didn’t install it specially) , but it doesn’t get embedded in the PDF.

Please see the attached screenshot and the word document

CorrectFontsEmbedded-2.docx (11.7 KB)

@mkothe
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): WORDSNET-29033

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.

1 Like

I also tried copying the font into another folder location and adding that folder as a folderfontsource to the fontsettings fontsourcebase in addition to the system fonts folder and it still didn’t include

@mkothe I managed to reproduce the problem on my side and logged the problem as WORDSNET-29033.

Thanks so much @alexey.noskov

1 Like