Convert Test Editor
The Convert Test Editor dialog box specifies the information that Arbortext Publishing Engine Test Utility passes to the built-in convert function.
You can access this dialog box in either of two ways:
• Choose a Convert test in the Test List dialog box, and then click Edit Test.
• Choose Convert in the Test Type dialog box.
|
|
Refer to the Programmer's Guide to Arbortext Publishing Engine for information on using the f=convert function and its parameters.
|
You can specify the following parameters in the Convert Test Editor:
• Input File — Specifies the location and name of the server-side file for an HTTP GET request. You must specify an absolute path or a Logical ID. Click Browse to navigate to an existing file.
• Input Type — Specifies the format of the input file in an HTTP GET or HTTP POST request. Choices are sgml, xml, html, word, wordml, docx, rtf, frame, pdf, text, or zip.
If you specify word, docx, rtf, pdf, frame, or html as the input type, you can also specify an Import Template.
|
|
wordml is not supported by Import Template in this release.
|
• Input entry — Specifies the name of the document file to be converted within a zip archive. You must specify Input entry if the input file is a zip archive so that Arbortext Publishing Engine can identify which file to convert.
• Entry Type — Specifies the format of the input entry document within a zip archive. Choices are sgml, xml, html, word, wordml, docx, rtf, frame, pdf, or text.
If you specify word, docx, rtf, pdf, frame, or html as the input type, you can also specify an Import Template.
|
|
wordml is not supported by Import Template in this release.
|
• Output Type — Specifies the output format for the converted document. Choices are sgml, xml, html, postscript, pdf, htmlhelp, web, rtf, and toc.
If you specify html or web, you can also specify the character Encoding for the output.
If you specify web, you can also specify a Frameset for the output.
• Stylesheet — Specifies the path and file name of the stylesheet (.style, .xsl, .fos, or .3f) to apply during file conversion. Note that profiling specified in the Profile field is applied before an XSL stylesheet is applied to the input file (followed by any remaining conversion instructions).
• Profile — Specifies how profiling should be applied to the input file before converting it to the output format. Customizer's Guide contains information about setting up profiling. Programmer's Guide to Arbortext Publishing Engine explains how to submit the profile parameter.
|
|
Do not apply profiling if you are using the Arbortext Publishing Engine Test Utility in embedded mode, as it will cause Arbortext Publishing Engine Interactive to stop processing. Run the Arbortext Publishing Engine Test Utility in server mode if you want to apply profiles.
|
• XML Header — Specifies whether to include the XML header when the Output Type is xml.
• Print Options — If Output Type is set to PDF and you are usingPostScript, this setting provides a list of print options that can be applied to the output file. You can specify some of the arguments that are supported for the print composed command.
|
|
When Arbortext Publishing Engine produces PDF using PostScript output, it sets a few ACL print composed command arguments during processing. Do not use any of the following print options to ensure your PostScript or PDF request doesn't interfere with the Arbortext Publishing Engine formatting and output processing:
[all | current | page_range]
[onepass | allpasses | noformat]
[force | auto]
[wait | nowait]
[printer=printer_name]
[file=path_name]
[color | monochrome]
[panel]
|
• Zip Output — Specifies whether Arbortext Publishing Engine bundles a document and related files into a zip archive file and returns it. Select yes to zip the document or no to pass only the document through, which is the default. All output types are supported. If you specify yes, you can also specify Zip root and Zip graphics dir.
• PDF Config File — If you choose PDF for output, and Arbortext Publishing Engine is publishing direct to PDF, you can specify a PDF configuration file (a .pdfcf file) to apply to the output.
• Subset — If the Output Type is set to HTML, this option allows you to specify how the document is processed for conversion to HTML output. If set to all, which is the default, the entire document is processed. If the Input File specified is based on the ATI XML DocBook DTD, you can choose toc to extract a subset of the document as a table of contents.
• Encoding — Specifies the character encoding to use for HTML or web output.
• Return formatter errors — returned a document containing formatting errors if the document doesn’t format.
• Frameset — Specifies a directory containing a frameset to use if you specify web for Output Type. If not specified, the document type's default will be used.
• Flatten Entities — Specifies whether to expand the entities and flatten the document.
• Convert 3D to 2D — Specifies whether to convert embedded intelligent (such as 3D and ISO) graphics to web-friendly graphics (GIF, JPEG, or PNG) when producing HTML or Web output.
• Zip root — Specifies the document file name for the converted document when it's returned in the zip archive file. If it's not specified, the default is e3out.type, where type is the file extension for the specified output type.
This field is activated if you specify yes for Zip Output.
• Zip graphics dir — Specifies the directory name that will contain a document's graphics within the zip archive file. The name you specify will be followed by .graphics in the returned zip archive, in the form graphicsdir.graphics.
This field is activated if you specify yes for Zip Output.
• Return parser errors — returned a document containing parser errors from parsing the document.
• Import Template — If you choose word, docx, rtf, pdf, html, or frame as the Input Type, you can specify the server-side location of the import map file using Import Template.
|
|
wordml is not supported in this release.
|
• Failure Mode — Specifies whether Arbortext Publishing Engine should evaluate the input document for specific error conditions before proceeding with the conversion.
◦ Link Checking — Verifies the input file's graphic and file entity references.
◦ Local Graphics — Collects graphic entity references specified by a URL (an http:// reference) from the input file and copies the graphic entities to a local temporary http cache subdirectory.
• Get — Indicates the request is an HTTP GET.
• Post — Indicates the request is an HTTP POST. Specify the file to be included in the message body in the Input File field. Click Browse to navigate to an existing file.
The buttons on the Convert Test Editor are:
• Run — Runs the selected test. If errors were detected, the Error window displays. If the test ran successfully, the Results window displays.
|
|
Server errors are returned in the Results window, not the Error window.
|
• View Results — Opens the Results window if the selected test ran successfully.
• Validate — Validates the HTTP request syntax for the selected test. It does not check the validity of the application being tested. The Error window displays if errors were detected.
• View Errors — Opens the Error window if errors were detected in the selected test.
