can't get graphics to appear on screen (FOSI ?)

[ptc-1599051]

and since they're not on-screen, they won't appear in print preview either. Everything else works fine - valid SGML no errors.

I have graphic tags and sheet tags, and they have attributes filled in. Graphic entities are defined and the pictures themselves are located in the proper directory. ACL switch graphicdisplay is ON.

But I can't get the graphics to appear on the screen. I can't get the Insert Graphic File dialog box to appear. If I try to add a new graphic or sheet tag, it tells me graphics are not allowed by the DTD. That's preposterous - I'm right next to an existing graphics tag. There are 160 other graphics spread throughout the file.

There has to be some small switch or something? Can someone shed some light on this? FOSI displays everything else correctly on screen (generated text, indentions) how could it do all that and just NOT DISPLAY GRAPHICS?

Arbortext 5.2 / Windows 7 / CMM doctype (ATA industry standard)

JH

[SuzanneNapoleon]

It sounds like the graphic elements need to be declared as such in the .dcf file, which is in the doctype directory. Find the Specials tag, insert a <Graphic> tag for each element that is supposed to be a graphic, and fill in the relevant attributes. It will look something like this in ASCII:

<Specials>

<Graphic element="graphic" filename="name"/>

...

</Specials>

[TimPhelps]

Suzanne is probably has answered your question.

See Arbortext Editor's Help topics that describe the .dcf file

Enabling graphics support for a document type

Graphic elements and their attributes are defined in the document type. However, before graphics can be inserted and manipulated in a document, the graphic elements and their attributes must be configured in the document type configuration file (.dcf file). Review your document type to determine the graphic elements and their attributes since not all graphic settings in the .dcf file are valid for all graphic elements.

Note also that if the document type has an associated .style file, then any graphics elements must be styled in Arbortext Styler before the graphics will appear in the Arbortext Editor window. See the Arbortext Styler Help for more information on styling elements.

Note

Arbortext Styler imports information from a document type’s .dcf file when you create a new StylerSheet for the document type. However, once a StylerSheet is associated with a document type, any changed settings in that stylesheet override the original settings in the document type’s .dcf file.

To enable graphics support for a document type:

1. Open Arbortext Architect.
2. Choose File→Open.
3. Locate the directory in which the document type whose .dcf file you want to modify is saved, and click Select.
4. Once the document type is loaded, choose Edit→DCF. If the document type has a .dcf file, it displays in the Arbortext Architect DCF Editor window. If there is no .dcffile associated with this document type, Arbortext Architect automatically creates one.
5. Locate the Specials element in the DCF Editor. If the file doesn’t include a Specials element, add one.

   Note

   Open the Document Type Viewer (Tools→Document Type Viewer) to view the element hierarchy for the .dcf file. This will help you determine the valid location for the Specials element.
6. Place your cursor next to the Specials element, choose Insert→Markup, and then choose Graphic.
7. Click next to the Graphic element to open the Modify Attributes dialog box.

   Note

   You must have the Force Required Attributes Entry Edit preference selected for this dialog box to open automatically.
8. In the element field, select the element that you want to define as a graphic element.
9. Specify whether the graphic element will use file names or entities to reference graphics. If you specify both an entity attribute and a file name attribute for an element, Arbortext Editor will use the file name.
   • filename — Enter the name of the attribute that will hold the path and file name of the graphic.
   • entity — Enter the name of the attribute that will hold the entity name for the graphic file.
   Specify the appropriate attributes:
   • cropHeight — Enter the name of the attribute whose value supplies the height dimension when cropping the graphic.
   • cropLowerLeftX — Enter the name of the attribute whose value supplies the lower left X coordinate to be used as a starting point for cropping.
   • cropLowerLeftY — Enter the name of the attribute whose value supplies the lower left Y coordinate to be used as a starting point for cropping.
   • cropWidth — Enter the name of the attribute whose value supplies the width dimension when cropping the graphic.
   • inline — Enter yes if the element is an inline graphic element. The default is no.
   • horizOffsetAmount — Enter the name of the attribute whose value supplies the amount of horizontal offset at which the graphic displays.
   • horizOffsetPercent — Enter the name of the attribute whose value supplies the percentage of the width of the graphic to offset horizontally when displayed.
   • horizScale — Enter the name of the attribute whose value supplies the percent magnification at which the graphic displays.

     Note

     uses the value specified for horizscale for both horizontal and vertical scaling in this release.
   • notation — Enter the name of the graphic notation attribute. For graphics, the notation would likely correspond to a file format (for example, EPS, TIF, or GIF) within the DTD.
   • primary — Choose yes if you want the selected element to be the primary graphic element. The default setting is no.If there are multiple elements with primary set to yes, then the last element in the list is considered the primary graphic element. If no element has primary set toyes, then the first element in the list is considered the primary graphic element.Arbortext Editor inserts the primary graphic element when users select Insert→Graphic (when set promptgraphictags is set to off).
   • processor — Enter the name of the attribute whose value specifies the graphic’s processor type.

     Note

     Use The processor attribute when graphic processor access is supported on the Windows version of Arbortext Editor. This allows users to open a graphics processor from Arbortext Editor.
   • reproDepth — Enter the name of the attribute whose value supplies the height (depth) dimension when scaling the graphic.
   • reproWidth — Enter the name of the attribute whose value supplies the width dimension when scaling the graphic.
   • view — Enter the name of the attribute whose value supplies the initial view to display for an intelligent graphic.

     Note

     If you use an Arbortext Styler stylesheet (.style file) to control the display in Arbortext Editor, you must also define the view attribute in the Arbortext Styler Graphic Details dialog box. Refer to the Arbortext Styler help for more information about that dialog.
   • resolution — Enter the name of the attribute whose value supplies the resolution at which the graphic was created.
   • scaleToFit — Enter the name of the attribute whose value enables the scale-to-fit feature for the graphic.
   • vertOffsetAmount — Enter the name of the attribute whose value supplies the amount of vertical offset at which the graphic displays.
   • vertOffsetPercent — Enter the name of the attribute whose value supplies the percentage of the height of the graphic to offset vertically when displayed.
   • vertScale — Enter the name of the attribute whose value supplies the percent magnification at which the graphic displays.

     Note

     This setting, vertScale is not supported in this release. Arbortext Editor uses the value specified for horizscale for both horizontal and vertical scaling.
10. Click OK when you have finished specifying attributes.
11. Choose File→Save to save the changes you have made to the .dcf file.

Please note though that Arbortext Editor 5.2 is not supported on Windows 7.

It is not until version 5.4 that Windows 7 is supported.