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
document.getElementById("box2File").name = "";
}
document.getElementById("Page").name = "Page";
document.getElementById("Layout").name = "Layout";
url = prefix + port + renderer + file;
document.getElementById("form1").action = url;
}
</script>
</head>
This function reads the values you input in the various fields of the HTML form (server, port, project
name, scale, output type, text box name, text file to be flowed, picture box name, picture file to be
flowed, page number, and layout number).
Note: When you enter text in the "File on the Sever" text box, prepend "file:" to the path of the text file.
For example, suppose the text file is named "data.txt" and it is on the C: drive on the server. Specify its
path as: "file:C:\data.txt".
Since we are using the Quark Data Import XTensions software of QuarkXPress Server to flow text and
picture data, the suffix @dataimport is appended to the name of the box.
The complete URL is a combination of a server, port, and render type of the file name.
The form data is transmitted as follows:
The action of the form is defined in the HTML by this line of code in the JavaScript function
Submit_OnClick():
document.getElementById("form1").action = url;
The form's method is GET. The user agent gets the value (the URL) of the action, appends a ? to it, then
appends the form data set, which it encodes using the application/x-www-form-urlencoded content type.
The user agent then traverses the link to this URL. In this scenario, form data is restricted to ASCII
codes.
Working with QuarkXPress Server Manager
using an HTTP GET request
The methodology is identical to using HTTP GET with QuarkXPress Server (see above), except that
with Manager we recommend that you not use GET if you are working with non-ASCII characters. The
reason is that the behavior of GET requests in the case of non-ASCII characters is highly dependent on
the browser and there is no standard that all browsers follow. In such a case, use POST requests. Of
course, you would use Manager URL (/quark/servlet/qxpsm/...) if you are sending a request to
Manager.
Working with QuarkXPress Server using an
HTTP POST request
To view the HTML, click here
.
Use this HTML form to specify a server and its port where you want to send the request. You can
specify the name of a project, the output type, and scaling. You can also specify the name of a text box
and a picture box, and you can browse text and picture files on your local system to be flowed into them.
The text and picture files that you browse are sent to the server as a part of the post request. In addition,
you can specify the page and layout number of the project.
All the code described in the previous section will work with a few changes.
The form section begins with:
Page 33