|Acrolinx for Microsoft Word on Windows - Classic Edition||4.0, 4.0 SR1|
|Acrolinx for Arbortext Editor - Classic Edition||4.0,|
|Acrolinx for Lotus Notes - Classic Edition||4.7|
|Acrolinx Desktop Checker - Classic Edition||4.7|
|Acrolinx for JustSystems XMetaL||4.7|
|Acrolinx for Oxygen (Standalone and Eclipse) - Classic Edition||3.5|
Which Editor Do You Use?
To see the content that's relevant for your editor, choose it from the menu above
File Formats That Are Not Fully Supported
Although Acrolinx can check most document formats that can be opened in Word, the checking performance for HTML files can be much slower than for standard Word documents. If you notice performance issues when checking HTML files in Word, use the Acrolinx Batch Checker instead.
Checking Password-Protected Documents
Acrolinx for Microsoft Word cannot check password-protected documents. If a document is password-protected, remove the protection before you check the document. If a document is protected with an empty password, Acrolinx checks the document as read-only.
Performance in Microsoft Word 2013
When running a standard check in Microsoft Word 2013, the plug-in performance can be significantly slower than other versions of Microsoft Word. If you use Microsoft Word 2013, check large documents with the corrections dialog box instead of running a standard check. When you check documents in Microsoft Word 2013, the plug-in takes longer than usual to insert and remove flags. You can avoid this issue by using the corrections dialog box.
Additionally, if you run a check for SEO issues, the "Assign Keywords" dialog box can take a few seconds to respond when you place the cursor in a text field or click the "+" buttons.
Unsupported Field Types
There are certain types of fields that Acrolinx for IBM Lotus Notes always ignores regardless of filter settings. The following types of fields are ignored because they typically contain content that is not suitable for checking:
- Fields that have names beginning with "$".
- Fields that have names beginning with "tmp" (case insensitive).
- Fields that contain Boolean values.
- Fields that contain Lotus Notes Mail addresses beginning with "CN=".
- Fields that contain Lotus Notes resource references beginning with "stdNotes".
Checking Differences Between Editing Modes
In Oxygen, you can edit documents in different editing modes. You can use Acrolinx to check text in Author mode or Text mode. The plug-in generally works the same way in both editing modes but it might produce slightly different checking results when you compare results from the two editing modes.
Differences in Whitespace Handling
When you check in Text mode, the Acrolinx plug-in handles the whitespace filtering.
The plug-in extracts the text, filters out multiple whitespace characters such as spaces, line feeds and tabs, and replaces them with a single space.
When you check in Author mode, Oxygen handles the whitespace filtering.
Oxygen automatically filters out multiple whitespace characters. The plug-in then extracts the filtered text that is provided by Oxygen.
Incomplete Checking for Documents with Validation Errors
In Text mode, it is easier for users to accidentally change tags and characters so that the XML is no longer well-formed. If you check an XML document in Text mode and the markup contains Oxygen validation errors, the plug-in can still extract some of the text but might not be able to check the whole document. Consequently, you might receive inconsistent or unexpected checking results when you check a document with validation errors.
Limited Functionality When Checking Text in Content References
Text that is included as a content reference (or "conref") is extracted and checked as read-only. If the plug-in finds issues in content references, it inserts flags normally. However, these flags cannot be edited through the context menu or directly in the document. The options in the context menu are disabled. To edit the flags, you must edit the originating document of the content reference.
Checking Selections of Text
You cannot check selections of text. When you start a check, the plug-in always checks the entire document.