2017

Table Of Contents
USING QUARKXPRESS SERVER
156 | A Guide to QuarkXPress Server 2017
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
t
hat contains a note inserted by the Notes XT XTensions software. The note
contains “This is the text of a CopyDesk note,” which is represented as
VGhpcyBpcyB0aGUgdGV4dCBvZiBhIENvcHlEZXNrIG5vdGU=. If this text is passed
back to QuarkXPress Server in a
modify or construct request, the hidden text
i
nserted by the Notes XT XTensions software is preserved and can be read by the
Notes XT XTensions software if the project is opened in QuarkXPress.
The Custom Underline XTensions module feature also uses this approach, but also
stores the custom underline definitions in a binary data structure within the data of
the CLOSEPAREN hidden text entry:
<PARAGRAPH MERGE=”false” PARASTYLE=”Normal”>
<RICHTEXT MERGE=”false”>
The population of Iceland is 500,000,000.
</RICHTEXT MERGE=”false”>regular text</RICHTEXT>
<HIDDEN DATALEN=”0” OPCODE=”51526B41”
OWNER=”51526B” TYPE=”OPENPAREN”>
</RICHTEXT MERGE=”false”>text with custom
underline</RICHTEXT>
<HIDDEN DATALEN=”20” OPCODE=”51526B21”
OWNER=”51526B” TYPE=”CLOSEPAREN”>
<RICHTEXT
MERGE=”false”>/////wACAAAAAKj2AAIAAABqAAU=</RICHTEXT>
</HIDDEN>
<RICHTEXT MERGE=”false”>regular text</RICHTEXT>
</PARAGRAPH>
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.
Using interactivity
The <INTERACTIVITY> element describes an asset used as an interactive element
for a format such as App Studio and ePUB.
The specific schema for an interactive element is determined by the XTensions
module that owns that element, so such schemas are not defined here. The best way
to create or modify an
<INTERACTIVITY> element is to deconstruct it and then use
the deconstructed XML as a template. Below are some examples of App Studio
interactivity.