Fixed Issues in 12.0.0 Authoring Bridge
The following issues are fixed in Content Manager 12.0.0 compared to 11.0.0.
General Authoring Bridge
- When a browse dialog is opened to select an object, and the selectable object types are set to all types (Topics, Maps, Library Topics, Images and Other (Word, PDF, ...)), the filter is set to XML object types (Maps, Topics, Library Topics) on initialization. The default filter in this case will now have Objects of type specifying (All) allowing Other (
CTTEMPLATE) selection. [SRQ-3265|TS-9825] - When attempting to insert a
@conrefto a section of a document that contains@varrefdefinitions, the yellow rectangle selection extends to the end of the document, instead of including only the current block. Replacing the tags<ph varref="productname"/>with<ph varref="productname"></ph>corrects the problem so that the selection tool only selects the current block by default. The technical issue is that browser don't like self-closing<div/>elements. [TS-9752|SRQ-3271] - When you want to update an existing
<xref>element that references an element in a topic with bookmark, the selection is set to the Select bookmark dialog, but the selection is not shown in the preview. [TS-8622] - When you update an image with a new image binary, therefore with different content, then the new image is now displayed in the XML editor. Depending on timing, it requires the user to trigger a Refresh F5 request. [TS-9768|TS-8879|SRQ-3069|SRQ-2132]
- Access keys for our SDL Knowledge Center menu in all XML editors are altered in a way that they are all unique now. [TS-8972|TS-7995|SRQ-1340]
- Some ja-jp translation corrections have been done in Authoring Bridge, such as WhereUsed, batch metadata Current Values, etc. [SRQ-2460|SRQ-2496|SRQ-2374]
- When you check out a topic while the preview window is still loading, it may crash the application with a
stackoverflowexceptioncaused by the XULRunner preview engine. [TS-8928|TS-8929|TS-8930|SRQ-2294]
JustSystems XMetaL
*[ishcondition]:beforein infoshare-base-override.css does not work for<topicref>in a map because conflicting styling exists in map-base.css. When you have an@ishconditionon a<topicref>, the<topicref>is shown in gray and the condition text is also shown in the preview. [TS-9542|SRQ-3036]- A topic cannot be associated with a key definition file when it is not checked out (read-only). [TS-10468]
- The behavior of JustSystems XMetaL 9 and 10 is now fine-tuned together with XMetaL engineering and usability changes on our AuthoringBridge implementation. When inserting an
<xref>or<link>, the dynamic text resolving of XMetaL wasn't triggered. This meant that you had to do a manual . Our common efforts are packaged in this release. [TS-9780|TS-9779|TS-9784|TS-9790|SRQ-3272] - When opening a topic in read-only, and then checking it out using the editor's menu or toolbar, a subsequent check in command on this object would fail with
Following error occurred while checking in: The object 'xxx v. y - language' is currently in use.[TS-9754|TS-9753|SRQ-3289] - A failed Check in will now attempt to reopen the file if you get an exception triggered by the
IWrite*plugins like Following error occurred while checking in: The plug-in "CHECKREVIEWERFILLEDIN" returned the following error: "Plugin 'CHECKREVIEWERFILLEDIN' reports that field 'FREVIEWER' is empty for object 'GUID-8C8F01ED-9785-47DE-9A00-1F8AAFD94E7D' and should be filled in when field 'FSTATUS' is changed from 'In progress' to 'To be reviewed'". [TS-8742|TS-8968] - When having an object open in the XML editor in View mode (read-only), you can Check out that object in Publication Manager. The XML editor is now notified that the object has changed. [TS-9149|TS-8962|TS-8960|TS-8630|SRQ-2344]
<oXygen/> XML Author/Editor
- A file that contains a single quote (
') in its title, hence its file name, remains checked out after a Check in action. [TS-9944] - When you check out a topic in Publication Manager on a Japanese OS, oXygen hangs. It does not hang when the system locale is set to another locale (e.g. Dutch Belgium). This fix contains an adaptation that will trigger an open using a new thread instead of waiting for the main thread. This change was made after validating with the oXygen support team. [TS-9908|SRQ-3581]
- The repeated checking out a map leads to error The object is already in use by another program. [TS-9884|TS-9714|TS-9695]
- Closing oXygen and canceling all save requests crashes with
java.lang.NullPointerExceptionincom.sdl.trisoft.triab.AuthoringBridge.getConfigurationManager. [TS-9512|SRQ-3013] - oXygen 16.1 - An error message
Value can not be nullraised byGetWorkItemByPathappears after any URL is opened, when the Authoring Bridge is installed. [TS-9665|TS-9620|SRQ-3034] - The editor hangs when multiple files are opened from the Browse Repository dialog or from an external program like Publication Manager. The workaround is to use the tool bar which is resolved within the application while the right-click-menu are resolved over the operating system. The fix is that the multiple files are queued and opened when the editor allows it. [TS-9324|TS-9467|TS-8688|SRQ-2800]
- When checking in a topic, depending on timing, you could occasionally see an editor dialog displaying Could not save the document due to: C:\Users\...\InfoShare\......=en=.xml (Access Denied). This is a cosmetic error without data loss. Behind the scenes the file is handled and refreshed by multiple application threads. The file system read-only attribute is used to indicate that a file is no longer writable which can cause the generic Access Denied to appear from the other application threads. [TS-9409|TS-9468|SRQ-2632]
- Refreshing using the menu occasionally messes up resolving of images and conrefs. [TS-8745|TS-8596]
Arbortext Editor
- When having a DITA Map open in the XML editor in View mode (read-only), you can Check out that object in Publication Manager. The XML editor is now notified that the object has changed. [TS-9041|TS-8661]