9.5

Table Of Contents
Working with hidden text
In QuarkXPress, hidden text is used by features which need to include information within
the flow of text without that information being visible in its raw form, either on screen
or at output. XTensions modules for QuarkXPress and QuarkXPress Server can use the data
area in hidden text to store their custom data without changing the surrounding text. The
custom data in the hidden text is simply invisible when opened in a copy of QuarkXPress
that does not have the corresponding XTensions module. You can use hidden text in
Modifier XML to interpret information added by a custom QuarkXPress XTension or to
send instructions to a QuarkXPress Server XTensions during a modify or construct
request.
Each piece of hidden text is identified by an opcode. An opcode is a four-digit hexadecimal
number which specifies:
The developer ID of the developer who created the XTensions module.
The unique identifier of the hidden text type, as defined by the XTensions developer.
The type of hidden text entry (OPENPAREN, CLOSEPAREN, NONPAREN, or IGNORED)
An opcode is constructed as follows:
The structure of a hidden text marker
In Modifier XML, hidden text is represented by the HIDDEN element. By default, hidden
text is not output from the xml namespace. To output hidden text, specify the opcode=
parameter in your request, like so:
http://server:port/xml/projectname.qxp?opcode=51434450
This example URL outputs all of the hidden text inserted by the XTensions software with
this ID. To avoid byte order issues when cross-platform rendering is enabled, the XTID is
represented decimally, rather than with the usual char[4] representation.
If you specify opcode=*, QuarkXPress Server returns all hidden text in the XML output.
If you want only specific opcodes for a particular developer ID, you must pass the developer
A GUIDE TO QUARKXPRESS SERVER 9.5 | 141
USING QUARKXPRESS SERVER