Acrolinx for MadCap Flare - Version 4.7 SR1 (3 August 2016)
This is a minor service release but it also includes a few improvements and updates.
We've improved the messages for the batch checking feature
Sometimes, our messages in the batch checking feature weren't so easy to understand. We've improved the messages so that it's easier to understand why a certain document couldn't be checked or which extraction settings were applied during checking.
Available with Acrolinx Server version 5.0: You can now contribute new terms for spelling issues
We've realized that spelling issues are often new terms that haven't yet been added to your terminology. Previously, you could only contribute terms that Acrolinx flagged as New Terms. Now you can contribute new terms that Acrolinx flags as spelling issues directly from the plug-in. Your terminologist can then validate these words to make them available to all writers. To use this new feature, activate both New Terms and Spelling checking options.
Available with Acrolinx Server version 5.0: The Scorecard now loads large results faster and with a more consistent design
We've introduced a new HTML format of the Scorecard in the Acrolinx Server version 5.0 instead of the previous XML. If you had a large scorecard file, the previous format wasn't always able to show all the content. The previous format also had some minor layout and design inconsistencies across different browsers. If you use the 5.0 server, Acrolinx will show the new format, which has a consistent design across all supported browsers and loads large scorecard documents faster.
Acrolinx now logs which extraction setting was used during a batch check
If you use checking profiles and batch check documents but you have a number of different extraction settings available, Acrolinx selects the best possible match for each document. In previous versions of Acrolinx, it was not always clear which extraction setting was applied during checking. Acrolinx now displays which extraction setting was used to check which document in the plug-in log file.
We removed a workaround for a Flare version 12 bug
There was a bug in the official release of Flare version 12, so we built in a workaround for you. What happens is that if your documents contain the "Madcap:conditions" attribute and you run a check with Acrolinx then Flare crashes. In Flare version 12.0.5991, MadCap fixed this bug, so we've removed the workaround. That means that if you update to Acrolinx 4.7 SR1 but still use the Flare version with the bug, then Flare will crash. So, it's best to update to 4.7 SR1 and Flare 12.0.5991 if you're not already using them.
Segmentation and filter settings distributed with the model user settings weren’t working for batch checks
Previously, if your administrator distributed segmentation and filter settings using the model user feature, Acrolinx didn't correctly apply these settings when you ran a batch check. So, you might have seen false alarms due to missing sentence breaks or filter settings. We've fixed this, so now Acrolinx applies all your filter and segmentation settings during batch checks that your administrator distributed using the model user feature.
Acrolinx colored markings got "stuck" in documents
If everything's working as it should, when you save and close your document, Acrolinx removes all the colored markings. In previous versions, Acrolinx sometimes didn't remove the colored markings from your document, so they got "stuck". And even if you selected "Permanently Remove Flags", they still stayed "stuck" in your document. We've now made sure that in those circumstances, "Permanently Remove Flags" removes the colored markings from your document.
The plug-in requires Acrolinx server version 4.5 or later.
We recommend updating to Flare version 12.0.5991.
Acrolinx for MadCap Flare - Version 4.7 (18 May 2016)
This is a minor release but it also includes a few other improvements, bug fixes, and updates.
Also, if you've read the plug-documentation before, you might be accustomed to visiting our old infocenter at "infocenter.acrolinx.com". While older versions of the documentation are still there, we've moved the latest documentation to the section " Using Acrolinx in your Editor - Classic Edition " in this help center.
Rebranded Acrolinx Logo and Icons
We've updated all icon images and the Acrolinx logo that appear in the product.
We've removed the documentation that's packaged with the Plug-in
We've removed the documentation that's packaged with the MadCap Flare plug-in. Now, when you select "Help" in the MadCap Flare plug-in, you'll be taken to the article Using Acrolinx in your Editor - Classic Edition in this help center.
We want to make sure that you get the most up-to-date help so that's why we take you to the online help center. If you have writers who need offline help, you can click the PDF button at the top of an article. Download the PDF and distribute it to the writers who need to access the information offline.
Writers can now register with the server if their user ID or password contains umlauts
Previously, Acrolinx didn’t allow you to have any special characters in user IDs or passwords that you enter from the plug-in. You can now use user IDs or passwords that contain umlauts.
Enter Path to Files in Batch Checking Dialog
In previous versions of Acrolinx, if you wanted to batch check documents, you had navigate through your local file structure to select documents to check. You can now enter a path in the file selection field to select documents.
We've added the Acrolinx score to the embedded checking status
When enabling the option to embed the checking status into the checked document, we now also embed the newer Acrolinx score (sometimes referred to as the "quality score"). The embedded metadata now looks something like this:
acro_status Date = 10/13/15, Time = 13:15:12, spelling = 13, grammar = 23, style = 129, total = 165, score = 4135, status = red, AcrolinxScore = 17
We've added support for MadCap Flare version 12 32-bit and 64-bit.
We've added support for Microsoft Windows 10.
Acrolinx batch checking of documents that contained broken snippet links resulted in Flare crash
If you used version 4.0 of Acrolinx for Flare and tried to batch check documents that contained broken snippets, Acrolinx was not able to run a batch check and Flare would crash.
We fixed this issue so now when you try to check documents that contain broken snippet links, Acrolinx successfully runs and completes a batch check.
Acrolinx Plug-in for MadCap Flare - Version 4.0 (23 April 2014)
The Acrolinx Plug-in for MadCap Flare adds Acrolinx functionality to MadCap Flare so that you can check your documents in MadCap Flare.
You can find the user documentation in the Acrolinx Infocenter.
Support for MadCap Flare versions 10.1
You can install the Acrolinx plug-in for MadCap Flare versions 10.1.
You can now select checking profiles in the plug-in options
If you connect to an Acrolinx server that uses checking profiles, you can now select the checking profiles directly in the plug-in interface. With checking profiles, you can check your documents without configuring checking options or segmentation settings first. For example, a checking profile contains the configuration for the language, the rule set, the issue types, and if necessary, the term sets. Also, the checking profile contains all necessary filter and segmentation options so that Acrolinx can correctly extract the text.
Added support for comparative checking
Managers can use comparative checking to measure how a document has improved after authors use to correct a document. When comparative checking is enabled, the plug-ins automatically run a background check after a user closes a document. The results of these checks are written to your reporting database and can be used to compare the checking results before and after the author corrects a document with Acrolinx. You can use this reporting data to create database queries that measure the benefits and return on investment that provides.
You must manually save a document after you applied corrections
Due to a known issue in MadCap Flare 10.1, the editor does not always prompt the user to save changes before closing a document. If you do not save your document before closing, you might lose any corrections that you applied.
You might receive the error message "Your task could not be completed because Acrolinx is still busy"
This issue sometimes occurs after you open an Acrolinx window like the Acrolinx options and then click somewhere else in the main MadCap Flare window. The Acrolinx window is minimized to your task bar and you cannot do anything else with Acrolinx until you close that window. Sometimes it's easy to overlook an Acrolinx window that is minimized to your taskbar. If you get this error message, check your taskbar for a minimized Acrolinx window and close the window.