8.0
Table Of Contents
- Overview
- New and enhanced features
- Getting started
- Functions
- Function overview
- Render types
- Content modifiers
- Render modifiers
- XML modify
- XML deconstruct and construct
- About XML deconstruct/construct
- xml
- construct
- Deconstructing a project
- Constructing a project
- Working with pages and spreads
- Working with layers
- Working with boxes
- Working with pictures
- Working with text
- Working with tables
- Working with Composition Zones
- Using server XSLT
- Working with lists
- Working with anchored boxes
- Working with placeholders
- Working with metadata
- Working with hidden text
- Administrative Request handlers
- The Modifier DTD
- Sample applications
- Contact Quark
- Legal notice
Using server XSLT
You can use an XSLT file to transform the XML returned by the xml namespace into other formats.
You might find this feature useful if you want the
xml namespace to return an XML representation that uses a different schema or a subset of the returned
data.
There are two ways to using this feature. The first way is to select Use Default XSLT and specify the
path to an XSLT file in the preferences for QuarkXPress Server (Server/QuarkXPress Server >
Preferences > Modifier pane). If you choose this approach, the XSLT file is applied to all XML returned
by the
xml namespace.
XML area of the Modifier pane of the
Preferences dialog box
The second way to use XSL is to use the
XSL parameter in the request URL. If the XSL parameter specifies the absolute path to an XSLT file on
the server, QuarkXPress Server uses that XSLT file to transform the response to that call. For example:
http://QXPServer8:8080/xml/project1.qxp?modify=file:path to XML file on server&XSL= path to
XSLT file on server
To make returned XML use the Modifier DTD, uncheck Use default XSLT and do not use the XSL
parameter in your calls to the
construct namespace.
Note: QuarkXPress Server currently supports only XML output from XSL transformation.
Page 171