JggDvj2003Mar19/D0 .55 Draft FrameMaker Templates - April 8, 2003

Sep 26, 2026

Upload by Cart

FrameMaker templates for writing IEEE specifications, documented as an unapproved draft dated April 8, 2003 (Draft 0.55). The draft outlines how to use document templates when preparing IEEE drafts, and summarizes resolved and unresolved topics for template behavior. Resolved items cover list initialization, figure/table/equation counter restarting options, graphics snap-grid settings, and specific frame and table style conventions. Unresolved topics address consistent naming, table cell shading and references, figure/table interchange, and code fragment handling.

LanguageEnglish

CategoryPresentations

FormatPDF

Pages68

Reading Time24 min

AccessFree to download

Background

Resolved topics

Lists

Initializing

Figures

Tables

Table Row cross-references

C-code fragments

Unresolved topics

JggDvj2003Mar19 April 8, 2003 FrameMaker® templates for writing IEEE specifications Draft 0.55 Sponsor: Possibly the IEEE Computer Society Abstract: This standard defines templates that shall be used for IEEE Standards. Keywords: Style, formatting, template Copyright 2003 David V. James. All rights reserved. This is an unapproved draft, subject to change 1 JggDvj2003Mar19/D0 .55 DRAFT FRAMEMAKER TEMPLATES April 8, 2003 Background This manual describes the use of document templates developed by for use when writing IEEE drafts. This document is preliminary and subject to change. Edited by: David V. James 3180 South Ct Palo Alto, CA 94306 Home: +1.650.494.0926 Cell: +1.650.954.6906 Fax: +1.360.242.5508 Base: [dvj@alum.mit.edu](dvj@alum.mit.edu) Copyright 2003 David V. James. All rights reserved. 2 This is an unapproved draft, subject to change FOR WRITING IEEE SPECIFICATIONS JggDvj2003Mar19/D0 .55 April 8, 2003 Resolved topics: Resolved topics, for which further discussion may be unnecessary, include the following items: a) Lists. How should list initialization be performed? Are List1First, List2First, List3First needed? Status: 2003Mar26 . 1) Body, List1/List1First, List2/List2First initialize counts for List1, List2, and List3 .(in this sense, List1First, List2First, and List3First are be unnecessary) . 2) The List1First, List2First, and List3First styles are needed, to handle unusual cases where the preceding auto-initialize text is not available. b) Initializing. Can we safely eliminate initializing FigureTitleAFirst&TableTitleAFirst styles? Status: 2003Mar26 . Yes. The clause and annex numbering can do this automatically. c) When should figure/table/equation counts be restarted? Status: 2003Mar26. Either of the following options to be supported: 1) Reset at the start of each clause and at the start of each annex. 2) Reset at the start of the 1st clause and at the start of each annex. **However, techniques for supporting both options are TBD. d) Figures. Styles and conventions for FrameMaker graphics. 1) Snap grid. For Frame graphics, the default snap grid of 9 points is too coarse. Status: 2003Mar26 . The default snap-grid will be 3 points. However, groups may elect to use other snap-grid sizes. 2) What paragraph styles should be used for textual callouts? Status: 2003Mar26 . The following defaults to be supported, but not mandated: FigureText—Left justified Helvetica 8-point font. FigureTextCenter—Centered Helvetica 8-point font. FigureTextRight—Right justified Helvetica 8-point font. Note that these conventions are helpful, but need not be mandated. e) Tables. What styles should be used within tables? Status: 2003Mar26 . TableCell—Left-justified table entry (9-point font) . TableCellLeft—Left-justified table entry (9-point font) . TableCellRow—Centered table-row count entry (9-point font) . f) Table Row. How should a Row cross-references be formatted? Status: 2003Mar26 . Row 3.5-1. g) C-code fragments. What styles should be used for C-code fragments? Status: 2003Mar26 . Delete the table format, which has page-crossing problems. Use a distinct style for equations and C code fragments. Support single-line and multi-line C-code fragments. Copyright 2003 David V. James. All rights reserved. This is an unapproved draft, subject to change 3 JggDvj2003Mar19/D0 .55 DRAFT FRAMEMAKER TEMPLATES April 8, 2003 Unresolved topics: Topics believed to require further discussion include the following items: a) Naming. How can we migrate to intuitive&consistent style names? Status: Deferred 2003Mar26. This will be resolved after functionality is better known. b) Body vs T,Text: See if that change is compatible with the conversion process Status: Deferred 2003Mar26 . This could be affected by general naming decision, listed above. c) Table cell shading: Can table cells be shaded, to illustrate lower-relevance of res

FAQs

What is the purpose of the Draft 0.55 FrameMaker templates for IEEE specifications?

The standard defines templates to be used for IEEE Standards, and this manual describes using document templates developed for writing IEEE drafts.

Which topics are listed as resolved in the draft?

Resolved topics include list initialization approach, eliminating certain initialization styles, options for restarting figure/table/equation counts, graphics snap-grid defaults, and specific default styles for figures and tables.

What topics remain unresolved and still require further discussion?

Unresolved topics include consistent and intuitive style naming migration, compatibility of body versus T,Text conversion, table cell shading and reference support, implementing figures as tables, and how to classify and format code fragments.

Sep 26, 2026

Upload by Cart