Render XPS to OTP via .NET
.NET API to Export XPS to OTP on Windows, macOS, and Linux without using Microsoft® PowerPoint
Using a package of powerful File Format Automation APIs Aspose.Total for .NET you can easily Render XPS to OTP in two simple steps. By using PDF Processing API Aspose.PDF for .NET , you can transform XPS file format to PPTX. After that, by using Presentation Processing API Aspose.Slides for .NET , you can convert PPTX to OTP.
.NET API to Convert XPS to OTP
- Open XPS file using Document class
- Convert XPS to PPTX by using Save method
- Load PPTX file by using Presentation class
- Save the document to OTP format using
Save
method and set
Otpas SaveFormat
Get Started with .NET File Format APIs
Install from command line as nuget install Aspose.Total or via Package Manager Console of Visual Studio with Install-Package Aspose.Total.
Alternatively, get the offline MSI installer or DLLs in a ZIP file from downloads .
Document document = new Document("input.xps");
// save XPS as a PPTX
document.Save("PptxOutput.pptx", SaveFormat.Pptx);
// load PPTX with an instance of Presentation
Presentation presentation = new Presentation("PptxOutput.pptx");
// call save method while passing SaveFormat.Otp
presentation.Save("output.otp", SaveFormat.Otp);
Get XMP Metadata from XPS File via .NET
While converting XPS to OTP, you might need extra XMP metadata information to prioritize your batch conversion process. For example you can get and sort your conversion documents based on creation date and process the documents accordingly. Aspose.PDF for .NET allows you to access a XPS file’s XMP metadata. To get a XPS file’s metadata, you can create a Document object and open the input XPS file. After that, you can get the file’s metadata using the Metadata property.
Document doc = new Document("input.xps");
// get XPS XMP properties
Console.WriteLine(doc.Metadata["xmp:CreateDate"]);
Console.WriteLine(doc.Metadata["xmp:Nickname"]);
Console.WriteLine(doc.Metadata["xmp:CustomProperty"]);
Create Read Only OTP File via .NET
By using Aspose.Slides for .NET API, you can further enhance the features of your conversion application. One of the feature can be to create your output file read only to increase security. The API allows you to set your OTP file to Read-Only, which means users (after they open the presentation) see the Read-Only recommendation.
Presentation presentation = new Presentation("PptxOutput.pptx");
// make OTP read only
presentation.ProtectionManager.ReadOnlyRecommended = true;
// call save method while passing SaveFormat.Otp
presentation.Save("output.otp", SaveFormat.Otp);
Explore XPS Conversion Options with .NET
What is XPS File Format?
XPS, short for XML Paper Specification, is a file format created by Microsoft to represent fixed-layout documents. XPS files contain the content and print settings of a document, making them suitable for preserving the layout and appearance of a document across different devices and platforms.
The XPS format is based on XML (eXtensible Markup Language), a widely used markup language for structured data representation. XPS files encapsulate document content, such as text, images, vector graphics, and annotations, in a structured XML format. This enables easy interpretation and rendering of the document’s visual elements.
XPS files are conceptually similar to PDF (Portable Document Format) files in that they both aim to provide a reliable way to present and share documents while preserving their formatting and layout. However, PDF files have gained broader support across different software applications and hardware devices, making them more widely accepted and compatible.
To view and work with XPS files, Microsoft provides an XPS Viewer as part of the Windows operating system. Various third-party applications and tools also offer support for opening, creating, and converting XPS files. However, compared to PDF, the range of software and hardware supporting the XPS format may be more limited.
What is OTP File Format?
The OpenDocument Standard Format (ODF) serves as an XML-based file format for representing various electronic documents, including spreadsheets, charts, presentations, and word processing documents. The format is standardized by the Organization for the Advancement of Structured Information Standards (OASIS) and was initially adopted by ISO/IEC JTC1 SC34 in 2005. One of the key advantages of ODF is that it is an open format, meaning it is not restricted by copyright or patent limitations.
ODF is built upon the XML schema derived from the OpenOffice.org office suite and employs the Zip compression algorithm. Its design objective is to be platform-independent, enabling support across a wide range of applications and operating systems.
The ODF specification defines three main document types: text documents, spreadsheets, and presentations. Each document type corresponds to a specific XML schema. These schemas are designed to be extensible, allowing for the addition of application-specific features.
ODF documents have the capability to be encrypted and signed using the XML Encryption and XML Signature standards. This provides security and integrity options for sensitive or important documents.
Numerous office applications support the OpenDocument Format, including Apache OpenOffice, LibreOffice, IBM Lotus Symphony, and even Microsoft Office. This broad support ensures compatibility and facilitates the exchange and collaboration of documents across different software platforms.