PDF and XSL-FO export
PowerBuilder can save the DataWindow’s data and presentation
as a Portable Document Format (PDF) file using two techniques. By
default, PowerBuilder saves as PDF using a distiller. PowerBuilder
can also save to PDF or XSL Formatting Objects (XSL-FO) format using
the Apache XML Formatting Objects processor.
Using the Ghostscript distiller
In order for users to use the SaveAs method
to save data as PDF with the distiller, they must first download
and install Ghostscript on their computers as described in the procedure
that follows.
The use of GPL Ghostscript is subject to the terms and conditions
of the GNU General Public License (GPL). Users should be asked to
read the GPL before installing GPL Ghostscript on their computers.
A copy of the GPL is available on the GNU Project Web server
.
The use of AFPL Ghostscript is subject to the terms and conditions
of the Aladdin Free Public License (AFPL). Commercial distribution
of AFPL Ghostscript generally requires a written commercial license.
For more information, see the Ghostscript Web site
.
To install Ghostscript:
-
Into a temporary directory on your computer,
download the self-extracting executable file for the version of
Ghostscript you want from one of the sites listed on the Ghostscript Web site
.See the Release Bulletin
for the version
of Ghostscript that was used for testing. -
Run the executable file to
install Ghostscript on your system.The default installation directory is C:Program
Filesgs. You can select a different directory
and/or choose to install shortcuts to the Ghostscript console
and readme file.
After installing Ghostscript, you should read the readme.htm file
in the doc subdirectory in the Ghostscript
installation directory to find out more about using Ghostscript
and distributing it with your application.
Save Rows As fails To save as PDF in the DataWindow painter, select File>Save
Rows As and select PDF as the Save As type. If you do not install
Ghostscript and use the default export properties, PowerBuilder
displays a pop-up window notifying you that Save Rows As failed.
If you install Ghostscript and then change the name of the directory
where Ghostscript is installed, Save Rows As PDF fails silently.
Location of files
When you save a DataWindow object as PDF using the distill
method, PowerBuilder searches in the following locations for an
installation of GPL or AFPL Ghostscript:
- The
Windows registry - The relative path of the pbdwe115.dll file
(typically SybaseSharedPowerBuilder) - The system PATH environment variable
If GPL or AFPL Ghostscript is installed using the Ghostscript
executable file, the path is added to the Windows registry.
If the Ghostscript files are in the relative path of the pbdwe115.dll file,
they must be installed in this directory structure:
|
1 |
<i>dirname</i>pbdwe115.dll<br /><i>dirname</i>gsgs<i>N.NN</i><br /><i>dirname</i>gsfonts |
where dirname is the directory that contains
the runtime DLLs and N.NN represents the release
version number for Ghostscript.
You might not need to distribute all the fonts provided in
the distribution. For information about fonts, see Fonts and font facilities supplied with Ghostscript
.
PostScript printer drivers
If your users have installed a PostScript printer on their
computers, the PostScript driver files required to create PDF files, PSCRIPT5.DLL, PS5UI.DLL,
and pscript.ntf, are already installed, typically
in C:WINDOWSsystem32spooldriversw32x86 on
Windows XP or C:WindowsSystem32DriverStoreFileRepository
tprint.inf_1a216484Amd64 on
a 64-bit Vista system. Your users must use the version of these
files that is appropriate to the operating system where the PDF
file is created. They should copy the files to the dirnamedrivers directory.
You must also deploy the related files that are installed
in SybaseSharedPowerBuilderdrivers.
These files can be copied to or installed on users’ computers.
They must be located in this directory structure:
|
1 |
<i>dirname</i>pbdwe115.dll<br /><i>dirname</i>drivers |
PostScript printer profile
Each user’s computer must have a PostScript printer
profile called Sybase DataWindow PS. This profile is added to your
development computer automatically when you save a DataWindow’s
rows to a PDF file in the DataWindow painter. You can use this method
to add a Sybase DataWindow PS printer on any computer where PowerBuilder
is installed.
Users can also add the profile manually using the Windows
Add Printer wizard in one of the following ways:
- By
clicking the Have Disk button on the Install Printer Software page
of the wizard, browsing to the Adist5.inf file
(installed with PowerBuilder in the SharedPowerBuilderdrivers directory)
or to another PostScript driver file, and on the Name Your Printer
page, changing the printer name to “Sybase DataWindow PS”. - By selecting a printer with PS in its name (such
as “Apple Color LW 12/660 PS”) from the
list of printers on the Install Printer Software page of the wizard,
and changing the printer name to “Sybase DataWindow PS” on
the Name Your Printer page.
See the chapter on the Print Manager in the Deploying
Applications and Components to .NET
book if your applications
print to PDF or XSL files from an IIS server.
Using the Apache FO processor
If your application uses the Apache processor to save as PDF
or XSL-FO, you must deploy the fop-0.20.4 directory
and the Java Runtime Environment (JRE) with your application.
They must be deployed in the same directory as the PowerBuilder
runtime files. For example, if you deploy your application and pbvm115.dll and
the other PowerBuilder runtime files in a directory called MyApplication,
the Apache processor must be deployed in MyApplication/fop-0.20.4,
and the JRE in MyApplication/jre.
However, you do not need to place a copy of the JRE in this location
if the full JDK is installed on the target computer and is in the classpath.
The following JAR files must be in the user’s classpath:
- fop-0.20.4uildfop.jar
- fop-0.20.4libatik.jar
- fop-0.20.4libxalan-2.3.1.jar
- fop-0.20.4libxercesImpl-2.1.0.jar
- fop-0.20.4libxml-apis.jar
- fop-0.20.4libavalon-framework-cvs-20020315.jar
For more information about the JRE, see “Java support”.
On Windows DBCS platforms, you also need to deploy a file
that supports DBCS characters to the Windows font directory on the
target computer, for example, C:WINDOWSfonts.
For more information about configuring fonts, see the Apache Web site
.