3.1 - General user requirements

We have identified above the more important differences and similarities between paper and WWW versions of a document and the criteria governing their functionality. We now express this information as the general requirements that the WWW document generator WebMaker should have.

1. WebMaker is able to convert any FrameMaker document file or files that make up a FrameMaker book.

   There may not be any restrictions made on the structure, layout or final presentation of the paper version of a document simply because a WWW version is to be produced. However, there is more than one way to achieve a desired structure, layout and final presentation of a document for paper. There is normally a `proper' way and this is usually the way that FrameMaker was meant to be used. Please see the section Recommendations for writers.

2. WebMaker can map all possible FrameMaker entities to HTML entities.

   FrameMaker entities that WebMaker can currently translate are text made up from ISO Latin 1 characters, non ISO Latin 1 characters, anchored frames, mathematical formulae, tables, footnotes, cross-references, lists of contents, glossaries, indices, native graphics and imported graphics. WebMaker offers a strategy to map all of these entities into HTML.

3. WebMaker can be configured to resolve all issues relevant only to the WWW version of a document.

   Information that is foreign to the environment of the paper version of a document may be supplied by the user to WebMaker. This information is then used to generate the WWW document with the desired presentation and functionality. Typical such information may be how should the blocks of text be split up into the different HTML files, navigation options, search options, whether a graphic is to be inlined or not, and conditional text enabling the inclusion of special HTML features and/or the exclusion of contents intended only for printing.

Generated with WebMaker