9.2

Table Of Contents
Working with hidden text
Hidden text, represented in Modifier XML by the HIDDEN element, allows XTensions
software developers to insert custom, non-printing data into a text flow. This hidden text
can be retained when QuarkXPress Server deconstructs and reconstructs QuarkXPress
projects. For more information, see the Modifier DTD .
<PARAGRAPH MERGE="false" PARACHAR="HARDRETURN"
PARASTYLE="001-TEXT">
<RICHTEXT MERGE="false">
The population of Iceland is 500,000,000.
</RICHTEXT>
<HIDDEN DATALEN="100" OPCODE="51434410"
OWNER="514344" TYPE="CHARACTERTYPE">
<RICHTEXT LANGUAGE="USEnglish" MERGE="false">
VGhpcyBpcyB0aGUgdGV4dCBvZiBhIENvcHlEZXNrIG5vdGU=
</RICHTEXT>
</HIDDEN>
<RICHTEXT MERGE="false">
Iceland is located north of the Equator.
</RICHTEXT>
</PARAGRAPH>
The example XML extract above shows the output from the xml namespace of text that
contains a note inserted by the Notes XT XTensions software. Developed by Quark for
QPS, the Notes XT XTensions software stores its data as hidden text. The note contains
"This is the text of a CopyDesk note," which is represented as
"VGhpcyBpcyB0aGUgdGV4dCBvZiBhIENvcHlEZXNrIG5vdGU=" in the sample above.
If this text is passed back to QuarkXPress Server in a Modify or Construct request, the
hidden text inserted by the Notes XT XTensions software is preserved. Also, the hidden
text can be read by the Notes XT XTensions software if the project is opened in QuarkXPress.
The data within the RICHTEXT element inside a HIDDEN element is a Base 64-encoded
representation of the raw data that is stored within the hidden text. Considering that
hidden text in QuarkXPress can contain any type of data, and the structure of that data
is specified by the XTensions software that creates it, this method ensures that the data
can be safely represented in XML. Also, this data can be converted back into the same raw
data structure so that it can be read by the destination XTensions software. If the content
is edited, the destination XTensions software may not be able to interpret it. Only XTensions
software developers should attempt to interpret data from their own XTensions software.
For the <HIDDEN> element, the OPCODE attribute is a decimal representation of the XTension
ID of the XTensions software that inserted this hidden text. The OWNER attribute is a
decimal representation of the QuarkAlliance developer ID of the XTensions software
developer who inserted this hidden text. By default, hidden text is not output from the
xml namespace. To output hidden text, specify the opcode= parameter in your request
as follows:
http://server:port/xml/projectname.qxp?opcode=51433410
You can also specify "...opcode=*" to specify all hidden text in the XML output.
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.
110 | QXP SERVER 9.2 WEB INTEGRATION GUIDE
USING THE WEB INTERFACE