This reinvigorated rumors surfacing in 2001 that product development and support for FrameMaker were being wound down. Adobe denied these rumors in 2001, 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) in June 2015.

Remapping TrueType Fonts in Framemaker 9.0 maker.ini jmwashrae. Dec 20, 2010. Default Adobe PDF presets, including (if I remember right) even the Standard. RoboHelp 2019 – Update 9 (September 2019) 02 Adobe & Partner Translating Adobe FrameMaker Documents with the Across Language Server 03 FrameMaker 2019 Update 4 (August 2019) 04 Adobe & Partner SQUIDDS FINALYSER for Adobe FrameMaker 05 RoboHelp 2019 – Update 8 (July 2019); Product Pages.

Adobe FrameMaker
Stable release
FrameMaker 9, editing a document in Structured Mode on Windows Vista.
Developer(s)	Adobe
Written in	C/C++^[1]
Operating system	Windows 7 and later^[2]
Type	Document processor, XML editor
License	Trialware
Website	www.adobe.com/products/framemaker

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 1995 when Adobe purchased Frame Technology Corp.^[3] Adobe added SGML support, which eventually morphed into today's XML support. In April 2004, Adobe stopped supporting FrameMaker for the Macintosh.^[4]

This reinvigorated rumors surfacing in 2001 that product development and support for FrameMaker were being wound down. Adobe denied these rumors in 2001,^[5] 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) in June 2015, FrameMaker 2017 in January 2017, and FrameMaker 2019 in August 2018.

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 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. The purpose of MIF is to represent FrameMaker documents in a relatively simple, ASCII-based format, which can be produced or understood by other software systems and also by humans. 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]

While working on his master's degree in astrophysics at Columbia University, Charles 'Nick' Corfield, a mathematician alumnus of the University of Cambridge, decided to write a WYSIWYGdocument editor on a Sun-2workstation. He got the idea from his college roommate at Columbia, Ben Meiry, who went to work at Sun Microsystems as a technical consultant and writer, and saw that there was a market for a powerful and flexible desktop publishing (DTP) product for the professional market.

The only substantial DTP product at the time of FrameMaker's conception was Interleaf, which also ran on Sun workstations in 1981.^{[citation needed]} Meiry saw an opportunity for a product to compete with Interleaf, enlisted Corfield to program it, and assisted him in acquiring the hardware, software, and technical connections to get him going in his Columbia University dorm room (where Corfield was still finishing his degree).

Corfield programmed his algorithms quickly. After only a few months, Corfield had completed a functional prototype of FrameMaker. The prototype caught the eyes 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 as demoware for their computers, and hence, the primitive FrameMaker received plenty of exposure in the Unix workstation arena.

Steve Kirsch saw the demo and realized the potential of the product. Kirsch used the money he earned from Mouse Systems to fund a startup company, Frame Technology Corp., to commercialize the software.

Corfield chose to sue Meiry for release of rights to the software so they could more easily obtain additional investment capital with Kirsch. Meiry had little means to fight a lengthy and expensive lawsuit with Corfield and his new business partners, and he chose to release his rights to FrameMaker and move on.

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 and IBM's AIX operating systems.

Sun Microsystems and AT&T were promoting the OPEN LOOKGUI 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, 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 1000-page manual was too cumbersome and difficult for an average home user to type a one-page letter. And despite some initially enthusiast

Adobe Framemaker 9