Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Most Significant Changes
In Aspose.PDF 26.10, we have added:
Searchable PDF creation through OCR — Document.ConvertToSearchablePdf adds an OCR text layer to PDF documents containing images. Use OcrSearchablePdfOptions to select a recognition language and control image flattening. By default, recognition uses English, and image flattening is disabled. This feature requires the optional Aspose.OCR dependency (PDFNET-62414).
Literal special symbol support — The new Page.ProcessSpecialSymbols property controls the processing of special placeholders such as $p and $P. It is enabled by default; set it to false to preserve these sequences as literal text (PDFNET-62527).
Improved conversion performance and reliability — PDF to HTML conversion is faster on .NET 8. Additional fixes improve HTML to PDF, PDF to HTML, PDF/A, PDF to TIFF, PDF to DOCX, PDF to PPTX, and PDF to SVG conversion workflows (PDFNET-61233, PDFNET-43664, PDFNET-62621, PDFNET-62762, PDFNET-59148, PDFNET-62176).
The following example adds a searchable OCR text layer to an image-based PDF document:
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static void CreateSearchablePdf()
{
// The path to the documents directory
var dataDir = RunExamples.GetDataDir_AsposePdf();
// Open scanned PDF document
using (var document = new Aspose.Pdf.Document(dataDir + "scanned.pdf"))
{
// Configure OCR recognition
var options = new Aspose.Pdf.Ocr.OcrSearchablePdfOptions
{
Language = Aspose.Pdf.Ocr.OcrLanguage.English,
FlattenImages = false
};
// Add a searchable OCR text layer and save the document
document.ConvertToSearchablePdf(options);
document.Save(dataDir + "searchable.pdf");
}
}
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.10 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.9, we have added:
Editable underline and strikeout formatting in PDF to PPTX conversion - The new PptxSaveOptions.RecognizeUnderlineAndStrikeout property recognizes underline and strikeout lines as text formatting. It is enabled by default; set it to false to preserve these lines as graphics (PDFNET-59027).
Resolved names for embedded files - Use FileSpecification.GetFileName to retrieve an attachment name from its Unicode name, regular name, or collection key. You can provide a fallback name when an attachment has no usable name (PDFNET-62441).
Improved PDF conversion stability - Resolved PDF/A, PDF to SVG, PDF to HTML, PDF to DOCX, PDF to TIFF, and PDF to JPEG conversion issues, including text fidelity, compliance, rendering, and performance (PDFNET-62653, PDFNET-62684, PDFNET-62175, PDFNET-62182, PDFNET-62194, PDFNET-62195, PDFNET-43425, PDFNET-43426).
The following example converts a PDF document to PPTX while preserving underline and strikeout as editable text formatting:
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static void ConvertPdfToPptxWithUnderlineRecognition()
{
// The path to the documents directory
var dataDir = RunExamples.GetDataDir_AsposePdf();
// Open PDF document
using (var document = new Aspose.Pdf.Document(dataDir + "input.pdf"))
{
// Preserve underline and strikeout as editable text formatting
var options = new Aspose.Pdf.PptxSaveOptions
{
RecognizeUnderlineAndStrikeout = true
};
// Save the file in PPTX format
document.Save(dataDir + "output.pptx", options);
}
}
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.9 Release Notes page.
Most Significant Changes
Aspose.PDF 26.8 focuses on PDF/A compliance, document conversion stability, and resource handling:
Improved PDF/A conversion and validation - Fixed PDF/A-1b, PDF/A-2b, PDF/A-3b, and PDF/A-4 conversion scenarios, including validation in evaluation mode and preservation of ZUGFeRD XMP metadata (PDFNET-49493, PDFNET-58478, PDFNET-62385, PDFNET-62386, PDFNET-62497, PDFNET-62499).
More reliable document conversion - Resolved issues in EPUB to PDF, PDF to DOC, PDF to JPEG, PDF to PNG, PDF to SVG, PDF to TIFF, and PDF to HTML conversion workflows (PDFNET-42206, PDFNET-42215, PDFNET-42217, PDFNET-42225, PDFNET-42232, PDFNET-42249, PDFNET-42254, PDFNET-58570, PDFNET-58620, PDFNET-62178, PDFNET-62433, PDFNET-62459).
Improved processing of PDF content - Fixed comparison with ComparisonMode.IgnoreSpaces, updating text fragments found by regular expressions, extracting paragraphs with consistent spacing, and traversing malformed page trees without excessive memory consumption (PDFNET-62419, PDFNET-62434, PDFNET-62495, PDFNET-62365).
Detailed information about the changes can be found on the Aspose.PDF 26.8 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.7, we have added:
Side-by-side comparison results - SideBySidePdfComparer.Compare now returns SideBySideDocsComparisonResult for documents and SideBySidePagesComparisonResult for pages. Use HasChanges to determine whether differences were found, then inspect FirstDocChanges, SecondDocChanges, and FullChanges for detailed results. The comparer also supports writing the visual comparison result to a Stream (PDFNET-62001, PDFNET-62285, PDFNET-62002).
Safe digital signature verification - New TryVerifySignature and TryVerify methods report verification details via VerificationResult rather than throwing verification exceptions. The result provides State, Message, IsCompromised, and VerificationException (PDFNET-62322).
Optional OCR and PDF chunking dependencies - The core package no longer requires OCR and PDF chunking dependencies when the related features are not used. PDF chunking reports missing packages via MissingOptionalDependencyException (PDFNET-62368, PDFNET-62286).
The following example compares two PDF documents, writes the visual comparison output to a stream, and checks whether they differ:
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static void ComparePdfDocumentsToStream()
{
// The path to the documents directory
var dataDir = RunExamples.GetDataDir_AsposePdf_DocumentCompare();
// Open PDF documents
using (var firstDocument = new Aspose.Pdf.Document(dataDir + "first.pdf"))
using (var secondDocument = new Aspose.Pdf.Document(dataDir + "second.pdf"))
using (var comparisonStream = new System.IO.FileStream(
dataDir + "comparison-result.pdf",
System.IO.FileMode.Create,
System.IO.FileAccess.Write))
{
// Compare documents and save the visual result
var result = Aspose.Pdf.Comparison.SideBySidePdfComparer.Compare(
firstDocument,
secondDocument,
comparisonStream,
new Aspose.Pdf.Comparison.SideBySideComparisonOptions
{
ComparisonMode = Aspose.Pdf.Comparison.ComparisonMode.IgnoreSpaces
});
System.Console.WriteLine(result.HasChanges
? "Changes were detected."
: "The documents are identical.");
}
}
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.7 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.6, we have added:
Integrated OCR for PDF text recognition - A new Aspose.Pdf.Ocr namespace allows you to extract plain text from rendered PDF pages by using OcrTextAbsorber. The API supports recognition for a single Page, for a whole Document, and through the familiar Page.Accept and PageCollection.Accept visitor pattern (PDFNET-58807).
OCR recognition options - Use OcrTextRecognitionOptions to configure the recognition language, rendering resolution, and separator inserted between recognized text from consecutive pages. The default options use OcrLanguage.English, 300 DPI, and a double line break as the page separator.
Signing with certificate and TSA - Certificate-based digital signing workflows can now use timestamp authority settings when a signing certificate and TSA server are used together (PDFNET-55205).
The following example shows how to recognize text from all pages of a PDF document:
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static void RecognizeTextWithOcr()
{
// The path to the documents directory
var dataDir = RunExamples.GetDataDir_AsposePdf();
// Open PDF document
using (var document = new Aspose.Pdf.Document(dataDir + "input.pdf"))
{
// Configure OCR recognition options
var options = new Aspose.Pdf.Ocr.OcrTextRecognitionOptions
{
Language = Aspose.Pdf.Ocr.OcrLanguage.English,
Resolution = 300,
PageSeparator = "\n\n"
};
// Recognize text from all pages
var absorber = new Aspose.Pdf.Ocr.OcrTextAbsorber(options);
document.Pages.Accept(absorber);
// Save recognized text
System.IO.File.WriteAllText(dataDir + "recognized-text.txt", absorber.Text);
}
}
The recognized text is available through the OcrTextAbsorber.Text property. If you call Visit or Accept again with the same absorber instance, the previous recognition result is replaced by the latest result.
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.6 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.5, we have added:
Marker-like PDF chunking for AI and RAG workflows - A new PDF chunking API splits PDF documents into semantic DocumentChunk objects for Retrieval-Augmented Generation (RAG), semantic search, and vector indexing scenarios. The new GetChunksAsync extension method converts a PDF to Markdown and returns chunks, while IngestAsync runs the complete pipeline: chunking, embedding generation, and upserting records into a vector store (PDFNET-60708).
Signing with certificate and TSA - Digital signing workflows can now use certificate-based signatures together with a timestamp authority (TSA). New constructor overloads for PKCS7 and PKCS7Detached accept TimestampSettings (PDFNET-62072).
Restored net40 compatibility package publication - Publication of the Aspose.PDF for .NET Framework 4.0 (DLLs only) compatibility package has been resumed. This package was previously discontinued beginning with Aspose.PDF for .NET 26.3, and has been restored in response to customer requests for .NET Framework 4.6.2 and .NET Framework 4.7 compatibility (PDFNET-62130, PDFNET-62139).
The following example shows how to split a PDF document into semantic chunks:
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static async Task GetDocumentChunks()
{
var dataDir = RunExamples.GetDataDir_AsposePdf_AI();
using (var document = new Aspose.Pdf.Document(dataDir + "RagGuide.pdf"))
{
var options = new Aspose.Pdf.AI.ChunkingOptions
{
MaxChunkSize = 512,
OverlapSize = 50
};
var chunks = await document.GetChunksAsync(options, sourceId: "my-document");
foreach (var chunk in chunks)
{
Console.WriteLine(string.Format("Chunk {0}: {1}", chunk.Index, chunk.Id));
Console.WriteLine(chunk.Content);
}
}
}
More information about PDF chunking is available in the PDF Chunking and Embedding article.
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.5 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.4, we have added:
Improved PDF-to-Image Conversion Performance – Significantly enhances the performance of PDF-to-image conversion, making high-volume image export workflows more efficient when rasterizing PDF pages to JPEG format (PDFNET-41182).
Optimized PDF/UA Structure Tree Processing – Improves the performance of PdfUaConvertStrategy.Process_7_1_structureTree for large PDF documents by replacing List<string> lookups with HashSet<ulong> and using a composite key instead of string formatting (PDFNET-61884).
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.4 Release Notes page.
Most Significant Changes
In Aspose.PDF 26.3, we have added:
Lossless image stream recompression during PDF optimization. The OptimizationOptions.CompressAllContentStreams property now also compresses eligible image XObject streams with FlateDecode, helping reduce file size while keeping image quality intact.
Image recompression now matches the selected ImageCompressionOptions.Encoding setting during optimization, ensuring more consistent results when using Jpeg2000 or Flate, along with image resizing, resolution limits, and quality controls.
Support for rendering comments when saving PDF documents as images or HTML, helping to preserve visible review markup when exporting annotated documents for sharing outside PDF viewers.
Improved PDF-to-TIFF rendering performance for high-volume rasterization scenarios, especially when exporting pages to bitonal TIFF images.
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.3 Release Notes page.
Other Notable Enhancements
RemoveUnusedStreams optimization scenario (PDFNET-40691).Backward Incompatible Changes
The compatibility package Aspose.PDF for .NET Framework 4.0 (DLLs only) is no longer published starting with Aspose.PDF for .NET 26.3.
Image recompression now follows the selected ImageCompressionOptions.Encoding value during optimization. This makes results more predictable when using Jpeg2000 or Flate together with image resizing, resolution limits, and quality settings.
Support for rendering comments when saving PDF documents as images or HTML. This helps preserve visible review markup when exporting annotated documents for sharing outside PDF viewers.
Improved PDF-to-TIFF rendering performance for high-volume rasterization scenarios, especially when exporting pages to bitonal TIFF images.
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.3 Release Notes page.
Other Notable Enhancements
RemoveUnusedStreams optimization scenario (PDFNET-40691).Backward Incompatible Changes
Aspose.PDF for .NET Framework 4.0 (DLLs only) is no longer published beginning with Aspose.PDF for .NET 26.3.Most Significant Changes
In Aspose.PDF 26.2, we have added:
The conversion can be achieved by using the RtfLoadOptions class.
// For complete examples and data files, visit https://github.com/aspose-pdf/Aspose.PDF-for-.NET
private static void ConvertRtfToPdf()
{
// The path to the documents directory
var dataDir = RunExamples.GetDataDir_AsposePdf_DocumentConversion();
// Initialize RTF load options
var options = new Aspose.Pdf.RtfLoadOptions();
// Open RTF document
using (var document = new Aspose.Pdf.Document(dataDir + "ConvertRtfToPdf.rtf", options))
{
// Save the document as PDF
document.Save(dataDir + "ConvertRtfToPdf_out.pdf");
}
}
Table Placement After Last Page Element – Added ability to add tables precisely after the last content element on a page. By using the Page.CalculateContentBBox() method to determine the bounding box of existing content, developers can calculate the exact position where the last element ends and place tables immediately after it. When table data exceeds the available space on the current page, the table will automatically flow to the next page starting from the top.
Complete Deletion of Invisible Text Objects – Added support for complete deletion of invisible text objects from PDF documents. The TextFragmentAbsorber class can now properly identify and remove text fragments that have their TextState.Invisible property set to true, or have a RenderingMode of TextRenderingMode.Invisible, or have a foreground color with zero alpha channel.
Detailed information about the changes and usage examples can be found on the Aspose.PDF 26.2 Release Notes page.
In Aspose.PDF 26.1, we have added:
Performance improvements – resolved poor performance when adding text to documents (PDFNET-34609) and overall performance issues (PDFNET-58899).
Enhanced rendering accuracy – fixed missing vertical text on the left side of PDFs (PDFNET-38618) and corrected Chinese character rendering during PDF-to-PNG conversion (PDFNET-58950).
Improved HTML conversion – the API now respects line color in HTML-to-PDF conversion (PDFNET-38417) and fixed text overlap issues in XFA-to-Standard conversion (PDFNET-38458).
Bug fixes for document structure – NumberingStyle now works correctly for Heading objects (PDFNET-38421), and PDF-to-HTML now preserves highlighted text color (PDFNET-50941).
Detailed information about the changes and usage samples is available on the Aspose.PDF 26.1 Release Notes page.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.