Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: January 10, 2018, 05:11:32 AM 
Started by KdG - Last post by KdG
I noticed that since XMetaL Author Essential the OpenString function hangs when you add the [boolTemplate]
So Documents.OpenString(doc,1,"test.xml",false); causes no response
While Documents.OpenString(doc,1,"test.xml"); works fine.

Is this a general thing or just someting with my installation?

Steps to reproduce: Copy-paste the example from the Programers Guide (below) into XMetaL:

// XMetaL Script Language JSCRIPT:
var xmlDec = '<?xml version="1.0"?>';
var docType = '<!DOCTYPE Article SYSTEM "journalist.dtd">';
var contents1 = "<Article><Title>New Document</Title>";
var contents2 = "<Para>Contents</Para></Article>";
var doc = xmlDec + docType + contents1 + contents2;
// Open the document in Tags On view

 on: January 05, 2018, 12:08:57 PM 
Started by luskds - Last post by luskds
We are having some problems with XMetal not opening documents due to a "Server Busy" error.  We get this with Windows 10 users running XMetal 10 and 12.  Users are running Windows 10 version 1511, 1607, and 1607 with the current updates.  XMetal is both Essentials (concurrent license) and Enterprise.  We have some success with the two following workarounds, but the problems don't go away.  If a workaround works (they don't in all cases), it has to be repeated every time XMetal is opened.  Workarounds:
1.  Hold down the Ctrl key when you open a doccument and skip the last session's workspace.
2.  Clear all files in C:\Users\<your_id>\AppData\Local\Temp before opening XMetal

Any ideas?

 on: December 27, 2017, 07:56:41 AM 
Started by MarcB - Last post by MarcB
Using XMetaL Author Enterprise on Windows 7 with default DITA version set to 1.2 in the DITA Options.

We are noticing the following behavior when including references to DITA maps from within a DITA map in conjunction with the @navtitle attribute. If the referenced DITA map is a regular map, XMetaL shows the value of the @navtitle attribute as before. If the referenced DITA map is a bookmap, the @navtitle attribute is ignored and the ID value of the referenced map is displayed.

Reference to a regular map:
<topicref format="ditamap" scope="local" href="command_central/_command_central_help.ditamap" navtitle="Command Central Help"/>

Reference to a bookmap:
<topicref navtitle="Element ID :bookmap_A5B7B17D145749FC9C631614A439B8AC" href="installer/_using_installer.ditamap" scope="local" format="ditamap">

This happens with <topicref> and <mapref> alike, starting with XMetaL 12.

I understand the @navtitle is deprecated with DITA 1.2, but we have many DITA maps with that attribute, including nested DITA bookmaps, and they are now all displaying the Element ID as navtitle.
A workaround is to set the @locktitle attribute to "yes" on the topicref, but my question is: what should we be doing? What is the recommended format of a topic reference in a DITA map?

Marc Beckers
Software AG

 on: December 21, 2017, 02:35:55 PM 
Started by JS_Nbg_DE - Last post by Derek Read
This type of selector isn't supported. The following would do it but only for this specific case:

msub > mi mi {
  vertical-align: sub

That's going to affect all <mi> elements that have a <mi> before them.

If you are going to have content where there are more than two <mi> elements you would have to write a script to affect just one and not the others. Something similar to the following would do that:

//XMetaL Script Language JScript:
//create a Range we can move around to alter style(s) for specific elements
var rng = ActiveDocument.Range;
//get all nodes that are the second mi sibling inside msub:
var nodes = ActiveDocument.getNodesByXPath("//msub/mi[2]");
//loop through the list of nodes, move the Range to each, and set the style(s):
for(i=0; i<nodes.length; i++) {
rng.ContainerStyle = "display:inline; vertical-align:sub; font-size:0.8em";

Note to anyone that wants to use this approach for DITA: Please don't try. Modifying the DITA customization's scripts is not supported.

Regarding MathML:
If you are trying to style MathML to make it easier to edit in XMetaL Author I think that's going to be a lot of work unless you use a very small specific subset and perhaps only use some specific equation layouts. If you use MathML on a regular basis I would highly recommend Design Science's "MathFlow Editor" for XMetaL Author (it works with XMAX as well):

 on: December 21, 2017, 09:38:27 AM 
Started by JS_Nbg_DE - Last post by JS_Nbg_DE

is it possible to set a specific style to the second child element?
In this sample i want the second child element of msub should be shown with vertical-align sub in xMax.


This don't work:

msub > *[2] {
  display: inline;
  vertical-align: sub;
  font-size: 0.8em;


 on: December 19, 2017, 10:17:05 AM 
Started by ballen - Last post by ballen
I have XMetaL Author Enterprise version 12 and I'm generating PDFs using the RenderX XEP delivery type. I've been working on customizing the PDF output. I'm trying to make figure text (like the number and title) appear above the image instead of below it, but I'm stuck.
I've been working in the below file, which specifies what appears in the figure text. But I can't tell if it controls the text position in relation to the image:

I'm pretty new to xsl stylesheets so anything to point me in the right direction is much appreciated.

 on: December 18, 2017, 02:39:29 PM 
Started by Verner - Last post by Derek Read
Not out of the box as we haven't had any requests for such a feature. It isn't on the feature request list either (for the same reason).

I think writing a script that would do this would be fairly straightforward using the APIs XMetaL Author (or XMAX) provides. Walking the document to get each element then turning that into a string and saving it all out to a text file sounds fairly easy to do. I'm sure there are bound to be a few gotchas you'd need to work out (do you need comments and PIs, or just elements and attributes, the entire document / a portion of it, leave out specific elements and values, etc...?)

 on: December 15, 2017, 08:50:35 AM 
Started by Verner - Last post by Verner
We are going to make documentation for apps and responsive webdesign. Today we use XMETAL9 and SDL LiveContent Architect Publication Manager 11.3 with a pdf output.

I know that Oxygen can convert DITA to JSON. Can XMETAL do the same?

 on: December 11, 2017, 06:13:29 PM 
Started by tmakita - Last post by Derek Read
In addition, in Tags On view (and specifically not Normal view) you can place the insertion point between the opening <table> tag and the grid-rendered portion of the table to access that element's attributes, or between the grid and the closing </table> tag. My previous post works for both Normal and Tags On view.

 on: December 11, 2017, 02:20:21 PM 
Started by tmakita - Last post by Derek Read
Yes, you can set the value for this attribute. Currently, if you wish to set this attribute value (or other attributes that are not exposed in the Table Properties dialog) you can do the following:

1) Place the insertion point anywhere in the table.
2) Open the Attribute Inspector.
3) Drill up to the "table" element using the dropdown list at the top of the Attribute Inspector. The current values for that attribute will be listed.
4) Click on the @rowheader attribute value's listbox and select one of the enumerated values listed (it will list all the values defined by the current DTD). If you are authoring to the DITA 1.3 DTD then the value "headers" will be available. If the DTD is for an older version of DITA (1.1 or 1.2) then that value will not be available. If you are working with a specialized DITA DTD then any values you have defined should be available.

Note: This Attribute Inspector feature can be used to access the attributes on any ancestor element relative to the current selection.

Pages: « 1 2 3 4 5 6 7 8 9 10 »