Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: May 31, 2019, 03:15:26 PM 
Started by mikestratton99 - Last post by mikestratton99
Product: XMetaL Author Enterprise 11.0
Installer#: 11.0.0214

OS: Windows 10 Enterprise
Version: 1709
OS Build: 16299.1146

SITUATION: I was given a document in MS Word format and asked to convert it into a task topic in XMetaL. The Word doc details the procedure for how a user can report a software issue to tech support, and it contains a clickable link that opens a MS Outlook email template. (The email template is a blank trouble report that consists of a series of questions for the user to answer to describe their software issue before sending it to tech support.)

Screen shot from Word doc attached.

QUESTION: How can I create a link in my XMetaL task topic that links to/opens this same Outlook blank email template?

 on: May 29, 2019, 04:27:03 PM 
Started by jodekirk - Last post by Derek Read
In theory yes...if you can find and install a JavaScript engine that meets those needs.

Windows includes JScript and VBScript with the Windows Script Host but you can install other script engines. Such an engine would probably need to identify itself using a name other than "JScript" to avoid conflicts with the Windows Script Host version of JScript. The script engine's name is what you insert in a macro inside the MCR file used by XMetaL Author to let it know which script engine to tell Windows Script Host to use to run the script for that particular macro.

Whether such an engine exists for Windows I don't know. It needs to meet these requirements:

This would be similar to people that install and use the PerlScript (ActivePerl) or PythonScript (ActivePython) engines with XMetaL Author. Most people are using JScript or VBScript as they do not require additional software to be installed, but there are a number of XMetaL Author users that do use these other engines.

 on: May 29, 2019, 04:03:49 PM 
Started by megl - Last post by Derek Read
It sounds like this is limited to one user, so identifying what is different about this particular computer's setup would be the first step. Compare any files installed that modify or extend the XMetaL Author installation: "application customization" files (this would include CMS integration modifications or other changes to the software, primarily limited to scripting modifications or other code that is calling XMetaL APIs) as well as "document customization" files (the DTD/XSD plus any other files loaded when a particular XML file is loaded, which can include script inside MCR, CTM and possibly other files). The people that created these customizations should be able to do this.

If this is affecting multiple users then debugging can be done by the people that created any custom scripts or other code you are running then the code to examine in particular would be anything inside events corresponding to mouse clicks (On_Click, On_Double_Click), the "Selection" object in general (or the mostly equivalent "Range" object), events that fire frequently (On_Update_UI), or similar.

If that isn't possible for whatever reason please feel free to submit any customizations plus a sample XML document to XMetaL Support so they can try to reproduce the issue. If the issue is limited to one person then the most likely cause is a broken file. If the issue is affecting everyone, but has not in the past, then it is most likely that changes to the customization have been made that are buggy that were not properly tested, or that an API is being used incorrectly, or if used correctly then perhaps in an unexpected way that was unforeseen.

The more information that can be provided to XMetaL Support the better as they will likely need to reproduce your setup as closely as possible to trigger the issue.

 on: May 29, 2019, 08:06:25 AM 
Started by jodekirk - Last post by jodekirk
Is there any way to use modern JavaScript with XMetaL Developer for macros? I would like to use the new ES2015 or newer JavaScript syntax and features. Currently I have been using lots of polyfills.

I would like to use the new features such as:

I keep forgetting old JScript syntax now that I've been using modern JavaScript in other web development projects for over 4 years.

Jeremy Odekirk

 on: May 29, 2019, 07:27:54 AM 
Started by megl - Last post by megl
I have a user on Windows 10 Pro using XMetaL 12 Enterprise who is having crashing issues. Whenever text is highlighted, even just a few words, XMetaL crashes.

Any insight to a workaround or settings adjustment to resolve this would be helpful.


 on: May 22, 2019, 08:34:53 AM 
Started by dmurphy - Last post by dmurphy
Hi Derek - Sorry, I should have mentioned that in the beginning. We are using an SDL CMS. We use SuiteHelp 4 output type, which does not support DITA 1.3. I guess SuiteHelp 5 does support it.

 on: May 21, 2019, 06:34:42 PM 
Started by dmurphy - Last post by Derek Read
In case this is actually a concern for some reason, the DITA 1.2 spec lists it as an #IMPLIED attribute (and the DTD that I have shows it that way as well).

That suggests to me that the DTD being picked up for you (DITA-1.2/technicalContent/dtd/ditabase.dtd), which will be relative to the XML file at that location (ie: in a subfolder called DITA-1.2), defines this attribute as #REQUIRED.

But, if you are using the following DOCTYPE then (by default at least) you should be getting the DTDs that are installed with XMetaL Author provided there is no DTD named "reference.dtd in the same folder as the XML file (which I would expect is the case): <!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">

However, if a CMS is involved then it could be that nothing I've said above applies as CMS integrations often change where DTDs are loaded from by customizing XMetaL Author's behaviour through configuration and scripting.

 on: May 21, 2019, 06:15:32 PM 
Started by dmurphy - Last post by Derek Read
I guess the error "invalid against DTD error" must be coming from some 3rd party (outside of XMetaL Author) system?

Can I assume you have XMetaL Author integrated with something else like a CMS?

If so, then I guess you should check with the people running it to be sure you are meeting any input requirements. It sounds you have done that (ie: must use DITA 1.2) but just in case there are others I'd suggest you confirm.

Still not sure why XMetaL Author would be giving a validation error about rowheader. As far as I can tell it has never been a required attribute (from DITA 1.x through 1.3). That suggests there is some other DTD involved here that has it set to #REQUIRED.

 on: May 21, 2019, 04:27:48 PM 
Started by dmurphy - Last post by dmurphy
Derek - I have a solution for this. We cannot use DITA 1.3 yet because the custom output we use does not support DITA 1.3. I didn't know about the default setting for DITA version in XMetaL. After switching from DITA 1.3 to 1.2 in Tools > DITA Options, no more errors about rowheaders in tables!


 on: May 21, 2019, 02:19:36 PM 
Started by dmurphy - Last post by dmurphy
Thanks for the reply, Derek. If I double-the error while in Plain Text view, it takes me to the colspec element. If I insert rowheader="norowheader" into each of the colspec elements, I do not get the errors anymore. But when I try to save or check it in, it throws an "invalid against DTD error."

We do not use a specialized DTD. However, I noticed that in the topic that has the errors, the DOCTYPE line is this:

<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA 1.2 Composite//EN" "DITA-1.2/technicalContent/dtd/ditabase.dtd">

But in a newly created topic, it is this:

<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">

If I create a new topic, copy all content from the topic that has the errors, and paste it into the new topic, it does not report the "rowheader" errors. But if I change the DTD reference in the topic with the errors, to the one from the new topic, it still has the errors.

So I believe you're right, it's a DTD issue, but I just can't figure out how to resolve it. I don't want to just create topics and copy all content into those because we would lose all of the versioning info for the topics (we use a CMS).

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