Tools > Options dialog accelerators don't work
sometimes
Some property pages within the new unified options dialog won't
respond to keyboard shortcuts until focus is moved into the embedded XFT form
that is on the active property page. This limitation relates to Windows'
handling of embedded ActiveX controls.
Generate Output fails if filenames or paths contain a mix of
Polish characters and spaces
The DITA Open Toolkit included with the software fails to generate
output if any of the filenames or paths contain Polish characters AND spaces.
The only workaround at this time to adhust filename and paths to exclude spaces
OR put all the files into the same folder.
Shortcut key doesn't work after moving focus to Map Editor with
XMetaL Navigator
Shortcut key doesn't do anything after moving focus into the Map
Editor using the XMetaL Navigator feature. To work around this, please press
the <Tab> key once and try your keyboard shortcut again. If it still
doesn't work repeat pressing <Tab> key and trying your shortcut key until
you get some action.
WebHelp output's Print function doesn't work for local
files
When opening a local copy of the WebHelp output into a web browser,
especially Google Chrome, clicking the "Print" button results in no action.
This behavior is typically the result of a web browser's "same-origin" security
model for local files versus files loaded over http.
This behavior can be worked around by running a local web server or
deploying the WebHelp webhelp_out folder's contents to a web server and
navigating your browser to that web server location.
When using DITA 1.3 XML schemas, reusable component feature is
disabled
XMetaL's reusuble component feature has not been setup for the DITA
1.3 XSDs. As a result, related menu items like Reuse > Create Reusable
Component are disabled.
WebDAV lock cannot be obtained for document just opened
When a document is opened from a WebDAV server into XMetaL Author
Enterprise, an error message maybe displayed stating that the WebDAV lock could
not be obtained. This issue is due to the DITA MapEditor feature preprocessing
the document's XML with our XMetaL XML processor (XMXML). XMXML contains a lot
of the same code as XMetaL Author including the WebDAV locking logic and as
such, XMXML ends up obtaining the WebDAV lock first.
To work around this issue, the DITA options must be changed so that
ditamap files open into the XML view by default. To change this setting, select
the Tools > Options... menu item and select the DITA category's Map Editor
tab. On the Map Editor tab, adjust the "Open DITA maps in the:" drop-down list
so that "XML view" is selected. Click OK to accept the changes and restart
XMetaL.
Note: The DITA feature does not support WebDAV out-of-the-box. A
WebDAV capable XMetaL connector is required to use the DITA feature with a
WebDAV server.
The x64 Cameras In Focus and Meeting Minutes samples have some
features that don't work
A few of the Cameras In Focus and Meeting Minutes sample's features
rely upon Microsoft components that do not have an x64 equivalent (e.g.
MSScript.ocx, MSCAL1.ocx). Yet other features rely upon a x64 version of
Microsoft Word to be installed on the computer. In the x64 version of the
software, these samples have been removed from the Help > Samples submenu to
avoid issues. You can still invoke either samples template but please use
caution when running these samples as they may not gracefully degrade when
invoking features with a dependency on these 3rd party items.
Built-in toolbar auto-layout on first launch
When XMetaL Author is started for the first time, the built-in
toolbars will each be docked on a separate row. Custom DTD-specific toolbars
will be docked more efficiently (i.e. multiple per row) providing there is
enough horizontal space to do so. Once toolbars have been reorganized (by
dragging them around), their positions will be remembered. This vertically
oriented auto-layout for built-in toolbars will also take effect any time the
XMetaL Author workspace is reset, which is done by holding the Ctrl key down at
startup.
Child submenus/menu items not copied when moving top-level menu
buttons
Moving top-level menu buttons will not copy the child submenus or menu
items. Similarly, moving submenu items will not duplicate those child items.