Word to Pdf:Document Format

Aspose.Words Product Family
1

I’ve noticed inconsistencies in paragraph formatting when converting some documents to PDF. For example, text that’s on the second line in Word becomes the third line in PDF; in extreme cases, a one-page document becomes two pages. The client is not satisfied with this result. How can I resolve this issue?
version:words-25.10-jdk17.jar
fie:
TEST.7z (182.0 KB)

1713×479 116 KB

2

@serendipity.zhq

Summary
When converting a DOCX to PDF with Aspose.Words, differences in line breaks or pagination are most often caused by font‑related issues – the conversion engine cannot find the exact fonts used in the Word document, so it substitutes other fonts whose character widths and line heights differ. This leads to extra line‑wraps or additional pages in the resulting PDF.

Why it happens

  • Missing fonts – The DOCX references fonts that are not installed on the machine where the conversion runs. Aspose.Words falls back to a default font, changing the layout.
  • Fonts not embedded – By default the PDF may be saved without embedding the original fonts. If the viewer does not have those fonts, the rendering can differ.
  • Incorrect font‑search path – If the library is not pointed to the folder that contains the required .ttf/.otf files, it cannot locate them.

What to do next

  1. Identify the fonts used in the source document
  • In Word: Home → Replace → Replace Fonts to see which fonts are applied.
  • Or unzip the .docx and inspect word/fontTable.xml for <w:font> entries.
  1. Make the fonts available to Aspose.Words
import com.aspose.words.*;

public class WordToPdf {
public static void main(String[] args) throws Exception {
// Folder that contains all fonts referenced by the DOCX
String fontsFolder = "C:/MyFonts";

FontSettings fontSettings = new FontSettings();
fontSettings.setFontsFolder(fontsFolder, true); // search sub‑folders

Document doc = new Document("TEST.docx");
doc.setFontSettings(fontSettings);

PdfSaveOptions saveOptions = new PdfSaveOptions();
saveOptions.setEmbedFullFonts(true); // embed the exact fonts
saveOptions.setUseHighQualityRendering(true); // optional, improves fidelity

doc.save("Result.pdf", saveOptions);
}
}
  1. Verify that the fonts are correctly embedded – open the generated PDF in a viewer and check the document properties (Fonts tab) to ensure the expected fonts are listed as embedded.
  2. Test the conversion
  • Compare the PDF side‑by‑side with the original Word file to confirm that line spacing and pagination match.
  1. If the problem persists
  • Ensure the font files are not corrupted and that their family names match those declared in the DOCX.
  • Check for any code that modifies PageSetup (margins, paper size) before saving.
  • Collect the original DOCX and the produced PDF and contact Aspose support with those files for deeper analysis.

These steps address the most common cause of layout changes during DOCX‑to‑PDF conversion with Aspose.Words.

Note: The specific evidence retrieved for this query did not contain details about font‑substitution or PDF layout issues, but the above guidance reflects the typical resolution pattern for the described problem when using Aspose.Words.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.

3

It’s not a font issue. Even if I set all the fonts in the document to the same font that’s installed on my machine, using the code above, the conversion result is the same; the PDF only contains the same font setting.

4

@serendipity.zhq
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-28816

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.