Adobe Framemaker Unresolved Cross-references

Hi, I inherited a FrameMaker 9 project from another writer and now there are many Unresolved Cross-References that I am having a hard time fixing. The file (book) was on a shared drive, but there was a strange permissions issue, and I had to copy the file locally to open it. Sample script for listing unresolved references does not work. This script uses enhanced scripting support of 1.0.1 version from 8/23/2007. To be able to run this script, please update your plug-in. Adobe FrameMaker Structured Authoring The course covers everything needed to work with structured templates to produce valid documents confirming to an EDD or an SGML DTD. I inherited a FrameMaker 9 project from another writer and now there are many Unresolved Cross-References that I am having a hard time fixing. The file (book) was on a shared drive, but there was a strange permissions issue, and I had to copy the file locally to open it. Then, I renamed it. ADFM101—Adobe FrameMaker is essential This course is currently available in another city, on demand or for private classes only. Working with cross-references. Inserting cross-references; Creating/editing cross-reference formats; Fixing unresolved cross-references; Using footnotes. The all-new 64-bit Adobe Framemaker (2019 release) empowers you to create rich and immersive technical content in a jiffy, using XML/DITA authoring.

  1. Adobe Framemaker Overview
  2. Adobe Framemaker Alternative
  3. Adobe Framemaker Unresolved Cross References

Adobe® FrameMaker® 11 Classroom in a Book®, First Edition by Adobe Creative Team. • Fix unresolved cross-references • Insert footnotes • Change footnote properties. This lesson will take approximately 60 minutes. When you need a cross-reference, you specify its source and wording. Later, if page numbers or headings change when you.

Adobe FrameMaker
FrameMaker 9, editing a document in Structured Mode on Windows Vista.
Developer(s)Adobe
Stable release
Written inC/C++[1]
Operating systemWindows 7 and later[2]
TypeDocument processor, XML editor
LicenseTrialware
Websitewww.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.

In Creating Shareholder Value, Alfred Rappaport argues that management's primary responsibility is to company shareholders. First published 12 years ago, the ideas put forth by Rappaport have since become commonplace in companies around the world. The ultimate test of corporate strategy, the only reliable measure, is whether it creates economic value for shareholders. Now, in this substantially revised and updated edition of his 1986 business classic, Creating Shareholder Value, Alfred Rappaport provides managers and investors with the practical tools needed to generate superior returns. Summary of Creating Shareholder Value Alfred Rappaport, Looking for the book? We have the summary! Get the key insights in just 10 minutes. This journalistic feature popularizes Rappaport's 'Shareholder Value' (SV) theory among institutional and individual investors. The lay reader who has not majored in economics, or in corporate. Shareholder Value Creation Cumulative Shareholder Value Created = Sum of all the Past, Present and Future EVAs. Long-term value creation Alfred Rappaport prescribes ten Basic Governance Principles a company adopt for long-term shareholder value creation. 32 Principles of Shareholder Value Creation Do not manage earnings. Alfred rappaport shareholder value pdf reader. Companies profess devotion to shareholder value but rarely follow the practices that maximize it. Ten Ways to Create Shareholder Value. Alfred Rappaport offers ten basic principles to help.

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 enthusiastic users, FrameMaker never really took off in the academic market, because of the company's unwillingness to incorporate various functions (such as support of endnotes or of long footnotes split across pages), or to improve the equation editor.

Sales plummeted and brought the company to the verge of bankruptcy. After several rounds of layoffs, the company was stripped to the bare bones.

Adobe Systems acquired the product and returned the focus to the professional market. 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 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[6] and the iPhone[7] 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 was 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.

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[citation needed], 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.

Versions[edit]

FrameMaker 1.11b
Released in 1986 (Solaris and AEGIS)
FrameMaker 2.0 and 2.1
Released in 1989 (Mac version released in 1990). 2.1 was running on OSF/Motif. First version to include the Paragraph Designer, Character Designer, Cross Reference capability, and the equation editor (same version that ships with FrameMaker today). First version to support book level generated lists.
FrameMaker 3.0
Released in 1991. First Windows version available in 1992. FrameMaker 3 introduced table support, hypertext support, and improved book support. In 1992 Sun introduced FrameBuilder (FrameMaker with SGML support).
FrameMaker 4.0
Released in 1993. FrameMaker 4 introduced Change Bars, Side Head support, run in paragraph format, and improvements on the Table Designer.
FrameMaker 5.0, 5.1, 5.1.2
Version 5.1 was released in 1995, and 5.1.2 in 1996. FrameMaker 5 introduced online help, long filename support in Windows 95, OLE support, rudimentary Save to HTML, and import text by reference. This major version also introduced FrameMaker and FrameMaker+SGML (to replace FrameBuilder).
FrameMaker 5.5/5.5.6
Released in 1997 (FrameMaker 5.5.6 was released in 1998) FrameMaker 5.5 introduced drag and drop dialogs, first Japanese localized version with doublebyte support, PDFMark support (PDFMark embeds bookmarks, links, and cross-references into PDF files automatically), color libraries (DIC, Focaltone, Munsell, Pantone, Toyo and Trumatch), language is embedded into Paragraph Designer and Character Designer, and Table designer now supports sorting by row or column. FrameMaker 5.5.6 beta was also the only version to run on Linux, however there was never a final version released due to poor feedback from potential customers. It was also the last version available for IRIX.
FrameMaker 6.0
Released in 2000. FrameMaker 6.0 introduced completely rewritten userguide, book wide find/replace and spell check, introduced new and improved chapter/book numbering system, compare document tool and bundled Quadralay WebWorks Publisher.
FrameMaker 7.0
Released in 2002. FrameMaker 7.0 introduced combined SGML and unstructured version, XML application support introduced, Save As PDF fixed, tagged PDF support, improved running header/footer support, document info stored in XMP format. FrameMaker 7.0 was the last version to run on the Macintosh (OS 8/9), HP/UX and IBM AIX.
FrameMaker 7.1
Released in 2003. FrameMaker 7.1 was bundled with Distiller 6, and included more OpenType fonts and can import Quark and Pagemaker documents. FrameMaker 7.1 on Unix now uses PDFLib and no longer relies on Distiller. FrameMaker 7.1 is only released on Windows and Solaris.
FrameMaker 7.2
Released in 2005. FrameMaker 7.2 introduced multiple undo, and included an unsupported DITA (Darwin Information Typing Architecture) application pack. It is bundled with WebWorks 8, and Distiller 7 (Unix version uses PDFLib). In 2006 Adobe released officially supported Framemaker 7.2 application packs for DITA and S1000D.[8]
FrameMaker 8
Released in 2007. FrameMaker 8 introduced Unicode, Flash, 3D and built-in DITA support. A patch (8.0.1) was released during November, 2007 to fix a number of bugs and errors.
FrameMaker 9
Released in January, 2009. FrameMaker 9 contains a brand-new user interface and several productivity enhancements. New features included: full support for DITA, importing comments from PDF, enhanced WebDAV based CMS integration through native HTTP path support.[citation needed]
FrameMaker 10
Released in January, 2011. FrameMaker 10 included changes such as: DITA 1.2 support, DITA usability enhancements, author XML content, content management system support,scripting, automatically checking spelling, finding and changing overrides, using the table catalog, repeating the last operation, setting a poster: In videos, drag and drop editing, creating read/write rules, configuring the maker.ini file, text drag and drop, background colour and suppressing alerts.[9]
Framemaker 11
Released in July 2012. Framemaker 11 included native XML code view, author view, XSLT 2.0 and XPath 2.0 support, comprehensive DITA support, integration with popular content management systems, and enhanced video support.[10]
Framemaker 12
Released in January 2014. FrameMaker 12 included support for multichannel/multidevice publishing, support for MathML equations, integration with Adobe Experience Manager, simultaneous PDF-based reviews and authoring, smart catalogs, and out-of-the-box Dropbox integration.[11]
FrameMaker (2015 release) (internal version: 13)
Released 2 June 2015. FrameMaker (2015 release) included full right-to-left language support for Hebrew and Arabic, support for Thai and complex script languages, a new PDF Maker, out-of-the-box multi-channel, multi-device publishing, mobile app output for iOS and Android, and many more features.
FrameMaker (2017 release) (internal version: 14)
Released 31 January 2017. FrameMaker (2017 release) new features included support for high-resolution displays (up to 4K), bigger and better welcome screen, search for menu commands, new Project Manager, next-generation responsive HTML5 layouts, search faster with auto-complete, customizable basic HTML5 output, and a direct connector with the XML Documentation Add-on for Adobe Experience Manager, Adobe's DITA CCMS.
FrameMaker (2019 release) (internal version: 15)
Released August 22, 2018. Adobe revamped the whole technology foundation of FrameMaker, which includes a new 64-bit architecture. Large parts of the software were rewritten. Adobe also implemented the latest Adobe technologies for image processing, especially the Adobe Image Decode/Encode Library for high-quality and fast JPEG/JPEG 2000, PNG, TIFF, GIF, BMP, and Icon image formats. The new native PDF engine is based on the same PDF library other Adobe applications like InDesign, Illustrator, and PhotoShop are using. It supports PDF/X, fully accessible 'tagged PDFs', as well as password-protected (encrypted) PDFs. In addition to that, Adobe introduced interactive real-time progress bars, support for image transparency, SharePoint 2016 support, support for interactive HTML5-based dialogs for plug-ins, the latest ExtendScript engine, one-click (proportional) image resizing, enhancements for DITA authoring, the world's first visual DITA customization (constraining) wizard, as well as support for the latest DITA Open Toolkit 3.x, and XSLT 3.0 and XPATH 3.0. FrameMaker also comes with a full license for Saxon Enterprise Edition and is the first desktop application to support Google's WebP image format. Adobe also went into an agreement with DUDEN to support the latest spell checking and hyphenation methods for the German language (German, Swiss-German and Austrian German).

See also[edit]

  • Maker Interchange Format (MIF)

References[edit]

  1. ^Lextrait, Vincent (January 2010). 'The Programming Languages Beacon, v10.0'. Retrieved 2010-03-14.
  2. ^'FrameMaker system requirements'. August 2018. Retrieved 2019-03-21.
  3. ^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.
  4. ^http://www.macworld.com/article/1030037/framemaker.html
  5. ^'Rumors Of FrameMaker's Death Have Been Greatly Exaggerated [sic]'. The Mac Observer. 2001-02-09. Retrieved 2007-05-26.
  6. ^John Gruber 'Apple still using Framemaker in Classic', Daring Fireball
  7. ^Michael Tsai (2007-05-01). 'Old Meets New'.
  8. ^'FrameMaker 7.2 Application Packs for DITA and S1000D'. Adobe. Archived from the original on 10 May 2007. Retrieved 2007-05-26.
  9. ^'FrameMaker10 and FrameMaker Server 10 launched today!'. Adobe. Retrieved 2011-01-11.
  10. ^'FrameMaker 11 and FrameMaker Publishing Server 11 are here!'. Adobe. Retrieved 2012-07-25.
  11. ^'FrameMaker 12 is here!'. Adobe. Archived from the original on 2014-01-18. Retrieved 2014-01-14.

External links[edit]

  • Blog post about FrameMaker (2019 release)
  • Element Descriptions in Structured FrameMaker 10 Using Element Descriptions to cut down writers’ training costs and efforts.
  • FrameUsers.com FrameMaker users' largest online reference site and community
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Adobe_FrameMaker&oldid=888812503'

The following is a list of issues resolved in FrameMaker (2015 release) and subsequent patch releases.

Check the FrameMaker forum for solutions, workarounds, or any late-breaking information.

Note:Most issues listed below are relevant to both FrameMaker and FrameMaker XML Author. Issues relevant to only FrameMaker are labeled FM Only.

  1. Responsive HTML5 output is not optimized for Google search, which makes the output unsearchable.
    (Ref - 4190911)
  2. If there are a large number of fonts (1800+) installed on the system, FrameMaker fails to apply correct fonts that appear lower down in the font list.
    (Ref - 4052709)
  3. In some cases, if an SVG file contains open type fonts, it does not render correctly in FrameMaker and output PDF.
    (Ref - 4109022)
  4. In Windows 10, FrameMaker crashes while embedding fonts in EPUB output.
    (Ref - 4145336)
  5. Selecting the option Use Only ASCII Characters in Generated Filenames in Publishing Settings dialog does not work as expected.
    (Ref - 4187889)
  6. Incorrect cross-reference being generated if the source type selected is paragraph.
    (Ref - 4132389)
  7. FrameMaker console window displays publishing related error message on launch.
    (Ref - 4175428)
  8. In some cases, generating a PDF document takes too long.
    (Ref - 4177991)
  9. FrameMaker installer installs some unsupported software and OpenSSL files.
    (Ref - 4184193)
  10. Generating PDF output through FrameMaker Publishing Server fails if the file path is too long.
    (Ref - 4185941)
  11. In some cases, if there are a large number of nested cross-references in a DITA map file, FrameMaker takes longer time to load the file.
    (Ref - 4191901)
  12. Performance issue noticed while uploading files through CMS Connector for AEM.
    (Ref - 4192529)
  13. While checking out files from AEM, cached dependent files on the local system are not refreshed even if updated files are available on the AEM server.
    (Ref - 4192520)
  14. Resources dependency calculation should not be done while uploading a folder on AEM server hosting XML Add-on.
    (Ref - 4192517)

New Review Comments pod to track and manage review comments

You can now sync, view, and reply to review comments received on a topic using the new Review Comments pod in FrameMaker. An author initiates a review task for a single topic or multiple topics from the Adobe Experience Manager (AEM) interface. Multiple reviewers can review the topics and provide review comments. They can also view comments given by other reviewers in real-time and post replies. The Review Comments pod in FrameMaker gives a consolidated list of all review comments to the author to fix. From the Review Comments pod, you can:

  • Filter comments by choosing a specific reviewer or all reviewers.
  • Mark the status for each comment. You can choose from None, Accepted, or Rejected.
  • See all comments by clicking Show All comments.
  • Post a reply for a comment.

Note: The Review Comments pod shows comments only for the topics shared for review. If you have shared a DITA map for review, you can only view comments on the DITA map in the XML Documentation Add-on for Adobe Experience Manager interface.

Support for HTTPS

HTTPS uses Secured Socket Layer (SSL) to exchange information between a client and a server. You can now use HTTPS to establish a connection between FrameMaker and AEM.

Integrated search with XML Documentation Add-on for AEM

FrameMaker’s repository search is now seamlessly integrated with AEM. If you use the repository search feature in FrameMaker, the search is performed in the DITA content within the AEM repository. For this feature to work, your AEM server must have the XML Documentation Add-on installed. The results are displayed in the Repository Search pod in FrameMaker. Using the Repository Search pod, you can perform regular file functions on the search results, such as open or explore a topic.

The repository search functionality also comes with an added attribute search feature. You can search the DITA content by text, and also by an element’s attribute in FrameMaker. Perform attribute search using appropriate values in Attribute name = Value format.

New Adobe Experience Manager options in the Preferences dialog

The Preferences dialog box is updated to include configurable options for Adobe Experience Manager connector. You can use these options to set up file check-in and check-out preferences for AEM. Go to Edit > Preferences > CMS > Adobe Experience Manager to see the updated preferences.

Connection Manager dialog enhancements

- Alphabetically organized list of connectors

The list of connectors in the Connection Manager dialog is organized alphabetically. You can now easily look for the connector while setting up a connection and choose the one that is required.

- Option to browse and update the location for Local Folder

FrameMaker creates a local download folder that acts as a temporary location on your machine. You can download files from AEM into this Local Folder. The default location of the Local Folder is C:Users<username>Documents. However, you can change this location by clicking the Browse button given alongside the Local Folder field.

- Option to save and remember connection password

You have an option to save the connection password while setting up a new connection. Enter the connection password and select the Save Password option. FrameMaker remembers the password when you reconnect after your first successful attempt.

Repository Manager window enhancements

- New Review Comments pod launch icon

Repository Manager has an enhanced user experience. It includes a new Review Comments pod icon. Click this icon to quickly launch the Review Comments pod that facilitates easy management of the review comments.

- Repository Manager context menu enhancements

After you set up a connection with a repository, the contents are organized in the form of files and folders in the Repository Manager window. You can perform a set of functions on these files and folders. The list of these functions has been enhanced and reorganized to provide seamless experience.

For more information about the functions that you can perform, see Working with files section in the Content Management Systems chapter of the Adobe FrameMaker (2015 release) User Guide.

Organized list of items in the Format menu

Earlier when you clicked Format > Fonts (Characters or Paragraphs), a list of fonts installed on your system was displayed in a multi-column layout. If you had a long list of fonts on your system, the list would cover up the entire FrameMaker user interface. Now, when you click Format > Fonts (Characters or Paragraphs), the list of items is neatly organized in a single column. If the list is long, you can use the up and down scroll icons to easily traverse the list of items.

  1. When connected to the AEM server, if the file has unresolved cross-references or text insets, it fails to check-in.
    (Ref - 4166507)
  2. When setting up a Fm-AEM connection over VPN, the connection fails.
    (Ref - 4160478)
  3. While creating or updating a stand-alone TOC for an unstructured document in structured mode, the information for generating the TOC file is lost. As a result, an empty file is generated. This is also applicable for generating a list of figures, tables, and paragraphs.
    (Ref - 4155655)
  4. When you try to import or export an EDD file for an Arabic document, the settings are not replicated correctly.
    (Ref - 4152183)
  5. In FrameMaker, if you check out, edit, and save the file and then try to check in the same file, you are prompted to save the file again.
    (Ref - 4158932)

Host Responsive HTML5 content on Adobe RoboHelp Server 10

You can publish Responsive HTML5 output from FrameMaker (2015 release) Update 3.1 and host it directly on RoboHelp Server 10. Your content is rendered seamlessly on multitude of devices, including mobile devices. With the support for dynamic content filters in HTML5, your end users can easily access personalized content.

Enhanced Responsive HTML5 publishing process

There are two new enhancements in the publishing process of Responsive HTML5 output. Firstly, all images used in your book are now saved in a single assets folder in the published output. Secondly, you have an option to merge styles across documents in your book into a single CSS file. This reduces the overall size and maintenance overhead of your project.

User interface enhancements

The following enhancements have been made in the latest user interface:

  • Field and button string changes

Minor string changes have been done to improve user experience. The affected dialogs where string changes have been made can be found at the following locations in the main menu:

- Special > Table of Contents > Create Standalone TOC

- Special > Table of Contents > Create Mini TOC

- Special > List Of > all dialogs

- Special > Standard Index

- Special > Index Of > all dialogs

If the current focus is on the Book window, then the above-mentioned dialogs can be accessed from the Add menu (in place of the Special menu).

  • Paragraph symbol removed from tag names

Tag names displayed in the following dialogs will no longer display the redundant paragraph symbol '¶' prefixed to the names:

Direttore Amministrazione e Finanza. Zircosil (Italy) Srl. Direttore Amministrazione e Finanza - Tetra Pak Carta Spa Gruppo TETRA PAK INTERNATIONAL (Svezia): leader mondiale nella produzione e commercializzazione di contenitori asettici per liquidi alimentari. 2 vendor due diligence nell’ambito del processo di Merge. Mercati e finanza. Nuova Cassa di Risparmio di Ferrara S.p.A. Known as Nuova Carife [New Carife] in short, was an Italian bank, based in Ferrara, Emilia-Romagna.Nuova Carife was founded on 22 November 2015 as a good bank that spin off from the original Cassa di Risparmio di Ferrara S.p.A. The old Carife was under administration from 2013 and 2015, and now being liquidated as a bad bank. In Amministrazione, Finanza e Controllo Tesi di Laurea Sustainability Reporting and its Impact on Corporate. Sort of merge between the ordinary financial statement and the modern sustainability reporting. Environmental consumers i.e. Corporations as a consequence of a novel stakeholders.

- Special > Table of Contents > Create Standalone TOC

- Special > Table of Contents > Create Mini TOC

- Special > List Of > all dialogs

  1. On relaunching the Help window, the dimensions set earlier are not retained.
    Ref# 4107829
  1. Working with Conditional Tags pod under various scenarios causes FrameMaker to crash.
    Ref# 4092122
  1. When publishing output for documents that use left-to-right layout, the layout-rtl.css file is also generated in the output folder.
    Ref# 4113157
  1. A few extra .fpj files are getting generated in the Preview folder of the published output.
    Ref# 4114869

Adobe Framemaker Overview

  1. In the published Responsive HTML5 output, images imported from reference page are saved under the topic folder instead of the assets folder.
    Ref# 4123826
  1. FrameMaker crashes while publishing a document if it is split based on styles, in such a way, that same name TOC pages are generated.
    Ref# 4113191
  1. For some fonts, FrameMaker does not display standard ligatures correctly.
    Ref# 4093102
  1. In FrameMaker ExtendScript and FDK, the value for constant Constants.FF_FIND_USE_REGEX is not mapped correctly.
    Ref# 4102169
  1. XMP metadata contains incorrect version number of FrameMaker.
    Ref# 4102879
  1. Frame crashes on pasting text frame into a graphic inset.
    Ref# 4111649
  1. If there is a deeply nested book structure, synchronization between the Book Window and Structure View is lost.
    Ref# 4059503
  1. From a Ditamap, opening a file that contains large number of cross-references causes FrameMaker to slow down or throw out of memory error.
    Ref# 4103726
  1. Random FrameMaker crash issues noticed if conditions are applied on a mini TOC.
    Ref# 4106196 (FM only)

Upload articles to Adobe DPS

Now generate Adobe DPS output for your FrameMaker documentation and upload the generated articles to Adobe DPS. Use your Adobe account to sign into the Adobe Digital Publishing Solution and create your DPS projects. Ensure that you are using FrameMaker on the same Adobe account. In the Publish Settings dialog, select your Adobe account and the DPS project. When you run the publish procedure, the articles are generated in your output folder and uploaded to the selected project in your DPS account.

Support for XML sitemap in the Responsive HTML5 output

A sitemap helps search engines to index your web pages and make your website SEO-friendly. FrameMaker now gives you an option to create the XML sitemap file for your Responsive HTML5 outputs. In the absence of this feature, you would either use a third-party tool to create a sitemap or manually create one.

The sitemap generation process is seamless as you simply select an option in the Responsive HTML5 output settings to generate the sitemap for your book or ditamap. The sitemap contains the references of your web pages, the base URL of your website where you would host the published output, and the frequency at which you intend to update your pages. As it is an XML file based on the standardized XML sitemap protocol, you can easily change the sitemap file as and when needed.

  1. Working with Conditional Tags pod under various scenarios causes FrameMaker to crash.
    Ref# 4035109, 4038332, 4035102
  2. Under various scenarios, FrameMaker search does not work as expected in a conditionalized table.
    Ref# 4033948, 4033979
  3. If a table contains conditional rows and column, user opens the Find/Change pod, searches for the conditionalized text, and clicks the Change All button with nothing specified in the Change field, FrameMaker freezes.
    Ref# 4033942
  4. Arabic ligatures break and the base line shifts before FATHATAN and ALEF in the PDF output.
    Ref# 4014238
  5. If Arabic text with pronunciation or phonetic symbols is published to PDF, then the text is not correctly aligned to the baseline.
    Ref# 4024151
  6. Random FrameMaker freeze issue noticed while generating Microsoft HTML Help output of a Farsi document.
    Ref# 4020560
  7. Typing Japanese characters at the end of a line where the text flows to the next line causes FrameMaker to crash.
    Ref# 4023843
  8. Checking out a single file without dependent files and then editing the checked-out file results in the checkout of all dependent files.
    Ref# 4037847
  9. Transformation messages are displayed in the console window even for successful XSLT transformations.
    Ref# 4063761
  10. FrameMaker crashes while importing some JPEG files.
    Ref# 4068641
  11. FrameMaker fails to insert MathML equation in unstructured mode.
    Ref# 4070561
  12. Markers pod is not available in the Review workspace.
    Ref# 4051475
  13. In Japanese and German versions of FrameMaker, user sees an error message on checking in a file into the AEM server.
    Ref# 4037107, 4036921
  14. FrameMaker crashes while replacing any UTF2 character.
    Ref# 4030642
  15. For a FrameMaker .book, the paginated topics do not appear in the TOC even if the 'Add Paginated Topics to TOC' option is ON and the 'Merge Topics with no Content' option is OFF.
    Ref# # 4063245
  16. In a Responsive HTML5 output, if the metadata contains special characters, the special characters are lost in the final output.
    Ref# 4058046
  17. WebHelp output does not render correctly on MS Edge browser. For example, if a user performs a search in the output and then returns to the TOC, the TOC disappears.
    Ref# 4051256
  18. Fix for XSS in Responsive HTML5 output.
    Ref# 3983976
  19. In the Style mapping > Table tab, user cannot provide percentage values for table height and width. If a user provides a percentage value, an error message indicates 'Valid values include measurements in px, pt, pc, cm, em, mm, in.'
    Ref# 3757834
  20. WebHelp/Responsive output will show title, created using macros, in browser window.
    Ref# 3670135

Windows 10 support
FrameMaker 2015 is supported on the Windows 10 operating system.

Support for Adobe Experience Manager 6.1
FrameMaker 2015 supports the latest version of Adobe Experience Manager 6.1.

Simplified XML
Simplified XML feature has been enhanced to support DITA 1.3 documents. With the addition of new functionality, it is easier to convert paragraphs to list and list to paragraph, add definition list and entry elements, apply code formatting, and navigate to the end of the form element.

Support for Thai and Farsi languages
Thai and Farsi languages support has been added in FrameMaker. The RTL authoring and publishing feature has been enhanced to support the Farsi language.

MathML support for DITA 1.3
MathML equations can be inserted in DITA 1.3 document types. Quick Element Toolbar in Simplified XML view for DITA 1.3 documents has also been enhanced to include the MathML container button that allows insertion of MathML equations.

Quick Element Toolbar for DITA 1.3
QET is available in WYSIWYG view for DITA 1.3 document types (topic, task, concept, reference, and troubleshooting).

Quick Element Toolbar for DITA 1.2 reference type documents
QET has been introduced for DITA 1.2 reference type documents in WYSIWYG View and Simplified XML/Author View.

XSLT enhancements
FrameMaker’s XSLT architecture has been enhanced to use SAXON as the default XSLT processor. Your structured application can be configured to used different processors for handling pre-processing, post-processing, and smart pasting operations.

Support for DITA Open Toolkit 2.1
Support for DITA Open Toolkit (DITA-OT) has been upgraded from 1.8 to 2.1 library.

Mini TOC
The mini TOC has been enhanced to support book level updates. You can update the mini TOC at the book level by selecting the update Mini TOC option in the Update Book dialog box.

Smart filter
The Paragraph Designer dialog box has been enhanced to support Smart filter in the Next Paragraph Tag list, and the Object Designer dialog box been enhanced to support Smart filtering in the Object Style list.

Table and image handling enhancements
Table resizing and table text or image rotation options are available in the main and context menus’ in the Structured FrameMaker's Author View and FrameMaker XML Author's WYSIWYG and Author View. Also, If you are working in the Simplified XML view in Structured FrameMaker or FrameMaker XML Author, you can resize table column through the main and context menus.

DitaExchange - FrameMaker connector
In addition to the existing AEM, Documentum, and SharePoint connectors, FrameMaker also provides support for the DitaExchange connector.

Auto-generate IDs in Structured document
Now you can define rules that ensure that FrameMaker auto-generate IDs for any element in a structure document. You can also define the attribute to which you want FrameMaker to assign the ID.

Enable browse sequences in Microsoft HTML output (CHM)
A new option has been added to enable browse sequences in Microsoft HTML output.

Layout icons optimized for high-resolution Retina display
Icons in the Responsive HTML5 layouts have been optimized for high-resolution Retina display. The icons in Azure and Charcoal gray layouts appear sharp and clear on high-resolution devices.

Publishing to Digital Publishing Solution
FrameMaker’s multi-channel publishing feature has been enhanced to provide the option to publish your documents to the Adobe Digital Publishing Solution (DPS).

  1. For huge FrameMaker book that contains 500 or more pages, images at random places are shown as gray boxes.
    Ref# 3999717
  2. Users are unable to create right-to-left documents by using the right-to-left template provided with FrameMaker.
    Ref# 4008126
  3. In right-to-left documents, the registration mark goes out of page on publishing to PDF.
    Ref# 4015615
  4. FrameMaker crashes if a user tries to search for some complex word in the backward direction.
    Ref# 3991181
  5. A structured document containing text that Filter by Attribute or Conditional Text hides takes longer time to save as PDF.
    Ref# 3983610 - Fm Only
  6. FrameMaker sometimes freezes while editing or double-clicking a conditional tag in the Conditional Tags pod.
    Ref# 4018368 - Fm Only
  7. Deleting any text frame along with grouped objects and then trying to undo the delete operation causes FrameMaker to crash.
    Ref# 3980535 - Fm Only
  8. Using FrameMaker on Windows 8.1 with screen resolution of 1900x1200 or more results in small and overlapping icons.
    Ref# 3955253
  9. A new table row is not added on pressing the Tab key on tables where the title is set as Below Table.
    Ref# 3992365 - Fm Only
  10. Save as PDF picks the binding property from the first document in the book rather than the first non-generated document.
    Ref# 3980802 - Fm Only
  11. FrameMaker generates empty topics in the output even for empty topics that does not have any content. An option should be provided to not create a separate topic in such cases.
    Ref# 4020126
  12. The conditional indicators applied in FrameMaker document are visible in the generated output.
    Ref# 4017918 - Fm Only
  13. FrameMaker crashes if Output style field (Publish pod > Responsive HTML5 > Edit Settings > Style mapping tab) is blank in Responsive HTML5 publish settings.
    Ref# 3989415 - Fm Only
  14. FrameMaker does not allow usage of special characters in the display name of dynamic content filter criteria.
    Ref# 3987013 - Fm Only
  15. Keyboard does not close after pressing ‘Enter’ key, when viewing Responsive HTML5 Help on some mobile devices.
    Ref# 3985736 - Fm Only
  16. FrameMaker crashes when a file containing an inset with scalar vector graphic (SVG) is published in Responsive HTML5 layout.
    Ref# 3984234 - Fm Only
  17. When viewing glossary item definition (in mobile app output) on an iOS device, the user is unable to navigate back to the Help content as full screen is occupied with its context. The glossary definition link now opens in a pop-up allowing the user to navigate back to the Help content.
    Ref# 3974809 - Fm Only
  1. A new ID is not assigned to a DITA topic, if the topic is copied and pasted
    Ref# 1912850
  2. Delete() function does not work for objects in ExtendScript
    Ref# 2969854
  3. Text in SVG graphics is not searchable in the PDF generated from FramerMaker
    Ref# 3546318
  4. Format-change lists are not overwritten while importing element definition from a structured document
    Ref# 3568537
  5. If a user selects a group and opens the Object Properties dialog by choosing Graphics > Object Properties, some properties are reset
    Ref# 3590719
  6. MathML equations are carried over to PDF as bitmaps. This causes loss of fidelity and does not call a read to search for the equation in the PDF
    Ref# 3590985
  7. If an inline element starts on a new line in a DITA file, the space typically that the previous CR created is lost.
    Ref# 3674785
  8. EDD BackgroundColor element corrupts the EDD in a MIF round trip
    Ref# 3686735
  9. FrameMaker crashes if a file contains postscript flow
    Ref# 3693332
  10. A command at the end of a submenu that customui.cfg generated does not appear
    Ref# 3696402
  11. Track Changes does not function correctly if a user changes the status (Enable/Disable) of Track Changes multiple times
    Ref# 3700628
  12. If a nonzero length UserString entry is added to a Table and the FDK / ESTK Publish component is used to produce output, FrameMaker crashes.
    Ref# 3707947
  13. Invalid characters can be seen in the Code view if a user copies and pastes multiple paragraphs from PDF/Word documents to XML documents in WYSIWYG view and then switches to the Code view
    Ref# 3708356
  14. If a user updates a book, the sub/super-script formatting from cross-references is removed
    Ref# 3712513
  15. No actualization of cross references when chapters in a FrameMaker book are renamed.
    Ref# 3728066
  16. If a user saves a file with Tag view ON, then closes and reopens the file, FrameMaker crashes.
    Ref# 3756920
  17. FrameMaker should understand ampersand (&) character in entity declaration
    Ref# 3762775
  18. FM crashes when user drags-and-drops an image from a Word document to a FrameMaker document or across sessions of FrameMaker
    Ref# 3775602
  19. FrameMaker crashes if a user drags-and-drops a WMF image across sessions of FrameMaker
    Ref# 3775619
  20. Importing some JPEG files causes FrameMaker to crash
    Ref# 3781681
  21. If a user updates a text inset containing conditional text, text that is conditionally hidden also displays.
    Ref# 3783041
  22. All Condition tags are not applied correctly if a user applies tags by selecting chapters at the book level
    Ref# 3797475
  23. Chapter hyperlinks are broken in a PDF after upgrading FrameMaker 11 document to FrameMaker 12 or beyond
    Ref# 3801191
  24. If a user cuts and pastes a Linked Microsoft Excel Worksheet Object (OLE), FrameMaker crashes.
    Ref# 3822444
  25. Document compare fails for structured documents
    Ref# 3829146
  26. Entity search paths that XSLT doesn't use preprocess
    Ref# 3836398
  27. FrameMaker crashes when a user open an .mif file when the FDK client which closes the file also generates post open notification.
    Ref# 3838861
  28. FrameMaker freezes while opening an XML document of on a subsequent book update
    Ref# 3846529
  29. If a user create a CMYK PDF, some images and table are dropped.
    Ref# 3857184
  30. If a file contains more than 256 operators in a Boolean condition expression, FrameMaker hangs
    Ref# 3857984
  31. Using the Graphics > Create Link Table to Graphic… option to create links to the parts of a 3D Model, does not produce the expected result
    Ref# 3915844
  32. FrameMaker crashes if a user pastes a long string in the Autonumbering tag of the Paragraph Designer
    Ref# 3930900
  33. User is unable to change the element type of a cross-reference from the Cross-Reference dialog box
    Ref# 3940182
  34. The following FDK command used to clear console pod doesn't work: F_ApiSetString(0, 0, FP_FMConsoleString, (StringT)'-1');
    Ref# 3943538
  35. The size and position of custom dialogs that an FDK client provides are stored in the ModalDialogPosition.ini file. The first time a dialog is displayed its size is stored in this file. If the dialog size is modified in the source, it always displays at the original size unless this file is deleted or the entry in the file is removed. There is no way for the FDK client to control this other than to tell the user to manually edit or delete the file.
    Ref# 3952288

The following crashes were fixed in the Conditional Text area of FrameMaker. These are not generic crashes that were found for all cases of each of the scenarios described below. These crashes were reported / found in specific use cases and for specific documents that users provide.

  1. FrameMaker crashes if a user opens the files in a DITA map
    Ref# 3166900
  2. FrameMaker crashes if a user updates a book (containing an invalid color ID) of book
    Ref# 3762801
  3. FrameMaker crashes if a user updates a book containing conditional text
    Ref# 3771500
  4. FrameMaker crashes if a user updates a book (containing an invalid color ID) of book
    Ref# 3792667

Adobe Framemaker Alternative

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Adobe Framemaker Unresolved Cross References

Legal Notices Online Privacy Policy