8.0

from the text specified in the request. What could be the problem?

This may be due to the font applied on the text box. If you create a request
to import or flow Unicode text in a text box, and the font for the specific
Unicode language is not applied to it, then text flowed in the text box may
appear different than what was specified in the request. To get correct
output, replace the font of the text box with the font for the specific
Unicode language. For example, suppose a document is created with a text
box to which Arial font is applied. Upload or Save the document in the
document pool. Now create a request to flow Greek or Russian text in this
text box. The preview generated from QuarkXPress Server will not show
the same text in the text box as was specified in the request. To obtain the
correct output, change the font of text box to Arial Greek (for Greek) or
Arial CYR (for Russian) in the document. Save the document and upload
the document to the server. Create a request to flow the Unicode text in
the text box. Correct characters will now be displayed in the document.

This problem can also occur if the font fallback

feature is turned OFF in QuarkXPress Server. If this feature is turned
ON, then QuarkXPress Server automatically applies the correct fonts,
depending on the script being used. This feature is turned ON by default.


How many render types work with the clang parameter?

clang works for all render types supported in QuarkXPress Server.


How can else can Unicode data be sent to the server? You can also send
Unicode data to the server in the following ways, which do not require
clang and cplatform to be in the URL:


"URL encoded UTF-8" string in the URL


UTF-8 encoded XML files (in construct/modify)


UTF-8 text file in data import


Word, RTF files
Page 194