Pages: « 1 2 3 4 5 6 7 8 9 10 »
 41 
 on: June 23, 2017, 12:52:04 PM 
Started by kroan - Last post by kroan
Occasionally, XMetal becomes unresponsive and then crashes. Because it is occasional, I have not been able to pinpoint specific actions that cause it. The last time this happened, the system reported a Visual C++ Runtime Library error. 

Are there known conflicts with other C++ applications? Has anyone else seen this behavior? Is there a file where logging details are captured where I might be able to see more information?

To my knowledge, I am the only person in my organization that is experiencing these crashes.

I am running
  • XMetaL version 9.0.0.53
  • SDL LiveContect Architect 2014 author bridge
  • SDL publication Manager 11.1 (for LCA 2014)

 42 
 on: June 22, 2017, 05:23:22 PM 
Started by akheiljain - Last post by Derek Read
I'm not sure what the exact final goal is but perhaps one of these posts that include some example code will help?

http://forums.xmetal.com/index.php/topic,512
http://forums.xmetal.com/index.php/topic,514

 43 
 on: June 22, 2017, 05:18:03 PM 
Started by Fa - Last post by Derek Read
In the current release (12) you can modify the ct_config.xml file directly (as you have done) or you can use the new UI for that (Tools > Configure Conditional Text).

However, you also need to use Tools > Style Conditional Text. I think in previous releases that was not necessary but in version 12 it is. Once you do that (make at least one change) everything should work everywhere.

 44 
 on: June 22, 2017, 03:49:19 PM 
Started by akheiljain - Last post by tonys
This topic might also be relevant: http://forums.xmetal.com/index.php/topic,3706.0.html

 45 
 on: June 22, 2017, 03:34:58 PM 
Started by akheiljain - Last post by tonys
A good place to start would be the Windows Scripting Host documentation. It will tell you what is available to all applications that implement JScript.

 46 
 on: June 22, 2017, 08:44:03 AM 
Started by akheiljain - Last post by akheiljain
Hi Tonys,
 Thank you for your reply, would there be another way to accomplish this in XMetal, I need to launch a URL window, attach an event listener to it and get event data back. I am able to run the JS directly through Chrome, but not sure how to accomplish it through an xmetal macro.

 47 
 on: June 22, 2017, 07:36:35 AM 
Started by Fa - Last post by Fa
Hi!

I have modified the default values of the ct_config file, but I have kept the default attributes (i.e. audience, platform and product), I've only changed the values.

I have then restarted XMetaL and my changes are shown correctly in the "Configure Conditional Text" window.

However, when I want to build my pdf using conditions, from the "Generate output" window I choose "Show/Hide Conditional Text", the values are still the default (e.g. "administrator" and "user" for Audience, etc.).

In my old XMetaL, all I needed to do was to modify ct_config.xml, but it seems XMetaL 12 requires something more, which I have not found from the help.

Also, the help topic (Show conditional text in previews and output) refers to clicking "Advanced" to specify advanced settings, but I can find "Advanced" neither in the "Generate Output" dialog nor in the "Show/Hide Conditional Text". I find an "Advanced" tab under "Configure Output", but nothing there points to settings related to conditional building attributes and values.

Am I missing something? Any help would be very much appreciated!

Fa

 48 
 on: June 21, 2017, 04:57:39 PM 
Started by akheiljain - Last post by tonys
The window object is implemented by web browsers. Since XMetaL is not a browser, it doesn't exist.

 49 
 on: June 21, 2017, 02:52:04 PM 
Started by akheiljain - Last post by akheiljain
XMetal macro JScript wont run
window.open
window.addEventListener

does any one know why or how to make it work?

 50 
 on: June 20, 2017, 08:12:30 AM 
Started by Fa - Last post by Fa
Hi Derek (and anyone else interested)!

Following up on this topic (sorry about the long delay!).

After discussion with my colleagues why they had ended up creating their own elements, it turned out that the main (and probably only) reason why they did that is that the program they develop uses context sensitivity.

The help file they create is a simple "single html file".

Since they are writing their code for the different modules before the corresponding help topics even exist, they already create a context sensitive link within the software pointing to an element that does not yet exist (in a file that does not yet exist either).

At first, they tried to use the topic id attribute value as a unique identifier, but it failed because of the way the conversion is done. When DITA-OT processes the xml topics, it collects all the links and targets (in this case the topic id's), and it renames all targets in the html to "#unique_01", "#unique_02", etc.

I guess the reason behind the behaviour is that since it creates a single html out of lots of small DITA files, it wants to make sure there are no duplicate anchors, and therefore, instead of having a mechanism that checks for duplicate, it just coldly replaces all names for anchors created from elements with new names that it knows are unique.

The drawback in this case is that there is therefore no way of knowing what to link to before the html has been built, and even then it would require a lot of manual work. That's how they came up with the idea of creating the help_anchor elements that they then process to become an html anchor (<a href="...">).

So my question now is: is there
a) a way to force XMetaL (DITA-OT) to keep the elements' IDs intact and transfer them to the href attribute value for anchors (<a>) in the html instead of replacing them by the #unique_nn value
or
b) an existing, valid DITA element that could be use for this purpose?

Thank you!

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