Recent from talks
Nothing was collected or created yet.
Adobe FrameMaker
View on WikipediaThis article needs additional citations for verification. (May 2008) |
| Adobe FrameMaker | |
|---|---|
Editing a document in Structured Mode in FrameMaker 9 on Windows Vista | |
| Developer | Adobe |
| Stable release | Summer 2020 release [1]
|
| Written in | C/C++[2] |
| Operating system | 64-bit version of Microsoft Windows 10[3] |
| Type | Document processor, XML editor |
| License | Trialware |
| Website | adobe |
Adobe FrameMaker is a document processor designed for writing and editing large or complex documents, including structured documents. It was originally developed by Frame Technology Corporation, which was bought by Adobe.
Overview
[edit]FrameMaker became an Adobe product in October 1995 when Adobe purchased Frame Technology Corp.[4] Adobe added SGML support, which was eventually adapted into XML support. In April 2004, Adobe stopped supporting FrameMaker for the Macintosh.[5]
This reinvigorated rumors surfacing in 2001 that product development and support for FrameMaker were being wound down. Adobe denied these rumors in 2001,[6] later releasing FrameMaker 8 at the end of July 2007, FrameMaker 9 in 2009, FrameMaker 10 in 2011, FrameMaker 11 in 2012, FrameMaker 12 in 2014, FrameMaker (2015 release - confusingly, internal version 13.0) in June 2015, FrameMaker 2017 (internal version 14.0) in January 2017, FrameMaker 2019 (internal version 15.0) in August 2018, FrameMaker 2020 (internal version 16.0) in 2020, and FrameMaker 2022 (internal version 17.0) in 2022.
FrameMaker has two ways of approaching documents: structured and unstructured.
- Structured FrameMaker is used to achieve consistency in documentation within industries such as aerospace, where several models of the same complex product exist, or pharmaceuticals, where translation and standardization are important requirements in communications about products. Structured FrameMaker uses SGML and XML concepts. The author works with an EDD (Element Definition Document), which is a FrameMaker-specific DTD (Document Type Definition). The EDD defines the structure of a document where meaningful units are designated as elements nested in each other depending on their relationships, and where the formatting of these elements is based on their contexts. Attributes or Metadata can be added to these elements and used for single source publishing or for filtering elements during the output processes (such as publishing for print or for Web-based display). The author can view the conditions and contexts in a tree-like structure derived from the grammar (as specified by the DTD) or as formatted in a typical final output form.
- Unstructured FrameMaker uses tagged paragraphs without any imposed logical structure, except that expressed by the author’s concept, topic organization, and the formatting supplied by paragraph and character tags.
When a user opens a structured file in unstructured FrameMaker, the structure is lost.
MIF
[edit]MIF (Maker Interchange Format) is a markup language that functions as a companion to FrameMaker. MIF always had 3 purposes. The first was to represent FrameMaker documents in a relatively simple ASCII-based format, which can be produced or understood by other software systems and also by human operators. The second was to ensure any version of FrameMaker could read a document produced by any other version, at least to the extent it had the same features. While every version of FrameMaker could read the last couple of version's documents, reading them all took too much software effort and testing, so reading MIF was sufficient. The third was to ensure that FrameMaker would never lose a writer's work. If FrameMaker crashed, it would first write out the current document in MIF.
Any document that can be created interactively in FrameMaker can also be represented, exactly and completely, in MIF (the reverse, however, is not true: a few FrameMaker features are available only through MIF). All versions of FrameMaker can export documents in MIF, and can also read MIF documents, including documents created by an earlier version or by another program.
History
[edit]This section needs additional citations for verification. (April 2013) |
Frame Technology was founded in 1986 by David Murray, Charles Corfield, Steven Kirsch, and Vickie Blackslee. [7]
While working on his doctorate in astrophysics at Columbia University, Corfield, a mathematician alumnus of the St John's College, Cambridge, decided to write a WYSIWYG document editor on a Sun-2 workstation.
The only substantial DTP product at the time of FrameMaker's conception was Interleaf, which also ran on Sun workstations.[8]
After only a few months, Corfield had completed a functional prototype he called /etc/publisher. The prototype caught the eye of salesmen at the fledgling Sun Microsystems, which lacked commercial applications to showcase the graphics capabilities of their workstations. They got permission from Corfield to use the prototype of /etc/publisher as demoware for their computers.
Kirsch and Blakeslee were founding members of Mouse Systems, where they brought on Murray as Director of Application Software Development. In early 1986, Kirsch and Murray were visiting Sun Microsystems where they were given a demonstration of /etc/publisher. They thought there was a great opportunity for this and contacted Corfield. After several days of meetings they decided to form a company together. Kirsch, Murray, and Blakeslee left Mouse Systems and Corfield moved from New York to join them.[9]
Originally written for SunOS (a variant of UNIX) on Sun machines, FrameMaker was a popular technical writing tool, and the company was profitable early on. Because of the flourishing desktop publishing market on the Apple Macintosh, the software was ported to the Mac as its second platform.
In the early 1990s, a wave of UNIX workstation vendors—Apollo, Data General, MIPS, Motorola and Sony—provided funding to Frame Technology for an OEM version for their platforms.
At the height of its success, FrameMaker ran on more than thirteen UNIX platforms, including NeXT Computer's NeXTSTEP, Dell's System V Release 4 UNIX and IBM's AIX operating systems.
Sun Microsystems and AT&T were promoting the OPEN LOOK GUI standard to win over Motif, so Sun contracted Frame Technology to implement a version of FrameMaker on their PostScript-based NeWS windowing system. The NeWS version of FrameMaker was successfully released to those customers adopting the OPEN LOOK standards.
At this point, FrameMaker was considered an extraordinary product for its day, not only enabling authors to produce highly structured documents with relative ease, but also giving users a great deal of typographical control in a reasonably intuitive and totally WYSIWYG way. The output documents could be of very high typographical quality.
Frame Technology later ported FrameMaker to Microsoft Windows, but the company lost direction soon after its release. Up to this point, FrameMaker had been targeting a professional market for highly technical publications, such as the maintenance manuals for the Boeing 777 project, and licensed each copy for $2,500. But the Windows version brought the product to the $500 price range, which cannibalized its own non-Windows customer base.
The company's attempt to sell sophisticated technical publishing software to the home DTP market was a disaster. A tool designed for a 1,000-page manual was too cumbersome and difficult for an average home user to type a one-page letter.
Adobe Systems acquired the product and returned the focus to the professional market. Then, they released a new version under the name Adobe FrameMaker 5.1 in 1996. Today, Adobe FrameMaker is still a widely used publication tool for technical writers, although no version has been released for the Mac OS X operating system, limiting use of the product. The decision to cancel FrameMaker for OS X caused considerable friction between Adobe and Mac users, including Apple itself, which relied on it for creating documentation. As late as 2008, Apple manuals for OS X Leopard[10] and the iPhone[11] were still being developed on FrameMaker 7 in Classic mode; Apple has since switched to using InDesign.
FrameMaker versions 5.x through 7.2 (from mid-1995 to 2005) did not contain updates to major parts of the program (including its general user interface, table editing, and illustration editing), concentrating instead on bug fixes and the integration of XML-oriented features (previously part of the FrameMaker+SGML premium product). FrameMaker did not feature multiple undo until version 7.2 (its 2005 release).
FrameMaker 8 (2007) introduced Unicode, Flash, 3D, and built-in DITA support. Platform support included Windows (2000, XP, and Vista) and Sun Solaris (8, 9, and 10).
FrameMaker 9 (2009) introduced a redesigned user interface and several enhancements, including: full support for DITA, support for more media types, better PDF output, and enhanced WebDAV-based CMS integration. Platform support for Sun Solaris and Windows 2000 was dropped, leaving Windows XP and Windows Vista as the sole remaining platforms.
FrameMaker 10 (2011) again refined the user interface and introduced several changes, including: integration with content management systems via EMC Documentum 6.5 with Service Pack 1 and Microsoft SharePoint Server 2007 with Service Pack 2.
Other FrameMaker tools
[edit]- FrameMaker Publishing Server is an online document processor server for automated creation of multi-use content types. The web interface enables users to direct aggregation of differing information sources routinely into detailed a presentation in multiple environments on numerous devices.[12]
Alternatives and competition
[edit]There were several major competitors in the technical publishing market, such as Arbortext, Interleaf, and Corel Ventura. Many academic users now use LaTeX,[13] because modern editors have made that system increasingly user-friendly, and LyX allows LaTeX to be generated with little or no knowledge of LaTeX. Several formats, including DocBook XML, target authors of technical documents about computer hardware and software. Lastly, alternatives to FrameMaker for technical writing include Help authoring tools and XML editors.
See also
[edit]References
[edit]- ^ "Download FrameMaker". Archived from the original on 2021-09-07. Retrieved 2021-09-07.
- ^ Lextrait, Vincent (January 2010). "The Programming Languages Beacon, v10.0". Archived from the original on 2018-01-09. Retrieved 2010-03-14.
- ^ "FrameMaker system requirements". August 2018. Archived from the original on 2021-03-14. Retrieved 2019-03-21.
- ^ Nadile, Lisa. "Adobe to buy Frame, adding content apps to tools." PC Week 12.25 (1995): 3. Business Source Premier. EBSCO. Web. 6 June 2011.
- ^ Dalrymple, Jim (2004-03-23). "Adobe discontinues FrameMaker for Macintosh". macworld.com. Archived from the original on 2021-03-06. Retrieved 2019-12-28.
- ^ "Rumors Of FrameMaker's Death Have Been Greatly Exaggerated [sic]". The Mac Observer. 2001-02-09. Archived from the original on 2016-04-25. Retrieved 2007-05-26.
- ^ "David J. Murray Biography". IEEE Xplore. IEEE. Retrieved September 20, 2024.
- ^ "On Beyond Numbers: New Applications" (PDF). Release 1.0. 1988-02-16. p. 10. Archived (PDF) from the original on 2022-10-09.
- ^ Murray, David J. (July–September 2019). "Frame Technology and FrameMaker". IEEE Annals of the History of Computing. 41 (3). IEEE: 62–74. Bibcode:2019IAHC...41c..62M. doi:10.1109/MAHC.2019.2926662.
- ^ John Gruber (2008-06-03). "Apple still using Framemaker in Classic". Daring Fireball. Archived from the original on 2013-01-26.
- ^ Michael Tsai (2007-05-01). "Old Meets New". Archived from the original on 2020-12-02. Retrieved 2013-01-21.
- ^ "Adobe FrameMaker Publishing Server". www.adobe.com. Archived from the original on 2021-04-26. Retrieved 2021-04-26.
- ^ Pepe, Alberto (February 21, 2017). "How many scholarly articles are written in LaTeX?". Authorea. doi:10.22541/au.148771883.35456290.
External links
[edit]- Official website

- FrameUsers.com Archived 2015-05-08 at the Wayback Machine FrameMaker users' largest online reference site and community
- History of FrameMaker
- Adobe FrameMaker Online Forum
Adobe FrameMaker
View on GrokipediaIntroduction
Overview
Adobe FrameMaker is a desktop publishing and document processor application designed for creating, editing, and publishing large-scale, complex technical documents.[1] It serves as a robust tool for technical communicators, enabling the production of high-volume content with advanced formatting and layout capabilities.[5] The software is primarily used for developing technical manuals, books, policy documents, and structured content such as XML- or DITA-based outputs.[7] It supports both unstructured workflows, which allow free-form layout design, and structured workflows, which enforce XML/DITA standards for content reuse and modularity, all within a unified environment.[5] As of 2025, Adobe FrameMaker operates on a subscription-based model, with plans at US$39.99 per month under annual commitment (approximately USD 480 per year) and higher for month-to-month options.[8] The latest major release is FrameMaker 2022 (version 17.0), accompanied by ongoing updates such as Update 8 in October 2025, which emphasize stability improvements and minor enhancements.[6] Originally developed for UNIX systems, it has evolved to provide native support on Windows, with legacy versions available for other platforms including macOS.[1]Key Features
Adobe FrameMaker provides robust authoring tools that support both unstructured and structured content creation. It features a WYSIWYG editing environment with keyboard shortcuts like Tab for indentation and Ctrl+B for bold formatting, enabling intuitive manipulation of DITA and XML elements. The structure view offers an enhanced interface for searching and editing XML/DITA content, while out-of-the-box support for Lightweight DITA (LwDITA) allows users to author and publish Lw-Topic and Lw-Map files directly without additional setup. Recent updates include AI-assisted content generation for smarter authoring workflows.[9] The software excels in publishing capabilities, supporting exports to PDF, HTML5, EPUB, and mobile-optimized formats, including compliance with PDF/A and PDF/X standards. Recent optimizations in its PDF engine have accelerated generation by up to 65%, streamlining workflows for large-scale document production.[7] Modern interface enhancements improve usability for complex projects. A new navigation pane displays the document structure based on styles, facilitating quick orientation in unstructured content. The document splitter utility allows dividing large files into chapters using paragraph formats or markers. High-resolution display support ensures crisp rendering on 4K screens, and users can embed YouTube videos directly into documents for interactive outputs in PDF and HTML5.[10] Content management features facilitate seamless integration and localization. FrameMaker imports content from Microsoft Word or Markdown files, converting them to DITA or native formats with automated mapping. Language-specific smart quotes are enabled via the Hunspell dictionary in preferences, adapting punctuation to regional standards. Translation workflows are enhanced through XLIFF export and import, with pre-segmentation for efficient round-trip editing.[9] Performance optimizations make FrameMaker suitable for handling extensive documents. Its 64-bit architecture, introduced in 2020, provides enhanced stability and memory management for files reaching gigabyte sizes. The subscription model delivers cloud-like updates, ensuring access to these improvements without manual installations.[11] Cross-platform compatibility centers on Windows 10 and 11 with full native support on 64-bit systems, while macOS and Linux users rely on legacy versions or virtualized environments for operation.[11]History
Origins and Development
Adobe FrameMaker originated from the efforts of Frame Technology Corporation, founded in April 1986, in San Jose, California, by Charles Corfield, David Murray, Steve Kirsch, and Vickie Blackslee. The company was established without initial outside capital, relying on a $100,000 loan from Kirsch to bootstrap operations. The primary motivation stemmed from Corfield's need for advanced tools to publish his physics dissertation at Stanford University, where he developed a prototype called /etc/publisher on a Sun-2 workstation to handle rich-content documents with hypertext capabilities.[12][13] Early development of FrameMaker evolved directly from Corfield's /etc/publisher prototype. By October 1986, a FrameMaker 0.6 prototype was released and presold to early customers, leading to the full version 1.0 launch in March 1987 after six months of enhancements. This initial release targeted UNIX workstations, focusing on high-end technical publishing for engineering documentation, and achieved cash-flow positivity within a year. Funding grew through key deals, including a $1 million agreement with Toshiba in June 1987 and $3.1 million in Series A venture capital in May 1988, alongside OEM partnerships with UNIX vendors such as Sony, Motorola, DEC, Wang, and Matsushita for customized versions on their platforms.[12][13][14] By 1992, Frame Technology marked significant milestones, including an initial public offering in February that valued the company at $146 million, with 1991 revenues reaching $41.7 million, 297 employees, and over 100,000 users. The software expanded beyond UNIX to support Apple Macintosh and Microsoft Windows platforms, alongside broader UNIX compatibility, with version 3.0 released in summer 1991 introducing features like tables and conditional text. A key pre-acquisition innovation was the introduction of FrameBuilder in October 1992, providing underlying SGML support for structured document handling and establishing FrameMaker's foundation in standardized markup for technical publishing.[12][14]Acquisition by Adobe and Version Evolution
In October 1995, Adobe Systems completed its acquisition of Frame Technology Corporation for approximately $500 million in stock, integrating FrameMaker into Adobe's portfolio of desktop publishing and document management tools.[3][15] This move allowed Adobe to expand its reach into technical documentation markets, particularly for complex, long-form content in industries like aerospace and engineering.[16] Under Adobe's ownership, early versions from 5.1 (released in 1996) to 7.0 (2002) prioritized cross-platform compatibility, supporting Windows, UNIX, and Mac OS with improved stability for large documents.[17] These releases also enhanced PDF integration, enabling direct export to Adobe Acrobat formats for streamlined printing and distribution workflows.[18] Development during this period shifted toward tighter alignment with Adobe's ecosystem, including better interoperability with Acrobat and Illustrator.[19] From version 8.0 (2007) to 12.0 (2014), Adobe introduced significant advancements in internationalization and structured content handling. Version 8.0 added full Unicode support via UTF-8 encoding, allowing multilingual authoring without character limitations, alongside initial DITA and XML enhancements for topic-based technical writing.[20][21] Subsequent updates, including version 14.0 (2017) introducing 64-bit support, improved performance for handling massive files exceeding 32-bit memory constraints, while expanding XML import/export for standards-compliant workflows.[22][23] More recent iterations continued to modernize output and architecture. Version 14.0 (2017 release) debuted responsive HTML5 publishing layouts, enabling mobile-optimized, interactive outputs with Section 508 accessibility compliance.[24] Version 15.0 (2019) provided full native 64-bit support on Windows, accelerating publishing speeds by up to 65% for PDF and HTML5 generation compared to prior 32-bit modes.[25][26] Version 16.0 (Summer 2020) transitioned to 64-bit only, dropping 32-bit compatibility, and introduced a new Navigation pane for easier document overview and element management.[27][28] Version 17.0 (September 2022) incorporated beta support for Lightweight DITA (LwDITA), simplifying structured authoring for lighter-weight topic models.[29] As of November 2025, no major new version beyond 17.0 has been announced, with Adobe focusing on incremental updates to the 2022 release. For instance, the October 2025 security patch (Update addressing APSB25-101) resolved critical vulnerabilities.[30] Community discussions in early 2025 highlighted an unclear long-term roadmap, amid Adobe's emphasis on cloud-integrated technical communication tools.[31] Adobe's stewardship marked a pivot from perpetual licenses to a subscription model starting with version 16.0 in 2020, priced at $29.99 monthly or $359.88 annually for individual users, aligning FrameMaker more closely with the Adobe Creative Cloud ecosystem for technical documentation.[32] This shift underscored a broader focus on integrating FrameMaker with Adobe Experience Manager and other tools for collaborative, multichannel publishing in enterprise environments.[33]Technical Architecture
Unstructured and Structured Authoring
Adobe FrameMaker supports two primary authoring paradigms: unstructured and structured, allowing users to choose based on the needs of their content creation workflow. Unstructured authoring provides a free-form environment where content is created using templates that define presentation elements such as fonts, paragraph formats, table styles, and character formats.[34] This mode is particularly suited for non-technical long documents, such as books, where visual layout and design flexibility are prioritized over rigid content rules.[34] In contrast, structured authoring enables element-based editing, where content is organized into semantic elements defined by an Element Definition Document (EDD) or Document Type Definition (DTD), often in conjunction with DITA maps for modular documentation.[35] This approach enforces content reuse through attributes and validates structure to ensure consistency, making it ideal for technical publications that require precise organization and multi-output publishing.[35] FrameMaker's structured mode supports full authoring and publishing of DITA 1.3 topics and maps, as well as lightweight DITA (LwDITA) introduced in the 2022 release, including features like conditional text via DITAVAL files and variable management for dynamic content adaptation.[29][8] The key differences between these modes lie in their focus: unstructured authoring emphasizes visual design through a What You See Is What You Get (WYSIWYG) interface, relying on style sheets for formatting, while structured authoring prioritizes semantic markup, visible and editable in the Structure View pane for hierarchical navigation.[34][36] FrameMaker offers a hybrid capability, allowing conversion between modes using Conversion Tables that map paragraph, character, and table styles from unstructured files to corresponding XML elements, facilitating migration while preserving content integrity.[37] Workflow tools in structured authoring enhance efficiency through the Structure View, which supports drag-and-drop manipulation of elements for reorganization, such as moving sections or nesting content.[36] Validation against schemas or EDDs is integrated, with options to check the entire document, current flow, or specific elements via the Structure > Validate command, highlighting errors in the view and logging them in the Errors console for quick resolution.[36] Additionally, the Elements catalog provides context-sensitive insertion of valid elements, streamlining content migration from unstructured to structured formats by applying rules that enforce semantic consistency.[35][37]Maker Interchange Format (MIF)
Maker Interchange Format (MIF) is a proprietary, plain-text file format developed by Adobe for representing FrameMaker documents in an ASCII-based structure, allowing for the preservation of text, graphics, formatting, and page layout elements.[38] Introduced in early versions of FrameMaker, such as version 2.0 and later, MIF was designed primarily to facilitate document portability and interchange between FrameMaker and other applications or across different versions of the software.[38] This format translates the binary .fm files into a human-readable sequence of commands that FrameMaker can interpret to recreate the original document.[39] The structure of MIF employs a hierarchical, tag-based syntax enclosed in angle brackets, where top-level statements like<MIFFile> define the overall document type and version, followed by nested substatements for specific components.[38] For instance, elements such as paragraphs are encoded with tags like <Para> containing sub-elements like <ParaLine> and <TextLine> for text content, while graphics and tables use dedicated sections such as <Graphics> or <Tbls>.[38] Catalogs for reusable items, including paragraph formats (PgfCatalog), colors (ColorCatalog), and cross-references (XRefFormats), are defined early in the file to support consistent application throughout the document.[38] This syntax supports all major FrameMaker objects, including anchored frames, footnotes, variables, and even advanced features like MathML equations and XMP metadata in later versions.[38]
MIF serves as a key mechanism for importing and exporting documents, enabling seamless exchange with external tools, databases, or older FrameMaker versions through utilities like MIFWash for batch conversions of .fm files to .mif.[39] It forms the foundation for scripting and automation via the FrameMaker Developer Kit (FDK), where developers can parse and modify MIF files programmatically to process large document sets without relying on binary formats.[38] Common applications include database publishing workflows and custom integrations that require editing document elements like text flows or conditional content.[38]
Among its advantages, MIF's human-readable nature allows for easy inspection and basic manual edits using text editors, promoting transparency in document processing.[38] It ensures version independence for fundamental documents, with backward compatibility from FrameMaker 2.0 onward, and supports cross-platform portability through device-independent pathnames.[40][38] Additionally, its tag-based format facilitates programmatic manipulation, such as batch editing for scalability in enterprise environments.[39]
However, MIF has limitations, including its verbosity for complex documents, which can result in large file sizes and increased processing time.[38] It demands precise syntax adherence, as errors in tags or nesting can lead to import failures, and it is not suited for direct end-user editing due to the technical nature of the commands.[38] Certain advanced features, such as optimized PDF elements or full diacritical support, may not translate perfectly across versions, and string lengths are capped at 255 characters for some elements.[38] Adobe advises using XML or DITA standards for contemporary structured document interchange instead of MIF.[40]
As of November 2025, MIF remains supported in Adobe FrameMaker version 17 (2022 release) for legacy compatibility and ongoing automation needs, though it plays a secondary role to modern XML-based formats in new workflows.[6][40]