Quark QuarkXPress Server - 9.2 User Manual
QXP Server 9.2 Web
Integration Guide
CONTENTS
Contents
Overview.........................................................................................10
Supported interfaces............................................................................................10
The Dynamic Publishing Process (DPP).................................................................10
The WIG and the XTensions Developer Kit (XDK)................................................11
Changes in this version...................................................................12
Getting started...............................................................................14
Getting started: HTTP and HTTPS........................................................................14
Dissecting a QXP Server URL........................................................................................14
Interpreting the QXP Server Manager response...........................................................15
HTTP GET and POST Requests.....................................................................................15
Getting started: Web services..............................................................................19
QRequestContext..........................................................................................................20
RequestService..............................................................................................................21
QRequest......................................................................................................................25
RequestParameters.......................................................................................................25
NameValueParam..........................................................................................................26
QContentData...............................................................................................................26
QException...................................................................................................................27
QXP Server Manager............................................................................................27
Using the Web interface.................................................................29
Understanding rendering......................................................................................29
Understanding logging.........................................................................................30
Understanding render types.................................................................................31
ave.................................................................................................................................31
eps.................................................................................................................................33
epub..............................................................................................................................35
jpeg...............................................................................................................................36
literal..............................................................................................................................37
pdf.................................................................................................................................38
png................................................................................................................................42
postscript.......................................................................................................................43
qcddoc..........................................................................................................................45
ii | QXP SERVER 9.2 WEB INTEGRATION GUIDE
CONTENTS
qxpdoc..........................................................................................................................46
screenpdf.......................................................................................................................47
swf.................................................................................................................................51
Understanding render modifiers...........................................................................53
Box................................................................................................................................53
Boxes.............................................................................................................................54
Compositionzone..........................................................................................................55
Layer..............................................................................................................................55
Layout............................................................................................................................57
Movepages....................................................................................................................57
Page..............................................................................................................................58
Pages.............................................................................................................................59
Scale..............................................................................................................................60
Spread...........................................................................................................................60
Spreads.........................................................................................................................60
Using content modifiers........................................................................................61
Inserting text.................................................................................................................61
Applying a font at import..............................................................................................62
Inserting a picture.........................................................................................................63
Saving a projects with a new name...............................................................................64
Importing XML with placeholders.................................................................................65
Using XML modify................................................................................................67
Modifying box properties and content.........................................................................67
Creating boxes..............................................................................................................71
Deleting boxes..............................................................................................................73
Grouping and ungrouping items...................................................................................74
Creating tables..............................................................................................................75
Using inline tables.........................................................................................................76
Modifying text attributes...............................................................................................79
Modifying picture properties.........................................................................................82
Importing data...............................................................................................................85
Exporting Job Jackets files during deconstruction.......................................................88
Using interactivity..........................................................................................................88
Using XML deconstruct and construct..................................................................88
Deconstructing a project...............................................................................................89
Constructing a project...................................................................................................92
Working with pages and spreads..................................................................................95
Working with layers.......................................................................................................96
Working with boxes.......................................................................................................96
Working with groups.....................................................................................................98
Working with pictures....................................................................................................99
Working with text........................................................................................................100
Working with tables.....................................................................................................102
QXP SERVER 9.2 WEB INTEGRATION GUIDE | iii
CONTENTS
Working with sections.................................................................................................104
Working with Composition Zones...............................................................................105
Using XSL transformation............................................................................................105
Working with lists........................................................................................................106
Working with anchored boxes.....................................................................................106
Working with placeholders..........................................................................................107
Working with metadata...............................................................................................109
Working with hidden text............................................................................................110
Creating and using hyperlinks.............................................................................111
Web hyperlinks............................................................................................................111
Anchor hyperlinks........................................................................................................111
Page hyperlinks...........................................................................................................111
Using the Streaming Document Provider...........................................................112
Using administrative request handlers...............................................................112
Addfile.........................................................................................................................113
Delete..........................................................................................................................116
Evaluate.......................................................................................................................117
Exportprefsasjj.............................................................................................................118
Fileinfo.........................................................................................................................119
Flush............................................................................................................................120
Flushall........................................................................................................................120
Getdocinfo..................................................................................................................121
Getdocpoollist.............................................................................................................122
Getlogs........................................................................................................................123
Getprefs......................................................................................................................123
Getprocessid...............................................................................................................124
Getprojinfo..................................................................................................................124
Getrendererprefs.........................................................................................................125
Getserverinfo...............................................................................................................126
Jobjacket.....................................................................................................................127
Preflight.......................................................................................................................127
Setprefs.......................................................................................................................128
Setrendererprefs..........................................................................................................129
Updateprefsfromjj.......................................................................................................134
Using the QXPSM SDK.................................................................135
Writing a Java QXPSM client..............................................................................135
Java sample: Deconstructing a project.......................................................................136
Java sample: Rendering a PDF....................................................................................136
Java sample: Chained request....................................................................................136
Java sample: AddFile request.....................................................................................137
Writing a .NET QXPSM client.............................................................................137
iv | QXP SERVER 9.2 WEB INTEGRATION GUIDE
CONTENTS
.NET sample: Deconstructing a project......................................................................138
.NET sample: Rendering a PDF...................................................................................139
.NET sample: Chained request...................................................................................139
Writing an Objective-C client for Mac OS or iOS................................................139
Objective-C sample: Deconstructing a project...........................................................141
Objective-C sample: Rendering a PDF.......................................................................141
Objective-C sample: Chained request........................................................................142
Extending QuarkXPress Server Manager...........................................................142
Writing special request handlers.................................................................................143
Implementing a custom load balancer........................................................................143
Keep document open (sessions).................................................................................144
Using the Extensibility tool..........................................................................................144
Understanding ManagerSDK.xml................................................................................146
Using the RequestParameters class.............................................................................147
Modifier DTD (annotated).............................................................149
Entities (Modifier DTD).......................................................................................149
ADDCELLS (Modifier DTD).................................................................................151
ALIGNHORSETTINGS (Modifier DTD).................................................................152
ALIGNVERSETTINGS (Modifier DTD).................................................................153
ALLOWBOXOFFPAGE (Modifier DTD)...............................................................153
ALLOWBOXONTOPASTEBOARD (Modifier DTD)..............................................154
ANCHOREDBOXREF (Modifier DTD)..................................................................154
ARTICLE (Modifier DTD).....................................................................................155
AUTHOR (Modifier DTD).....................................................................................155
BNSTYLE (Modifier DTD)....................................................................................156
BOTTOM (Modifier DTD)....................................................................................156
BOTTOMGRID (Modifier DTD)............................................................................156
BOX (Modifier DTD)............................................................................................157
BOXREF (Modifier DTD).....................................................................................159
CALLOUTANCHOR (Modifier DTD)....................................................................160
CALLOUTBOXREF (Modifier DTD)......................................................................161
CELL (Modifier DTD)...........................................................................................161
CHILDID (Modifier DTD).....................................................................................163
CLIPPING (Modifier DTD)...................................................................................163
COLGROUP (Modifier DTD)................................................................................165
COLSPEC (Modifier DTD)....................................................................................166
COLUMN (Modifier DTD)....................................................................................166
COMPONENT (Modifier DTD)............................................................................167
COMPOSITIONZONE (Modifier DTD).................................................................168
CONTENT (Modifier DTD)..................................................................................170
CONTENTPH (Modifier DTD)..............................................................................172
QXP SERVER 9.2 WEB INTEGRATION GUIDE | v
CONTENTS
CONTINUEDHEADER (Modifier DTD)................................................................172
CONTINUEDTROWSTYLE (Modifier DTD)..........................................................173
CONTOUR (Modifier DTD)..................................................................................173
CONTOURS (Modifier DTD)................................................................................174
COPYFIT (Modifier DTD).....................................................................................174
COPYRIGHT (Modifier DTD)...............................................................................175
DATAPROVIDER (Modifier DTD)........................................................................175
DELETECELLS (Modifier DTD)............................................................................175
DESCRIPTION (Modifier DTD)............................................................................176
DROPCAP (Modifier DTD)..................................................................................176
EBOOKMETADATA (Modifier DTD)...................................................................176
ENTRY (Modifier DTD)........................................................................................177
EVENTCOLSTYLE (Modifier DTD).......................................................................177
EVENTROWSTYLE (Modifier DTD).....................................................................177
FIRSTTCOLSTYLE (Modifier DTD).......................................................................178
FIT (Modifier DTD)..............................................................................................178
FITTEXT (Modifier DTD)......................................................................................179
FOOTER (Modifier DTD).....................................................................................180
FOOTERTROWSTYLE (Modifier DTD).................................................................181
FORMAT (Modifier DTD)....................................................................................181
FRAME (Modifier DTD).......................................................................................183
GEOMETRY (Modifier DTD)................................................................................184
GRID (Modifier DTD)...........................................................................................186
GRIDLINE (Modifier DTD)...................................................................................186
GROUP (Modifier DTD).......................................................................................187
GROUPCHARACTERS (Modifier DTD)................................................................188
GROWACROSS (Modifier DTD)..........................................................................188
GROWDOWN (Modifier DTD).............................................................................189
HEADER (Modifier DTD).....................................................................................189
HEADTROWSTYLE (Modifier DTD).....................................................................189
HEIGHT(Modifier DTD).......................................................................................190
HIDDEN (Modifier DTD)......................................................................................190
HYPERLINK (Modifier DTD)................................................................................191
ID (Modifier DTD)................................................................................................192
INLINETABLE (Modifier DTD).............................................................................192
INSET (Modifier DTD).........................................................................................193
INTERACTIVITY (Modifier DTD)..........................................................................193
ISBN (Modifier DTD)...........................................................................................194
KEEPLINESTOGETHER (Modifier DTD)..............................................................194
KEYWORDS (Modifier DTD)...............................................................................195
LASTTCOLSTYLE (Modifier DTD)........................................................................195
LAYER (Modifier DTD)........................................................................................195
LAYOUT (Modifier DTD).....................................................................................196
vi | QXP SERVER 9.2 WEB INTEGRATION GUIDE
CONTENTS
LAYOUTREF (Modifier DTD)...............................................................................197
LEFT (Modifier DTD)...........................................................................................198
LEFTCONTROLPOINT (Modifier DTD)................................................................198
LEFTGRID (Modifier DTD)...................................................................................198
LINESTYLE (Modifier DTD).................................................................................199
LINKEDBOX (Modifier DTD)...............................................................................200
LIST (Modifier DTD)............................................................................................201
LOCATION (Modifier DTD).................................................................................201
LOCKTOGRID (Modifier DTD).............................................................................201
MAX (Modifier DTD)...........................................................................................202
METADATA (Modifier DTD)................................................................................202
MIN (Modifier DTD)............................................................................................202
MOVEDOWN (Modifier DTD).............................................................................202
MOVELEFT (Modifier DTD).................................................................................203
MOVERIGHT (Modifier DTD)..............................................................................203
MOVEUP (Modifier DTD)....................................................................................203
ODDTROWSTYLE (Modifier DTD).......................................................................203
ODDTCOLSTYLE (Modifier DTD)........................................................................204
ORIGIN (Modifier DTD).......................................................................................204
OVERMATTER (Modifier DTD)............................................................................205
PAGE (Modifier DTD)..........................................................................................205
PAGEREF (Modifier DTD)...................................................................................206
PARAGRAPH (Modifier DTD)..............................................................................207
PARENTTABLE (Modifier DTD)...........................................................................208
PICTURE (Modifier DTD).....................................................................................208
PLACEHOLDER (Modifier DTD)..........................................................................211
POSITION (Modifier DTD)...................................................................................211
PROJECT (Modifier DTD)....................................................................................211
PUBLICATION (Modifier DTD)............................................................................212
PUBLICATIONCHANNEL (Modifier DTD)...........................................................213
PUBLISHER (Modifier DTD).................................................................................213
RELPOSITION (Modifier DTD).............................................................................213
RGBCOLOR (Modifier DTD)................................................................................213
RICHTEXT (Modifier DTD)...................................................................................214
RIGHT (Modifier DTD).........................................................................................222
RIGHTCONTROLPOINT (Modifier DTD)..............................................................223
RIGHTGRID (Modifier DTD)................................................................................223
ROW (Modifier DTD)...........................................................................................224
RUBI (Modifier DTD)...........................................................................................226
RUBITEXT (Modifier DTD)...................................................................................226
RULE (Modifier DTD)..........................................................................................227
RUNAROUND (Modifier DTD)............................................................................229
SAVEAS (Modifier DTD)......................................................................................231
QXP SERVER 9.2 WEB INTEGRATION GUIDE | vii
CONTENTS
SCALETO (Modifier DTD)....................................................................................232
SECTION (Modifier DTD)....................................................................................233
SHADOW (Modifier DTD)...................................................................................233
SHRINKACROSS (Modifier DTD).........................................................................235
SHRINKDOWN (Modifier DTD)...........................................................................236
SIZE (Modifier DTD)............................................................................................236
SPINEIMAGE (Modifier DTD)..............................................................................236
SPLINESHAPE (Modifier DTD)............................................................................237
SPREAD (Modifier DTD)......................................................................................238
STACKINGORDER (Modifier DTD)......................................................................238
STORY (Modifier DTD)........................................................................................238
SUPPRESSOUTPUT (Modifier DTD)....................................................................239
TAB (Modifier DTD)............................................................................................239
TABLE (Modifier DTD).........................................................................................240
TABLEBREAK (Modifier DTD).............................................................................242
TABLESTYLE (Modifier DTD)...............................................................................243
TABSPEC (Modifier DTD)....................................................................................243
TBODY (Modifier DTD).......................................................................................244
TCOL (Modifier DTD)..........................................................................................244
TCOLSTYLE (Modifier DTD)................................................................................244
TCONTINUED (Modifier DTD)............................................................................245
TEXT (Modifier DTD)...........................................................................................245
TEXTNODEPH (Modifier DTD)............................................................................247
TEXTPH (Modifier DTD)......................................................................................247
TFOOT (Modifier DTD)........................................................................................248
THEAD (Modifier DTD).......................................................................................248
TITLE (Modifier DTD)..........................................................................................248
TOP (Modifier DTD)............................................................................................248
TOPGRID (Modifier DTD)....................................................................................248
TROW (Modifier DTD).........................................................................................249
TROWSTYLE (Modifier DTD)...............................................................................250
VALUE (Modifier DTD)........................................................................................250
VERTEX (Modifier DTD)......................................................................................251
VERTEXPOINT (Modifier DTD)...........................................................................251
VERTICES (Modifier DTD)...................................................................................252
WIDTH (Modifier DTD)........................................................................................252
Sample applications.......................................................................253
Sample applications: QXP Server Manager........................................................253
ASP.NET samples........................................................................................................253
C# samples..................................................................................................................253
Java samples...............................................................................................................254
viii | QXP SERVER 9.2 WEB INTEGRATION GUIDE
CONTENTS
JSP samples.................................................................................................................254
Objective-C samples...................................................................................................254
Sample applications legal notice.........................................................................254
Contacting Quark..........................................................................263
Legal notices.................................................................................264
QXP SERVER 9.2 WEB INTEGRATION GUIDE | ix
OVERVIEW
Overview
Welcome to the QuarkXPress® Server Web Integration Guide (WIG). The WIG describes the
QuarkXPress Server interface and includes sample applications that demonstrate how to
build a solution that integrates with QuarkXPress Server or QuarkXPress Server Manager.
Supported interfaces
The WIG describes the interfaces available in QuarkXPress Server:
• HTTP: Lets you interact with the server using URLs that contain calls or point to XML
files that contain calls. You can write client applications in any language that supports
HTTP requests. For more information, see "Getting started: HTTP and HTTPS".
• HTTPS: Provides secure HTTP access.
• Web services: Lets you interact with the server via Web services using the
QuarkXPress Server Manager object model. You can write client applications in Java, .NET,
or any other programming language that can consume SOAP-based Web services. For more
information, see "Getting started: Web services".
To develop a custom load balancer or a custom application in Java, you must have
version 1.5 or 1.6 of the JDK.
The Dynamic Publishing Process (DPP)
The Dynamic Publishing Process (DPP) has several stages. You may not need to use all of
these stages every time, but this the order in which they occur:
• Pre-Processing Stage: During this stage, QuarkXPress Server performs any necessary initial
steps, such as creating style sheets, colors, and H&J rules for a new QuarkXPress project.
• Content Loading Stage: During this stage, QuarkXPress Server loads dynamic content into
boxes in the project.
• Layout Modification Stage: During this stage, QuarkXPress Server modifies the layout of the
project.
10 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
• Post-Processing Stage: During this stage, QuarkXPress Server examines the project and
performs maintenance tasks.
The WIG and the XTensions Developer Kit (XDK)
The WIG lets Web developers build client applications that use the features available in
QuarkXPress Server. The XDK lets software developers implement features that are not
available in QuarkXPress Server, such as server-side processing and application-specific
services.
The QuarkXPress Server XDK requires knowledge of C or C++.
OVERVIEW
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 11
CHANGES IN THIS VERSION
Changes in this version
This version of the QuarkXPress Server WIG includes the following changes.
New features
The following new features have been added:
• Inline tables: For more information, see "Using inline tables."
• Streaming document providers: For more information, see "Using the Streaming Document
Provider."
• App Studio enrichments: You can now create and modify App Studio assets in Modifier
XML. For more information, see "Using interactivity."
• The ability to create ePUB output with ePUB output styles. For more information, see
"epub."
• The ability to create hyperlinks. For more information, see "Creating and using hyperlinks."
Changes to the Modifier DTD
The following element types have been updated:
• PROJECT (Modifier DTD)
• STORY (Modifier DTD)
The following new element types have been added:
• BOTTOMGRID (Modifier DTD)
• COLGROUP (Modifier DTD)
• CONTINUEDTROWSTYLE (Modifier DTD)
• ENTRY (Modifier DTD)
• EVENTCOLSTYLE (Modifier DTD)
• EVENTROWSTYLE (Modifier DTD)
• FIRSTTCOLSTYLE (Modifier DTD)
• FOOTERTROWSTYLE (Modifier DTD)
12 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
• HEADTROWSTYLE (Modifier DTD)
• INLINETABLE (Modifier DTD)
• LASTTCOLSTYLE (Modifier DTD)
• LEFTGRID (Modifier DTD)
• ODDTCOLSTYLE (Modifier DTD)
• ODDTROWSTYLE (Modifier DTD)
• RIGHTGRID (Modifier DTD)
• TABLESTYLE (Modifier DTD)
• TBODY (Modifier DTD)
• TCOL (Modifier DTD)
• TCOLSTYLE (Modifier DTD)
• TCONTINUED (Modifier DTD)
• TFOOT (Modifier DTD)
• THEAD (Modifier DTD)
CHANGES IN THIS VERSION
• TOPGRID (Modifier DTD)
• TROW (Modifier DTD)
• TROWSTYLE (Modifier DTD)
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 13
GETTING STARTED
Getting started
Getting started: HTTP and HTTPS
The topics below describe how to create requests for the QuarkXPress Server Web interface.
For information about the options available in such requests, see "Using the Web interface."
You can submit HTTP and HTTPS requests to QuarkXPress Server as URLs, either manually
from a browser or automatically from an HTTP client application. QuarkXPress Server
processes such requests and returns rendered content in the HTTP or HTTP responses.
Depending on the type of request, the QuarkXPress Server preferences, and the type of
content returned, the rendered content may be downloaded by the end user, displayed in
the end-user's browser, or saved to a file system location accessible to QuarkXPress Server.
You can write a QuarkXPress Server client application in almost any language that can
generate HTTP GET/POST requests. A QuarkXPress Server HTTP-based solution typically
consists of QuarkXPress Server (running on a server computer connected to a network)
plus a front-end application (usually Web-based) that provides a graphical user interface
(GUI) for end users. The front-end application translates end users' input into HTTP or
HTTPS requests and sends the requests to QuarkXPress Server or QuarkXPress Server
Manager, which processes the requests and returns rendered content.
Dissecting a QXP Server URL
To interact with QuarkXPress Server from a Web browser, use a URL like the following:
http://[server]:[port]/[namespace]/[directory]/[DocumentName]?[parameter]=Value
•
[server]: The name or IP address of the computer for QuarkXPress Server or
QuarkXPress Server Manager.
•
[port]: The port number on which to contact QuarkXPress Server or QuarkXPress Server
Manager. The default port is 8080 for QuarkXPress Server and 8090 for QuarkXPress Server
Manager.
•
[namespace]: Defines what the URL action will be and any parameters and conditions
available to that namespace.
•
[directory]: The path in the document pool where the project is stored, relative to the
QuarkXPress Server document pool. To access the root level, no directory path is necessary.
14 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
GETTING STARTED
(Note that you can also supply assets as part of a multipart HTTP request. For more
information, see "Using HTTP POST with QXP Server.")
•
[DocumentName]: The name of the QuarkXPress project to be processed.
•
[parameter]: Further defines the URL action with attributes and values allowed for the
namespace or general call. Pass parameters in the form attribute=value, with parameters
separated by the "&" character.
For QuarkXPress Server Manager, use a URL like the following:
http://[server]:[port]/qxpsm/request/[namespace]/[directory]/
[DocumentName]?[parameter]=Value
Prior to QuarkXPress Server 9.0, you had to use different URL constructions when sending
requests to an instance of QuarkXPress Server Manager in a QPS installation than you did
when sending requests to a free-standing instance of QuarkXPress Server Manager. In
versions 9.0 and later, both can use /qxpsm/request/ after [port]/ .
You can now use both absolute and relative paths when you modify a project with SDK
objects or classes. Relative paths are almost always relative to the document pool. If you
use multiple QuarkXPress Server instances, you should use a common document pool.
Interpreting the QXP Server Manager response
When QuarkXPress Server Manager successfully processes a request through the HTTP
interface, the response is the same as QuarkXPress Server's response unless the user has
supplied additional parameters to QuarkXPress Manager. For more information, see
"Working with QuarkXPress Server Manager" in A Guide to QuarkXPress Server.
If an error occurs, QuarkXPress Server Manager retries the request, either on the same
QuarkXPress server instance or a different one (depending on the error and global settings
established in the QuarkXPress Server Manager client). If QuarkXPress Server Manager
cannot process the request, it returns an XML response describing the error, plus any
header error codes returned by QuarkXPress Server. For example:
<?xml version="1.0" encoding="UTF-8" ?>
<error>
<httpresponsecode>500</httpresponsecode>
<xpressservererrorcode>-43</xpressservererrorcode>
<xpressservererrormessage>File not found.</xpressservererrormessage>
<xpressserverextendedmessage> <![CDATA[ Error #-43 - File not found. ]]>
</xpressserverextendedmessage>
<xpressservermanagererrorcode>M8000001</xpressservermanagererrorcode>
<xpressservermanagererrormessage>The server could not locate the specified
file.
</xpressservermanagererrormessage>
</error>
HTTP GET and POST Requests
The topics below describe how you can use HTML to interact with QuarkXPress Server.
QuarkXPress Server supports both the GET and POST HTML methods. When you use the
GET method, the browser encodes form data into a URL. When you use the POST method,
form data is passed within the message body. Use the GET method only when the form
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 15
GETTING STARTED
processing is idempotent. In short: GET is for retrieving data, whereas POST can involve
storing or updating data, ordering a product, or sending an e-mail.
Using HTTP GET with QXP Server
Use HTML like the following to specify a server and port where you want to send a request.
You can specify the name of the target project, the output type, and a scaling value. You
can specify the name of a box and the path of a text or picture files to import into that
box, as long as the file's path is on the server's file system. You can also use HTML like the
following to specify the page number and layout number of the project.
The form section of the HTML should begin with the following line of code:
<form id = form1 method="GET" enctype="application/x-www-form-urlencoded">
For both GET and POST, the browser constructs a form data set and encodes it according
to the ENCTYPE attribute (you can use multipart/form-data for POST and
application/x-www-form-urlencoded (the default) for both POST and GET).
To create fields that let the user specify the server IP address, the port, and the project
name, use HTML like the following:
<TABLE cellSpacing=1 cellPadding=1 border=1 id=TABLE1 >
<TBODY>
<TR>
<TD>
<INPUT id=ServerTxt name=ServerTxt value="Server ID"
readOnly size=13 style="WIDTH: 107px; HEIGHT: 22px">
</TD>
<TD>
<INPUT id=Server maxLength=50 size=16 value=localhost name=Server
style="WIDTH: 170px; HEIGHT: 22px">
</TD>
</TR>
<TR>
<TD>
<INPUT id=PortTxt name=PortTxt value="Port Number"
readOnly size=13 style="WIDTH: 107px; HEIGHT: 22px">
</TD>
<TD>
<INPUT id=Port maxLength=50 size=17 value=8080 name=Port
style="WIDTH: 170px; HEIGHT: 22px">
</TD>
</TR>
<TR>
<TBODY>
</TABLE>
<TR>
<p></p>
<TD>
<INPUT id=DocTxt name=DocTxt value="Document Name"
readOnly size=13 style="WIDTH: 107px; HEIGHT: 22px">
</TD>
<TD>
<INPUT id=Doc maxLength=50 size=18 name=Doc style=
"WIDTH: 170px; HEIGHT: 22px">
</TD>
</TR>
To create a drop-down menu that lets the end user specify a render format, use HTML like
the following:
<SELECT id="select1" name="returntype">
<OPTION value="jpeg">JPEG</OPTION>
<OPTION value="pdf">PDF</OPTION>
<OPTION value="qxpdoc">QuarkXPress document</OPTION>
<OPTION value="eps">EPS Document</OPTION>
16 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
GETTING STARTED
<OPTION value="postscript">POSTSCRIPT</OPTION>
<OPTION value="png">PNG</OPTION>
</SELECT><td/>
To create a drop-down menu that lets the end user specify a rendering scale, use HTML
like the following:
<SELECT id="select2" name="scale">
<OPTION value="1">100%</OPTION>
<OPTION value="2">200%</OPTION>
<OPTION value="3">300%</OPTION>
<OPTION value="5">500%</OPTION>
<OPTION value=".5">50%</OPTION>
</SELECT><p/>
To create input fields that let the end user specify a box name and the name of a file to
be imported into that box, use HTML like the following:
<TD>
<INPUT id=box1Txt value="Box Name"
readOnly style="WIDTH: 181px; HEIGHT: 22px" size=16>
</TD>
<TD>
<INPUT id=box1 maxLength=256 size=43 style="
WIDTH: 293px; HEIGHT: 22px"></TD>
</TR>
<TR>
<TR>
<TD>
<INPUT id=box1FileTxt value="File on Server"
readOnly style="WIDTH: 181px; HEIGHT: 22px" >
</TD>
<TD>
<INPUT id=box1File maxLength=256 size=43 style="
WIDTH: 293px; HEIGHT: 22px">
</TD>
</TR>
To create fields that let the end user enter a page number a layout number, use HTML like
the following:
<TABLE cellSpacing=1 cellPadding=1 border=1 style="WIDTH: 188px; HEIGHT: 61px">
<TR>
<TD>
<INPUT id=PageTxt value = "Page"
readOnly style="WIDTH: 50px; HEIGHT: 22px" size=3>
</TD>
<TD>
<input id=Page size="16" maxlength="256"
style="WIDTH: 147px; HEIGHT: 22px">
</TD>
</TR>
<TR>
<TD>
<INPUT id=LayoutTxt value = "Layout"
readOnly style ="WIDTH: 50px; HEIGHT: 22px" size=4>
</TD>
<TD>
<input id=Layout size="16" maxlength="256"
style="WIDTH: 147px; HEIGHT: 22px">
</TD>
</TR>
</TABLE>
To create a button that lets the end user submit the request, use HTML like the following:
<input type="submit" value="Render document"
name="Submit" LANGUAGE="javascript"
onclick="return Submit_onclick()"/>
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 17
GETTING STARTED
The above HTML calls a function named Submit_onclick(). You can add such a function
to the <HEAD> section of the HTML. For example:
<head>
<TITLE>Quark Stream</TITLE>
<script ID="clientEventHandlersJS" LANGUAGE="javascript">
function Submit_onclick() {
var prefix;
var renderer;
var file;
var url;
var box1Name;
var dataImportStamp = "@dataimport";
prefix = "http://" + document.getElementById("Server").value + ":";
port = document.getElementById("Port").value + "/";
renderer = document.getElementById("select1").value + "/";
file = document.getElementById("Doc").value;
box1Name = document.getElementById("box1").value;
if (box1Name != "") {
document.getElementById("box1File").name = box1Name + dataImportStamp;
} else {
document.getElementById("box1File").name = "";
}
document.getElementById("Page").name = "Page";
document.getElementById("Layout").name = "Layout";
url = prefix + port + renderer + file;
document.getElementById("form1").action = url;
}
</script>
</head>
The Submit_onclick() function reads the values from the formand builds a request URL
using the server, port, and render type.
If the end user specifies a file name in the "File on Server" text box, he or she must add
file: to the beginning of the file path (for example, file:C:\data.txt).
The code above adds @dataimport to the end of the box name to accommodate data
import.
The action of the form is defined by this line:
document.getElementById("form1").action = url;
This form's method is GET. The user agent gets the value (the URL) of the action, appends
a ? to it, adds the form data set, and submits the URL.
In this scenario, form data must be in ASCII.
Using HTTP GET with QXP Server Manager
HTTP GET with QuarkXPress Server Manager works the same way as HTTP GET with
QuarkXPress Server (see "Using HTTP GET with QXP Server"), except that Quark does not
recommend using GET if you are working with non-ASCII characters. The behavior of GET
requests with characters is highly browser-dependent, and there is no standard that all
browsers follow. Instead, use POST.
18 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
Using HTTP POST with QXP Server
Use HTML like the HTML in "Using HTTP GET with QXP Server" to specify a server and port
where you want to send a request. You can specify the name of the target project, the
output type, and a scaling value. You can specify the name of a box and the path of a text
or picture files to import into that box, as long as the file's path is on the server's file system.
You can also use HTML like the HTML in "Using HTTP GET with QXP Server" to specify the
page number and layout number of the project. Differences between the GET method and
the POST method are described below.
The form section of the HTML should begin with the following line of code:
<form id = form1 method="post" enctype="multipart/form-data">
The following HTML creates a input fields that let the end user specify the name of a file
to be imported into a box:
<TD><INPUT id=box1FileTxt value="File on Client"
readOnly style="WIDTH: 180px; HEIGHT: 22px" ></TD>
<TD><input id=box1File type="file"
size="32" maxlength="256" style="WIDTH: 293px;
HEIGHT: 22px">
</TD></TR>
The action of the form is defined by this line:
GETTING STARTED
document.getElementById("form1").action = url;
The form's method is POST. The user agent conducts an HTTP post transaction using the
value of the action attribute (the URL), and a message is created according to the content
type specified by the enctype attribute.
When you use a multipart HTTP post request, you can include in the request any files
which are required by the rendering process, including QuarkXPress templates, picture
files, modifier XML, and digital publishing assets. For more information, see "Using the
Streaming Document Provider."
Using HTTP POST with QXP Server Manager
HTTP POST with QuarkXPress Server Manager works the same way as HTTP POST with
QuarkXPress Server (see "Using HTTP POST with QXP Server"), except that with
QuarkXPress Server Manager, you must use UTF-8.
Getting started: Web services
The Web services interface is a collection of request classes. You can download the SDK
WSDL class definitions from
http://[server]:[port]/qxpsm/services/RequestService?wsdl (replace [server]
with the QuarkXPress Server Manager computer's IP address and [port] with the
QuarkXPress Server Manager port number.
These classes can be chained together to form compound QuarkXPress Server requests.
The sample applications (see "Sample applications") show how to use these classes to invoke
a QuarkXPress Server command and manipulate the response.
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 19
GETTING STARTED
For more information, see "Using the Web interface." In addition to the classes listed there,
the Web services interface includes the following:
•
RequestService processes QuarkXPress Server requests. This object's generic
processRequest() method takes a QRequestContext argument and returns a
QContentData object containing the response. For more information, see the sample
applications and "Using the Web interface."
•
QRequestContext is the argument you pass to RequestService's generic
processRequest() method.This object contains settings which must be set once per
request. Set all chained requests inside the request context.
•
QRequest is the base class for all request objects (such as PDFRenderRequest).
Consequently, all request objects share some common data members.
•
RequestParameters is a generic class for executing any request and for adding dynamic
properties to a request.
•
NameValueParam is a generic class for adding dynamic properties to a request. This class
is specifically for requests that take a box's name and/or ID as the parameter name and
the box's content as the value.
QRequestContext
Description
•
QContentData is the response returned when a request is executed. QContentData is a
hyperlink that follows the same pattern as the classes above.
•
QException is the exception class for QuarkXPress Server Manager. Web services returns
a QException object if an error occurs with any Web service method. You can use try/catch
blocks to handle QException objects.
If you've written a Server XTensions module, you can extend the WIG to include any
changes it makes to the Modifier DTD by simply modifying an XML file and regenerating
the stubs.
To exclude empty tags in the request HTML, set the value of the appropriate variable to
null.
For Javadocs, WSDL schemas, and JSP samples, see the Welcome page that displays when
you launch QuarkXPress Server Manager.
The following topics describe the general Web services classes.
An argument passed to RequestService. Contains settings that must be set once per request. All
chained requests must be set inside the request context.
Web service data objectType
NameMembers
documentName
20 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
DescriptionTypes
File or object name on which the command will be rendered.String
GETTING STARTED
serverName
serverPort
userName
userPassword
maxRetries
requestTimeout
useCache
responseAsURL
bypassFileInfo
context
String
Integer
Boolean
Boolean
Boolean
Server name. Default is NULL. Load balancer searches for the host
itself in this case.
Port at which the desired server is listening.Integer
Server admin username.String
Server admin password.String
Max number of times to try executing the command before
returning failure.
Max time out in milliseconds.Integer
Indicates whether the cache should be checked for an existing
result or if the command should be executed again.
This value indicates whether the server should send the response
as-is (text or binary) or store the response on the server and return
its location as a URL. Because the object model works on SOAP,
which can be slow when transferring large binary files, you might
choose to set this value to "true" if you suspect that the response
is going to be several megabytes or larger.
Indicates whether file info should be fetched before executing the
command.
Context in which the command is being executed.String
Example, object
model
RequestService
Description
Methods
QRequestrequest
com.quark.qxpsm.QRequestContext rc = new com.quark.qxpsm.QRequestContext();
rc.documentName = this.DocumentSettings1.documentName.Text;
rc.responseAsURL = this.DocumentSettings1.responseAsURL.Checked;
rc.useCache = this.DocumentSettings1.useCache.Checked;
rc.bypassFileInfo = this.DocumentSettings1.bypassFileInfo.Checked;
//Create the service and call it QRequestContext object
RequestService svc = new RequestService();
com.quark.qxpsm.QContentData qc = svc.processRequest(rc);
Web service called to process the QuarkXPress Server request. RequestService has a generic method
named processRequest() that takes QRequestContext as an argument and returns QContentData
as the QuarkXPress Server response.
Web serviceType
processRequest
Processes the request context and returns the result.
QuarkXPress Server request is instances of request objects chained
together.
DescriptionTypeParameter
QRequestContextrequestCmd
Argument passed to
RequestService. Contains settings
that must be set once per request.
All chained requests are set inside
the request context.
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 21
GETTING STARTED
createSession
closeAlldocs
closeDoc
Creates a new session and returns a session ID.
DescriptionTypeParameter
timeout
Closes all open documents in the session without saving them. If the session
does not exist, an error is returned. If an error occurs while closing the
document, it is logged and the document is marked closed in the internal
cache. No error is returned.
sessionId
Closes the specified document without saving it. If the session does not exist,
an error is returned. If the document is not open, and error is returned. If the
document is open in another session, an error is returned. If an error occurs
while closing the document, it is logged and the document is marked closed
in the internal cache. No error is returned.
Long
String
Timeout for the session in
milliseconds. If no call is executed
in that time, session is expired and
all the open documents in that
session are closed without saving. If
0 is passed as value of timeout,
default timeout is used. If a negative
value is passed as timeout, the
session never expires.
DescriptionTypeParameter
Session whose documents are to be
closed.
closeSession
getOpenDocs
getOpenSessions
getPreferences
setPreferences
DescriptionTypeParameter
docName
sessionId
Closes the specified session. If the session does not exist, an error is returned.
If any documents are still open in the session, an error is returned.
sessionId
Gets all the open documents in the session. If the session does not exist, an
error is returned.
sessionId
Gets all open sessions.
Gets QuarkXPress Server preferences.
Sets QuarkXPress Server preferences.
String
String
Document to be closed.String
Session in which document was
opened.
DescriptionTypeParameter
Session to be closed.String
DescriptionTypeParameter
Session whose open documents are
sought.
getXPressDOM
Creates a DOM for the specified document.
22 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
GETTING STARTED
newDoc
Creates a new document for modification and keeps it open until further
notice. The document is created with a single layout. To create a more complex
document, use the processRequestEx API. If a document with the same name
is already open, an error is returned. If the session does not exist, an error is
returned.
DescriptionTypeParameter
docName
jobJacketName
jobTicketName
host
String
String
String
Document to be opened for
modification. Provide the name
only. You can proivde a relative
path when you save the document.
Name of the Job Jackets file to be
used. The Job Jackets file is assumed
to be already available on the
QuarkXPress server computer.
Name of the Job Ticket to be used.String
The QuarkXPress Server instance
that should be used for this
document modification. If null, this
value is supplied by the load
balancer. If the indicated server is
not an active registered server, an
error is thrown.
openDoc
port
sessionId
Opens the specified document and keeps it open until further notice. If the
document is already open, an error is returned. If the session does not exist,
an error is returned.
docName
host
port
sessionId
Integer
String
String
String
Integer
String
The port for the server specified in
the host parameter.
Session in which the document
should be opened.
DescriptionTypeParameter
Document (along with relative path
if required) to be opened for
modification.
QuarkXPress Server instance which
should be used for this document
modification. If null, this value is
supplied by the load balancer. If the
indicated server is not an active
registered server, an error is thrown.
The port for the server specified in
the host parameter.
Session in which the document
should be opened.
processRequestEx
Executes the request context. If a session ID is specified, the document is kept
open after the request is executed. If no session ID is specified, the request is
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 23
GETTING STARTED
executed normally without keeping the document open. If the document is
open in another session, an error is returned. If the document is marked dirty,
an error is returned (a document is marked dirty when the server that opened
the document has become inactive; in such a case, the document must be
closed and opened again).
DescriptionTypeParameter
saveAllDocs
QRequestContextreqContextObj
sessionId
Saves all open documents in the session. The documents are saved one by
one. If error occurs while saving a document, an error is returned immediately
and the rest of the documents remain unsaved. If a document is marked dirty,
an error is returned (a document is marked dirty when the server that opened
the document has become inactive; in such a case, the document must be
closed and opened again).
relativePath
String
String
Request to be executed.
Session in which the request should
be executed. This value may be null.
If a session ID is provided, the
document is kept open. If no session
ID is provided, the request is
executed normally, as if
processRequest had been called.
DescriptionTypeParameter
Relative path where open
documents should be saved. If this
value is provided, copies of open
documents with changes made so
far are saved in the new location.
The open documents are not saved
but have all of the changes made so
far.
saveDoc
sessionId
Saves the open document. If a document is marked dirty, an error is returned
(a document is marked dirty when the server that opened the document has
become inactive; in such a case, the document must be closed and opened
again).
docName
newName
relativePath
String
String
String
String
Session in which the document
exists.
DescriptionTypeParameter
Document to be saved. Must be the
same name that was used when
opening or creating the document.
New name of the document. If null,
the document is saved with the old
name.
Relative path where the document
should be saved. The relative path
can also contain the new name of
the document. If this is provided, a
copy of the open document with
24 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
GETTING STARTED
changes made so far is saved in the
new location. The open document
is not saved but has all of the
changes made so far.
Example, object
model
QRequest
Description
sessionId
getXPressDOMEx
getXMLFromXPressDOM
getXPressDOMFromXML
QRequestContext rc = new QRequestContext();
rc.documentName = "test.qxp";
rc.responseAsURL = false;
JPEGRenderRequest jpegRequest = new JPEGRenderRequest();
rc.request = jpegRequest;
RequestService svc = new RequestService();
QContextData response = svc.processRequest(rc);
Base class for all request objects (such as PDFRenderRequest). All request objects share some common
data members, which are described below.
Web service data objectType
Lets you create a DOM of a particular layout or portion of a layout.
Creates an XML string out of the DOM.
Takes a raw XML representation of a project as a string and returns an object
model representing that project, with Project as the root class.
String
Session in which the document
exists.
Additional
comments
NameMembers
RequestParameters
Generic class for executing any request and for adding dynamic properties to a request.Description
Web service data objectType
NameMembers
requestNamespace
You can use this class to send any request for which a specific class does not exist. When this
request exists in the chain, its namespace is concatenated with the namespaces of other requests.
That means the namespace provided here can be null.
The parameters of this class can be used to parameterize a request being sent to the server.
DescriptionTypes
QRequestrequest
QuarkXPress Server request that includes instances of request objects
chained together.
DescriptionType
Namespace of the request (for example, jpeg).String
NameValueParam[]params
Parameter array for the specified request (for
example, jpegquality).
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 25
GETTING STARTED
Example, object
model
NameValueParam
Description
QRequestContext rc = new QRequestContext();
RequestParameters request = new RequestParameters();
request.setRequestNamespace("jpeg");
rc.setRequest = request;
NameValueParam p1 = new NameValueParam();
p1.setParamName = "jpegquality";
p1.setTextValue = "4";
request.setParams(new NameValueParam[]{p1});
Generic class for adding dynamic properties to a request. This class is specifically for requests that take
a box name/id as the parameter name and the box content as the parameter value.
Web service data objectType
NameMembers
paramName
textValue
streamValue
String
String
byte[]
DescriptionType
Name of the parameter. In most cases this will be the name/ID of
the box.
Text value of the box. (You can set either textValue or
streamValue.)
Stream value of the box. (You can set either textValue or
streamValue.)
contentType
QContentData
A response to a Web Services call to QuarkXPress Server.Description
Web service data objectType
NameMembers
contentType
textData
responseURL
streamValue
encodingType
actualServerPortUsed
The MIME content type of the parameter.String
String
String
String
binary
String
DescriptionTypes
The type of the response. For example, "text/xml" or
"text/plain."
If the response type is text, this contains the text.
Otherwise, this value is null.
If the responseAsURL parameter was set to "true" in the
request, this contains the URL of the response.
Otherwise, this value is null.
If the response type is binary, this contains the byte
array. Otherwise, this value is null.
If the response type is text, this value indicates the
encoding of the text (for example, UTF-8 or ANSI).
Identifies the server port.String
actualServerUsed
26 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
Identifies the server.String
GETTING STARTED
Example, object
model
QException
Type
headers
multipartResponse
QRequestContext context = new QRequestContext();
context.setDocumentName("sample.qxp");
context.setResponseAsURL(true);
JPEGRenderRequest request = new JPEGRenderRequest();
request.setJPEGQuality("4");
context.setRequest(request);
RequestService requestService = new RequestServiceStub();
QContentData response = requestService.processRequest(context);
System.out.println(response.getResponseURL());
Exception class for QuarkXPress Manager.Description
Exception
NameMembers
httpResponseCode
managerErrorCode
String
String
If the response returned by the server is a set of headers,
this array contains the header response.
If the response returned by the server is multipart, this
array contains the multipart response parts.
DescriptionTypes
HTTP response code.String
QuarkXPress Server Manager error code.String
Example,
object model
QXP Server Manager
managerErrorMessage
serverErrorCode
serverErrorMessage
serverExtendedMessage
String docName = "notexisting.qxp";
try {
QRequestContext ctx = getRequestContext(docName);
QRequest request = getJPEGRequest();
ctx.setRequest(ctx);
QContentData response = getService().processRequest(ctx);
System.out.println(response.getResponseURL());
} catch (QException ex) {
// QuarkXPress Manager threw an QException and it is not
// a runtime exception. QException object will be returned.
System.out.println(ex.getServerErrorCode());
}
QuarkXPress Server Manager localized error message.String
QuarkXPress Server error code.String
QuarkXPress Server response message.String
QuarkXPress Server extended error message.String
The following topics are for people who want to enhance QuarkXPress Server Manager or
integrate it with other software.
Please refer to http://localhost:8090/qxpsmdocs/apidocs/index.html for manager
API documentation. (Note that the port number used to retrieve the API documentation
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 27
GETTING STARTED
is 8090 by default, but you should use whatever port number you specified when installing
QuarkXPress Server Manager.)
QuarkXPress Server Manager was developed using interface-based programming and uses
the Spring Framework to instantiate pluggable objects. When QuarkXPress Server Manager
starts up, it reads the contents of a Spring context definition file named
"ManagerContainerConfig.xml" and instantiates all of the beans listed in the file.
QuarkXPress Server Manager then initializes by reading various configuration options
from a file named "ManagerConfig.xml."
You can deploy QuarkXPress Server Manager in its own Tomcat container, in an external
Tomcat container, or in a shared Spring context. For more information, see "Deploying
QuarkXPress Server Manager" in the QuarkXPress Server ReadMe.
28 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
Using the Web interface
The topics below describe the features available via the QuarkXPress Server Web interface.
The topics covered here include the following:
• Render types are namespaces you can use to return a QuarkXPress project in a specified file
format.
• Render modifiers let you control which parts of a project are rendered and set the scale of
the returned renderings.
USING THE WEB INTERFACE
• Content modifiers let you alter the content and formatting of boxes in layouts without using
the XML modify parameter.
• XML modify lets you modify QuarkXPress projects using XML.
•
The xml namespace deconstructs a project according to the Modifier DTD. The construct
namespace lets you turn an XML representation of a QuarkXPress project back into a
QuarkXPress project.
• Administrative request handlers let you change the behavior of QuarkXPress Server.
QuarkXPress Server uses case-sensitive XML.
Understanding rendering
Rendering is the process in which QuarkXPress Server opens a QuarkXPress project,
transforms it into a different format (the render type), and then sends a response to the
requestor. Depending on the type of rendering operation, the response may be a message
or a rendered file.
For information on how to submit a render request, see "Getting started: HTTP and HTTPS."
Alerts
document type.
Please select a
QuarkXPress
document or
template.
HTTP Error #500Cannot open this
This alert displays if you try to render a file that is not a QuarkXPress project.
QXP SERVER 9.2 WEB INTEGRATION GUIDE | 29
USING THE WEB INTERFACE
read or write to disk.
required volume or
folder.
HTTP Error #404File not found
QuarkXPress Server Error #–43
This alert displays if you try to render a project that does not exist.
HTTP Error #500I/O error trying to
QuarkXPress Server Error #–36
This alert displays if QuarkXPress Server is running on Windows and a shared
network folder was selected as the document pool, but the folder is no longer
shared.
What to do: In the QuarkXPress Server administration interface, choose
Administration > Preferences > General and set Document Root Folder
to a shared folder.
HTTP Error #404Cannot find
QuarkXPress Server Error #–35
This alert displays if QuarkXPress Server is running on Mac OS and a shared
network volume was selected as the document pool, but the volume is no
longer shared.
What to do: In the QuarkXPress Server administration interface, choose
Administration > Preferences > General and set Document Root Folder
to a shared folder.
Example, GET
URL
Understanding logging
If a request succeeds, a transaction success message is written to the QuarkXPress Server
transaction log file. This message includes the transaction ID, date, time, request type,
project name, response type, response size in bytes, and client IP address. For example:
07/03/2011 14:37:47 - RequestURI = /xml/sample.qxp TransactionUUID =
afb6f457-80ae-4d5d-a434-ce9f3e089761 Client = 10.91.30.216 Type = text/xml
Size = 4846
If an alert is displayed, an error message is written to the QuarkXPress Server transaction
log file. The transaction entry contains the date and time of the request, the error code,
and the error message. The following is a sample of an error log transaction entry:
See Understanding loggingLogs
http://localhost:8080/sample.qxp
There are two ways to specify a render format:Notes
1. Enter the render type directly in the browser address
field:http://localhost:8080/pdf/project.qxp.
2. In the QuarkXPress Server administration interface, choose Administration > Preferences >
General and choose the default render type from the Default Renderer Type drop-down menu.
09/03/2011 13:54:33 - RequestURI = /sample.qcd TransactionUUID =
dffc3a7e-11fd-4d97-b3fe-8f2129353d58 Client = 10.91.30.216 Error #10120 Cannot open this document type. Please select a QuarkXPress document or template.
30 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
Loading...