Pages: 1 2 3 4 5 6 7 8 9 10
 on: August 11, 2017, 05:53:07 PM 
Started by akheiljain - Last post by Derek Read
The CritiqueUtils.dll doesn't ship with any products anymore and is unavailable. It was part of the integration between XMetaL Author Enterprise and XMetaL Reviewer (a server product that was discontinued).

 on: August 09, 2017, 11:26:48 AM 
Started by akheiljain - Last post by akheiljain
Not having any luck with running the demo 5 and demo 6 from the XMetal website demo of "Extending XMetaL Author Using the Resource Manager" Has anyone been able to run through the demo successfully? Does anyone know how to get access to CritiqueUtils.dll and/or the source code?

Akheil Jain

 on: August 07, 2017, 02:00:14 AM 
Started by Shekii - Last post by Shekii
Xmetal Version Using: Xmetal Author Enterprise 10.0


With our current stylesheet, we can successfully generate a PDF with multiple parts in the DITAMAP expressed as sections in the PDF and these sections make up one chapter. Although, now we need to generate the PDF with all of the collective chapters that have been made. When I try to insert even one chapter within the DITAMAP, it fails. I validated this DITAMAP against our DTD file and it came back successful.

Here is our current DITAMAP containing two chapters that I want to have on one PDF document:

When I try to compile:

The PDF generation works when the DITAMAP has many part map references but not with chapter map references.

Is it possible at top level, to have the chapter first and then part references inside these chapters? Or, due to the hierarchy of the dita standard, are chapters only allowed inside parts. I ask this because we have 20 chapters that we are going to be merging together.

I hope I have explained our problem well enough for you to understand, if not just tell me.


 on: August 03, 2017, 01:11:15 PM 
Started by tharpa - Last post by Derek Read
If you have the ability to debug the customization that would be the best option.

I'm not sure what opening a record means exactly, or what a record would be (if it is not simply opening an XML file stored on your drive), but it sounds like maybe the customization would be overriding the basic File > Open functionality on the File menu?

If that's the case then look in the macros in the customization for the event macro named "File_Open". If you find one of those that would be the best place to start debugging from. This would be an application-level macro, so it would probably be in the Startup subfolder in the installation.

Have a look at the Programmers Guide topic "File operations" for more information on the File_Open event macro and other related ones (File_New, File_Save, File_Close, etc).

If opening a record is done some other way from selecting File > Open then you could be looking for a macro with any name. In this case the macro file (MCR) would still likely be in the Startup folder but the macro that does the "open record" might be called anything. In this case I'd search for "open" or similar words in that MCR file.

Hopefully whoever built this documented something, or at least put comments into their code?

 on: August 03, 2017, 07:35:18 AM 
Started by tharpa - Last post by tharpa
I am supporting, as best I can, a legacy application which is supposed to open its records in XMetaL Author Essential 9.0.  I had not used this feature in a couple of months, however, now it does not do this, i.e. XMetaL does not open, or if it is already open, it does not open the record.  For other users it is still working properly.  I tried uninstalling and reinstalling both XMetaL and the other application.

Any thoughts on where I should look?

 on: August 01, 2017, 05:24:20 PM 
Started by jshick - Last post by Derek Read
It sounds like your XFT form is VBScript. To use my example unmodified you'd need to use it in a JScript XFT form. The scripting language is declared when you first create the form in the XFT editor (you can choose from any of the script engines installed on your machine).

XFT forms (unlike MCR files) can only include one scripting language.

If you are comfortable with JScript then you may wish to recreate your form, selecting JScript as the language. If you prefer VBScript then the code would need to be adjusted from JScript to VBScript.

 on: July 27, 2017, 01:51:08 PM 
Started by jshick - Last post by jshick
I copied into Notepad first to make sure it wasn't picking up any special characters from the HTML, then I copied from Notepad into the XMetal Form Layout Tool.

The first error I get is "Expected statement" on the first line. It apparently doesn't like // being used to denote comments. I can use a ' at the beginning of each comment line and it seems to get along with that just fine.

The second error I get is "Expected end of statement" on the line 3, the variable definition. It seems like it doesn't like a ; at the end of each line, so I removed those.

The third error which I can't get passed is the "invalid character" on the "while" line.

 on: July 26, 2017, 04:47:55 PM 
Started by jshick - Last post by Derek Read
Not sure where that would be coming from. Does it not say which character is invalid?

Try pasting into a different editor?
Stepping through with a debugger might give more information.

 on: July 26, 2017, 02:44:10 PM 
Started by jshick - Last post by jshick
I'm getting the following error:

Invalid character
Source line: while(rng.MoveToElement(elemName)) {

 on: July 26, 2017, 01:55:47 PM 
Started by jshick - Last post by Derek Read
There's almost always a way. Just need to define the problem in enough detail to understand what needs to be done.

Maybe something like this is what you need.

//XMetaL Script Language JScript:
//name of element you are looking for
var elemName = "ref-callout";
//create a range to walk through the document
var rng = ActiveDocument.Range;
//move the range to the start of the document
//for every element that matches the right element name...
while(rng.MoveToElement(elemName)) {
   //...if that element has an @href with the value r101
   if(rng.ContainerAttribute("href") == "r101") {
      Application.Alert("found one...");
      //do whatever you need to do to this element here...

Pages: 1 2 3 4 5 6 7 8 9 10
email us