The Adobe FrameMaker 2017 release has been one of the most successful releases in the history of FrameMaker. The completely re-thought and re-designed user interface with many smaller and bigger improvements, the new HTML5 based and customizable “Welcome Screen”, compatibility with high-res / high-dpi screens up to 4K, the smart command search, better image handling, the new project manager, enhanced conditional tags, enhanced DITA authoring and management, omnichannel publishing and brand-new modern and Section 508 compliant Responsive HTML5 outputs with the new predictive auto-complete search bar and much more got overwhelmingly positive reviews.
And we were very active since the launch in January. We got a lot of valuable feedback and wishes from you. We are always listening and willing to walk that extra mile to incorporate your feedback. Today, we’re happy to announce the availability of the first update to 2017 release of FrameMaker.
In this important update, we have incorporated a number of enhancements and ironed out a lot of smaller glitches. I would like to extend big thanks to all those who’ve contributed by reporting issues and helping us improve the product. In this post, you can find the important updates and fixes that we made in 2017 release of FrameMaker (Update 1). Complete list is available here.
What’s new and better
Following the list of enhancements and issues fixed in the 2017 release of FrameMaker (Update 1).
In this post:
Many of you told us that you prefer to dock the Graphics Toolbar horizontally. In 2017 release, only vertical docking was possible. So we brought that back: Dock the Graphics toolbar with Update 1 vertically or horizontally just as you prefer. Also, we ironed out a few UI glitches in the Graphics Toolbar
We made more enhancements to the Paragraph Designer! Now you can rename existing styles very easy with this nice new “Rename” button. And there’s more intelligence in it: When you just change a style’s properties, you see an “Update Style” button. When you type in changes in a style name, the “Update Style” button changes to “Create Style” and the “Rename” button becomes active. The decision to rename the current style or to create a completely new one is now just a mouse click away!
We understand that many of you do not only author and publish in their native language, but need to edit translated variants of their documents as well. And FrameMaker supports spell checking and hyphenation for up to 40 languages out of the box. But FrameMaker’s typography engine is even more powerful than that! In fact so powerful, that you can author and edit virtually any (!) language of this beautiful planet, even if we do not provide spell checkers and hyphenation engines for them. With FrameMaker 2017 you can even edit languages like አማርኛ (Amharic), ܐܬܘܪܝܐ (Assyrian), မြန်မာစ (Burmese), हिन्दी (Hindi), বাংলা (Bengali), తెలుగు (Telugu), मराठी (Marathi), தமிழ் (Tamil) and all others (not even your browser might be able to show them here!). You have never heard of “ᓀᐦᐃᓇᐍᐏᐣ (Swampy Cree)“? And you will probably not publish your technical documentation in this language? Okay. But it’s a good feeling you could do it with FrameMaker if you ever need to, isn’t it?
So. Now, you got this Arabic translation back from your translator. But which language do you assign now in FrameMaker? فارسی? or was it العربية? Now, in FrameMaker 2017 Update 1 you can simply select “Farsi” and “Arabic” from the language drop-down. And same for other language names with non-western characters that were in the language drop-down in their native language names.
Of course we also did not forget the Character Designer. And also not the Preferences dialog where you can specify which spellchecker and hypenation engine you want to use (depending on the language you can select between Hunspell, Proximity and Winsoft).
Oh, tables. Yes, we heard you. Many of you asked us to improve the Sort Table dialog because it was hard to work with it. In Update 1 for FrameMaker 2017, we have completely redesigned the dialog to make it much easier to use.
Adding and editing multiple Variables in one go is easier now. In 2017 release, creation and editing were done using a modal dialog which was better suited for a one-time action. This change is now rolled back as users prefer to have it open while adding and editing multiple variables in one go.
Adding Page Breaks now also happens in a pod which remains open in order to take multiple actions. In 2017 release, this was transformed to a modal dialog which would close after every action.
A Conditional Tag option is now added to the ‘Insert’ menu in unstructured mode. This change is part of menu reorganization where a new “Insert” menu is added to make insertion of common items easier.
You didn’t like that the ‘Conditional Tag’ pod had a minimum height that was unnecessarily big? We neither. That’s why we made the height of the Conditional Text pod completely adjustable now. The constraint on minimum height is removed and the last entry in the list is not truncated anymore.
If you are doing a lot of Structured Template development, you will love to hear that we made the Show Element Context dialog re-sizable now.
We understand that there are many FrameMaker users who do not work with XML. For those of you who work in the “classic” FrameMaker mode without XML, we have customized the welcome screen in the way, that all the DITA, DocBook and other XML options are not visible. See the difference between classic and structured FrameMaker in the Welcome Screen in this animation:
Customize your Welcome Screen! Those of you who have already started to customize FrameMaker 2017’s new Welcome Screen will love to hear that: We made it easier now to customize the Welcome Screen or even create your completely new own Welcome Screen.
We have added the Welcome Screen to
%appdata%\Adobe\FrameMaker\14\resources\welcomeScreen\, so that you can customize the
welcome.htmlthere. Makes it more easy to edit and more “update-save” and avoids the need to edit the
welcome.htmlin FrameMaker’s installation folder. We have also updated the User Guide with this info.
The File Open dialog lists all supported file formats now including XML and DITA formats. In earlier versions, if you open a file using
File > Openor Ctrl+o, the dialog lists only unstructured documents in ‘Files of type’ drop-down.
While working on extended desktops, the Command Search (F7) pop-up appears as expected on the desired monitor now.
Saving a document in View Only mode is now made possible. This option was removed from the 2017 release.
Dynamic Content Filters work correctly on indexes in Responsive HTML5 output. Earlier, indexes would continue to show even after applying filters.
We love Animated GIFs! That’s why we took care that they are now rendered correctly in Responsive HTML5 output.
All Responsive HTML5 layouts are now Section 508 compliant.
On clicking a link of responsive HTML5 output from Google search results, the content is now shown in the full layout. Earlier, the page would open without the layout and user had to click on “Show” to get back to entire help system with TOC and layout.
When you update from FrameMaker 2015 you can now import your customized Screen Layout
.slzfile and your customizations are migrated properly.
When pulblishiing to the new “Basic HTML”, the new slim XHTML 1.0 Transitional output format, a slim
index.htmlis created, that contains links to all HTML files included in the output. This is especially useful if you publish multiple files from a book.
FrameMaker Object Model version number appears correctly now in ExtendScript Toolkit.
In the FrameMaker 2017 release we made inserting images into your document much easier and faster with the new
Insert > Imagemenu. In previous versions you had to go a complicated route through
File > Import > File. We have enhanced this and now you can also insert images in CGM format by using the
Insert > Imagemenu option.
We have updated FrameMaker’s internal Book MIF Parser for full Unicode compatibility in Windows path and file names. This makes it more easy for developpers to created automated processes based on Book MIFs.
Redundant alert messages are no longer shown on removing structure from a document. Prior to this, two alerts were shown that required more clicks.
We have fixed a couple of crashes reported while using advance search in Repository Manager.
The Apache Xerces™ C++ XML Parser is an Open Source Software used for advanced XML parsing. The Xerces DLLs used in FrameMaker are updated to the latest version (3.1.4). This improves FrameMaker’s XML performance in many fields and fixes several bugs.
In addition we have fixed a couple of crashes reported while using advance search in Repository Manager and while saving FM files in older formats. A good number of issues related to localization (truncated strings or translation errors) are fixed as well.
You can also download the FrameMaker (2017 release) Update 1 Readme PDF here.
How to get Update 1 for FrameMaker (2017 release)
Getting the update is as easy. Just select
> Help > Updates from FrameMaker’s main menu to fire up the Adobe Update Manager (AUM) to download and install the update.
Want to download the update to deploy it to all your FrameMaker installations without downloading it on every machine? We understand this. That’s why you can find all update packages for download also in the Adobe FrameMaker Support Center.
After the update, the FrameMaker version will be 188.8.131.526. That’s good to know, isn’t it?
Found a bug? Want to suggest an improvement? Let us know!
You found a bug? You have an idea? You want to get something improved in the product?
There’s a channel for that: We call it “Adobe Tracker.” Adobe Tracker is your place to go when you find a bug and want to report it to us so that we can fix it in the next release. You can also file in your feature requests, ideas, requests for improvements. It’s very easy to do and the reports go directly into our systems, and our product managers, engineers, and support people have direct access to it.
Before you file a bug report or idea, you might want to check, if someone else has done it already. You can search through the database here. In case you find something fitting, you can add comments to the existing bug and you can also “vote” for this bug or feature request. And the more people vote for a feature … You get the idea.