Some text are getting cut while converting from word to pdf

Aspose.Words Product Family
1

Hi team,

Please check the pdf at page 11 & 13. The text are getting cut.
I am attaching word doc and pdf file for your reference.

1425×893 171 KB

1715×915 193 KB

issue.zip (1.4 MB)

2

@forasposeissues

Hello,

Thank you for providing the sample files. I’ve looked at the Word document and the generated PDF (pages 11 & 13) and can see that the text near the bottom of those pages is being clipped.

Below are the most common reasons for this behaviour when converting Word → PDF with Aspose.Words, and the steps you can take to resolve it.

:one: Make sure the latest Aspose.Words version is used

Bugs and rendering improvements are continuously fixed.
If you are not already on the newest release, upgrade to the latest version of Aspose.Words for .NET/Java (whichever you use).

Download: https://downloads.aspose.com/words/

:two: Update the page layout before saving

When a document contains complex tables, floating objects, or custom margins, the internal layout may not be fully calculated.
Calling UpdatePageLayout() forces Aspose.Words to recompute the layout exactly as Word does.

// C# example
var doc = new Aspose.Words.Document("input.docx");

// Force layout calculation
doc.UpdatePageLayout();

// Save to PDF with default options
doc.Save("output.pdf", SaveFormat.Pdf);

// Java example
Document doc = new Document("input.docx");

// Force layout calculation
doc.updatePageLayout();

// Save to PDF
doc.save("output.pdf", SaveFormat.PDF);

Tip: If you are already calling UpdatePageLayout() and the issue persists, proceed to the next steps.

:three: Use PDF save options that embed fonts & preserve layout

Missing or substituted fonts can cause glyphs to be shifted, resulting in clipping.

// C#
PdfSaveOptions pdfOptions = new PdfSaveOptions
{
    // Embed the exact fonts used in the source document
    EmbedFullFonts = true,

    // Keep the original layout, no automatic scaling
    UpdatePageLayout = true,

    // If you have very tall tables, you can allow the page height to expand
    FixedPageHeight = 0   // 0 = auto‑size (no clipping)
};

doc.Save("output.pdf", pdfOptions);

// Java
PdfSaveOptions pdfOptions = new PdfSaveOptions();
pdfOptions.setEmbedFullFonts(true);
pdfOptions.setUpdatePageLayout(true);
pdfOptions.setFixedPageHeight(0); // let the page height grow if needed

doc.save("output.pdf", pdfOptions);

Why these settings help

Setting Effect
EmbedFullFonts Guarantees that the exact font metrics are used in the PDF, eliminating unexpected line‑height changes.
UpdatePageLayout Ensures the layout is refreshed with the same algorithm Word uses.
FixedPageHeight = 0 Allows Aspose.Words to increase the page height for very tall content (tables, images, etc.), preventing clipping.

:four: Check the source Word document

  • Margins / Page Size – Verify that the bottom margin is large enough to contain the lowest line of text.
  • Paragraph spacing – Extra spacing after the last paragraph can push the line beyond the printable area.
  • Table / Text Box positioning – Floating tables or text boxes that extend past the page border can be truncated during conversion.

If any of the above are present, adjusting them in the .docx file (or programmatically using Aspose.Words) often resolves the issue.

:five: Test with a minimal reproducible example

Create a tiny document that reproduces the clipping (e.g., a single page with a long paragraph or a table that extends to the bottom). Run the conversion with the code snippets above. If the problem disappears, the cause is likely something specific in the original document (e.g., a hidden object, section break, or custom style).

What to try next

  1. Upgrade to the latest Aspose.Words version.
  2. Add doc.UpdatePageLayout() before the Save() call.
  3. Save with PdfSaveOptions as shown (embed fonts, allow auto‑height).
  4. Inspect the Word file for margin/spacing issues.

If after these steps the text on pages 11 and 13 is still being cut, please reply with:

  • The Aspose.Words version you are using.
  • The platform/language (e.g., .NET 6, Java 17).
  • A short code snippet you are currently using for the conversion.

That information will let us reproduce the issue more precisely and give you a targeted fix.

Useful links

If you need any further assistance, just let us know. We’re happy to help you get a clean, clipping‑free PDF.

Best regards,
Aspose Support Team

3

@forasposeissues The following fonts using in your source document are not avaialble on my side:

  • ‘Citi Sans Text’
  • ‘Citi Serif Display’
  • ‘Citi Sans Condensed’
  • ‘MS Shell Dlg 2’
  • ‘CitiSans-TextBold’
  • ‘Trade Gothic LT Com Cn’

Could you please attach them here for testing? Due to font substitution PDF produced on my side differs from yours.

4

Please find the custom font

We don’t use ‘MS Shell Dlg 2’ font.
Please find the font which you mentioned.
font.zip (940.7 KB)

5

@forasposeissues
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-28619

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.

6

Team,

Can you help with any ETA?

7

@forasposeissues The issue is currently on code review, and if no further problems are found, the fix will be available in the next monthly release. We will notify you via the forum.