Home
Publishing
Details about transformation scenarios and customizing various types of output
DITA to PDF Output Customization
CSS-based PDF Customization
Troubleshooting
Information about fixing publishing issues
Damaged PDF File

Introduction
Welcome to the User Manual of Oxygen XML Developer Eclipse plugin 26.1
Getting Started
Information and resources to help you get started using Oxygen XML Developer Eclipse plugin as quickly as possible
Installation
The requirements and installation instructions for each platform
Configuration
Description of all of the options that allow you to configure Oxygen XML Developer Eclipse plugin
Perspectives
The Editor, XSLT Debugger, XQuery Debugger, and Database perspectives
Editing Modes
The Text, Grid, , and Schema Design editing modes
Working With Documents
General information about features available when working with documents
Editing Supported Document Types
Details about the various types of supported documents and their unique editing features
Built-in Frameworks (Document Types)
The editing frameworks that are supported in Oxygen XML Developer Eclipse plugin
Additional XML Editing Frameworks (Document Types)
The custom frameworks that are supported in Oxygen XML Developer Eclipse plugin
Publishing
Details about transformation scenarios and customizing various types of output
- Transformation Scenarios
- WebHelp Output Customization
- DITA to PDF Output Customization
  - CSS-based PDF Customization
    - Overview
      A basic overview, technical details, and additional resources to help you get started
    - Generating PDF Output
      Information about generating PDF output using a command line tool or integration server
    - Publishing Templates
      Explains how to use Oxygen Publishing Templates to define the layout and style of the output
    - Customizing PDF Output Using CSS
      Numerous topics that provide instructions for how to customize your PDF output
    - Controlling the Publication Content
      Explains how using a bookmap offers more control over the output
    - XSLT Extensions for PDF Transformations
      Information about using XSLT extensions to customize PDF output
    - DITA-OT Extension Points
      Information about expanding the functionality through DITA-OT Extensions
    - Localization
      Information about configuring the language for PDF output
    - Security
      Details about how to set security permissions to protect PDF files
    - Troubleshooting
      Information about fixing publishing issues
  - XSL-FO to PDF Customization
- DocBook to PDF Output Customization
Working with XPath Expressions
Information about using XPath Expressions in Oxygen XML Developer Eclipse plugin
Working with Archives
Describes how to use the Archive Browser to work with various type of archives
Databases and SharePoint
Connecting to supported databases and integrating Oxygen XML Developer Eclipse plugin with SharePoint
Importing Data
Information about how to import data from external sources into XML documents
XSLT/XQuery Debugging
The debugging interface that detects problems with XSLT and XQuery transformations
Extension Points for the Oxygen Eclipse Plugin
A list of extension points available for the Oxygen Eclipse plugin
Tools
Specifics about the various tools that are included in Oxygen XML Developer Eclipse plugin
Troubleshooting
A compilation of common problems and their solutions
Scripting Oxygen
Details about the scripting possibilities that are available with Oxygen XML Developer Eclipse plugin
Glossary
Copyright
Legal information

Damaged PDF File

Problem

It is possible to get a PDF that cannot be opened in the PDF viewer. In this case, you might get an error similar to:

Error: PDF file is damaged - attempting to reconstruct xref table...
Error: Couldn't find trailer dictionary
Error: Couldn't read xref table

Cause

This usually means that your PDF viewer does not support a PDF version greater than 1.4. The main difference with newer PDF versions is that the xref table is compressed in a stream and is not available as a table.

Solution

You need to re-run the PDF transformation with the pdf.version parameter set to 1.4.