Latest posts by techwriter (see all)
- 15 Questions to Ask After You Finish a Technical Document Project - February 12, 2018
- THY’s Perfect Information Design - February 9, 2018
- Waterfall vs. Agile Models in Technical Documentation - February 7, 2018
© 2010 Ugur Akinci
I love FrameMaker. I’ve been using it on an almost daily basis for the last 12 years. It’s my authoring and publishing tool of reference for all book-length manuscripts with images, tables, TOC, Index, and multiple lists (of tables, figures, etc.), and complex pagination. It’s solid, scalable without any worries, and has a great XML-engine built right in. It’s ready for most of your structured authoring and single-sourcing needs.
Here are some trivia facts perhaps you didn’t know about Adobe FrameMaker:
Half of the world’s top 20 banks use FrameMaker for mission-critical publishing, typically producing approximately 10,000 documents per hour.
A single FrameMaker document can contain millions of paragraphs/images/tables, thousands of different master pages, and tens of thousands of variables and cross-references.
A single FrameMaker table can contain millions of cells. Table cells can contain millions of images and multiple tables, nestled to any level.
20,000-page FrameMaker catalogs can contain multiple, complex indexes and hundreds of thousands of cross-references.
A FrameMaker book can contain hundreds of documents, each of any length, including hundreds of tables of contents and indexes.
(Source: Adobe corporation)