IBM
Contents Index Previous Next



More Information on Output Formats


PostScript Output

PostScript output may be generated as one standard PostScript file or one or more Encapsulated PostScript (EPS) files. When multiple EPS files are generated, a translation table will also be produced in a Map File, linking the name of a generated file to the contents.

Standard PostScript

A normal print operation generate one PostScript document. All data is represented uniformly, using the same paper format, header, footer etc. Only the scale and orientation might vary between pages.

Encapsulated PostScript (EPS)

The EPS output makes use of the scale and orientation settings for each document category. Since EPS files are not clipped, the internal scale has little importance when the file is imported into an external documentation or desktop publishing system.

Header, footer and adjacent page markers are not included in the output. Paper layout are determined from the Print preferences Frame*PaperFormat.

Scaling in EPS Files

The scaling options are handled as follows:

Handling of Expanded Text in PostScript

Expanded texts are the text contained in such symbols that are minimized1 in a graphical page, see Text / Additional Heading / Package Reference Symbols.

Standard PostScript

Expanded text is output as plain text using the font specified by the SDT*PrintFontFamily and SDT*PrintTextHeight preferences.

Encapsulated PostScript

Expanded text in EPS output is stored on separate files. One text file is generated for each logical page containing expanded text, regardless of the number of expanded texts in that logical page.

PostScript Standard Conformance

The generated PostScript code conforms to either of these standards:

FrameMaker Output

FrameMaker output may be generated either as:

Depending on the scale setting (see Scaling in EPS Files), each logical page will be represented as one or more cropped anchored frames in the output.

Header, footer and adjacent page markers are not included in the output. Paper layout are determined from the Print preferences Frame*PaperFormat.

Handling of Expanded Text in MIF

Expanded text (see Handling of Expanded Text in PostScript for an explanation) is inserted as plain text after the anchored frames generated for the corresponding logical page. In order to preserve the appearance of the users original text, hard returns are inserted where new lines are found.

MIF Conformance

The generated MIF files conform to FrameMaker Interchange Format version 4.00, which can be read into FrameMaker version 4.x, 5.x and 6.x without problems.

Importing into FrameMaker (UNIX only)

The X Window root window has an atom (property) that governs how FrameMaker communicates with SDL Suite and TTCN Suite. The name is arbitrary, but must defined both in SDL Suite and TTCN Suite as well as in FrameMaker. In the example below, the name _Frame_Import will be used.

To have FrameMaker behave in accordance, you should specify what resource to be used by SDL Suite and TTCN Suite when starting FrameMaker. The resource values should be entered in the SDT resource file (in which case all users are affected) or in a suitable user X resource file. The resource is called sdtfmimp*rpcProp.

Example 22 : X Resource file sample

...
sdtfmimp*rpcProp: _Frame_Import
...

There are multiple ways to set up FrameMaker. The resource Maker.rpcProp may be used for this.

Interleaf Output

Interleaf output may be produced as:

The generated pages are the same in both cases. A translation table is also generated in the latter case.

Depending on the scale setting (see Scaling in EPS Files), each logical page will be represented as one or more anchored frames in the output.

Header, footer and adjacent page markers are not included in the output. Paper layout are determined from the Print preferences Frame*PaperFormat.

Handling of Expanded Text in IAF

Expanded text (see Handling of Expanded Text in PostScript) is inserted as plain text after the frames generated for the corresponding logical page. In order to preserve the appearance of the users original text, hard returns are inserted where new lines are found.

IAF Conformance

The generated IAF files conform to Interleaf ASCII Format version 8.0 (used in Interleaf 5).

MSWPrint Output (Windows only)

The MSWPrint output can be used on Windows to print on any Windows printer, thus this is suitable if the printer does not support Postscript. As the complete print output using this option will be divided into several print jobs the printing should be done only on one side of the paper, otherwise the page numbering will not be as expected.

Handling of Expanded Text in MSWPrint

Expanded text (see Handling of Expanded Text in PostScript) is handled the same as for standard PostScript.

Microsoft Word Output (Windows only)

Word output can be used to print as a Microsoft Word document. A complete Word document is created and the generated pages are created as enhanced metafiles.

Header, footer and adjacent page markers are not included in the output. Paper layout are determined from the defaults when creating a new Word document. The image sizes can be set by the Image format option.

Handling of Expanded Text in Word output

Expanded text (see Handling of Expanded Text in PostScript) is inserted as plain text after the frames generated for the corresponding logical page. In order to preserve the appearance of the user's original text, hard returns are inserted where new lines are found.

1

Meaning resized to a minimal size.

2

MIF stands for Maker Interchange Format.

3

IAF stands for Interleaf ASCII Format.


http://www.ibm.com/rational
Contents Index Previous Next