2017

Table Of Contents
USING QUARKXPRESS SERVER
154 | A Guide to QuarkXPress Server 2017
<METADATA>
<VALUE KEY=”Asset” ><![CDATA[1234567890]]>
</VALUE>
<
VALUE KEY=”Date” ><![CDATA[08.06.07]]>
</VALUE>
<VALUE KEY=”Password” ><![CDATA[Hello World]]>
</VALUE>
<
/METADATA>
<GEOMETRY SHAPE=”SH_RECT” PAGE=”1”>
<POSITION>
<TOP>5</TOP>
<LEFT>5</LEFT>
<BOTTOM>10</BOTTOM>
<RIGHT>10</RIGHT>
</POSITION>
</GEOMETRY>
</BOX>
To delete metadata that is associated with a box, use XML like the following:
<BOX>
<ID NAME=”BoxWithMetadata”/>
<METADATA>
<VALUE KEY=”Asset”></VALUE>
</METADATA>
</BOX>
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: