Pages: « 1 2 3 4 5 6 7 8 9 10 »
 41 
 on: July 12, 2018, 11:09:00 AM 
Started by smm735 - Last post by Derek Read
Please contact the JustSystems sales people.

In general you need to go through them to get any XMetaL software other than the current release of XMetaL Author Enterprise which runs in trial mode by default, so it's used for evaluations (licenses are still provided by the sales team). There is no trial mode for XMAX so we do not make it readily available.

 42 
 on: July 11, 2018, 01:24:18 PM 
Started by smm735 - Last post by Derek Read
Please contact the JustSystems sales department to obtain any version of any XMetaL software. They will provide everything: EULA, download, and license file.

 43 
 on: July 11, 2018, 10:05:00 AM 
Started by smm735 - Last post by smm735
Thanks Derek,

Just curious how I would get the latest release/build of XMax?  The website seems to indicate that XMax 11 is the latest release.  We were provided with 11.0.0.084 but you mentioned using 11.0.0.091 and I'm not sure how to obtain different binaries.  The Downloads page has 2 options - both for XMetaL Author, nothing for XMax.

I see that XMetal Author is at v13 but we are not using Author - just XMax.


 44 
 on: July 11, 2018, 08:40:39 AM 
Started by smm735 - Last post by smm735
Hello,

We have just upgraded from Xmax 7 to XMax 11.0.0.084 and are using Windows 10 Enterprise workstations.

We install xmax as follows:  xmforactivex.exe" /s /v"/qn ALLUSERS=1

Following installation we see that the Writing Tools are installed in the Corel/Shared/XMetaL/Writing Tools/10 directory, however on some systems the call to IsSpellCheckerInstalled returns true and on others it returns false.

We previously installed v7 using the same logic and did not see this issue.  We have also tried running our application as Admin, however the issue does not go away

I saw other posts regarding the spellChecker not working that indicated a Windows 10 update #1803 may be causing the issue, however this update does not appear to be installed on any of the machines, either working or not working.

Can you offer any hints as to why we might be getting this inconsistent behavior?  I would try to get a newer version of XMax to test with but I'm not sure where to obtain the software - the Downloads page seems to include only XMetal Author Enterprise 13 Trial software...

Thanks,
Sean

 45 
 on: June 30, 2018, 05:23:40 AM 
Started by dduburon - Last post by Wolcott
This explains it. I just recently started using XMetaL again after a long break and I wondered the same thing. I guess I'm going to update. Cheers Derek.

 46 
 on: June 27, 2018, 02:48:52 PM 
Started by smm735 - Last post by Derek Read
My first recommendation would be to try the current release.

If this was a bug in 11.0.0.084 I think it must require a specific setup to reproduce. I am unable to reproduce the issue in 11.0.0.084, 11.0.0.091 and 13.0.0.033 (current release).

Here is my test script:

Code:
//XMetaL Script Language JScript:
Selection.InsertCALSTable(2, 2, "table", true, false);
ActiveDocument.Host.Alert(ActiveDocument.xml);

This also gives me the expected results:

Code:
//XMetaL Script Language JScript:
Selection.InsertCALSTable(2, 2, "table", true, false);
if (Selection.InContextOfType("TABLE")) {
  if (Selection.MoveToElement("table",false)) {
    Selection.SelectElement();
    ActiveDocument.Host.Alert(Selection.Text);
  }
}

As does switching to Plain Text view and viewing the XML source.
Selecting the table, copying it to the clipboard, and pasting that into a text editor also gives me the correct results.

What do you see in Plain Text view?

Presumably in your case XMAX is also giving you validation errors?
If not, does the schema define an @Desc?


I'm trying to figure out which API is causing the problem for you: ActiveDocument.xml or InsertCALSTable.
Ultimately we will need to reproduce this though.

If you can reproduce this issue with 13 please let XMetaL Support know. The issue does not appear to be reproducible with a schema that supports the standard CALS table model, so if it requires a specific DTD or XSD to reproduce the issue please provide the files needed when you submit the support case.

 47 
 on: June 26, 2018, 02:23:51 PM 
Started by smm735 - Last post by smm735
Hi,

We have recently begun using XMax 11.0.0.084

When I call AxXmetaLControlLib.AxXMetaLControl.Selection.InsertCALSTable(2, 2, "table", True, False)  and then immediately read AxXmetaLControlLib.AxXMetaLControl.Document.xml the latter property contains the xml for my new table but looks like this:

<?xml version="1.0"?>
<table>
  <tgroup cols="cols-value" Desc="2">
    <colspec charoff="1" colnum="col1" colname="*"/>
    <colspec charoff="2" colnum="col2" colname="*"/>
    <thead>
      <row>
        <entry valign="col1">test</entry>
        <entry valign="col2">test</entry>
      </row>
    </thead>
    <tbody>
      <row>
        <entry valign="col1">test</entry>
        <entry valign="col2">test</entry>
      </row>
      <row>
        <entry valign="col1">test</entry>
        <entry valign="col2">test</entry>
      </row>
    </tbody>
  </tgroup>
</table>

More importantly, the tgroup element contains what appears to be an invalid attribute "Desc" and I don't understand why the "cols" attribute is set to "cols-value" instead of 2.  Subsequent processing chokes on the tgroup element as it does not like either the "Desc" attribute or the "cols-value" value for the "cols" attribute.

When I switch to XMax 7 (our previous version) and make the same call the xml looks like this:

<?xml version="1.0"?>
<table>
  <tgroup cols="2">
    <colspec colnum="1" colname="col1" colwidth="*"/>
    <colspec colnum="2" colname="col2" colwidth="*"/>
    <thead>
      <row>
        <entry colname="col1">test</entry>
        <entry colname="col2">test</entry>
      </row>
    </thead>
    <tbody>
      <row>
        <entry colname="col1">test</entry>
        <entry colname="col2">test</entry>
      </row>
      <row>
        <entry colname="col1">test</entry>
        <entry colname="col2">test</entry>
      </row>
    </tbody>
  </tgroup>
</table>

Any thoughts or suggestions on why I may be seeing this? 

Thanks,
Sean

 48 
 on: June 18, 2018, 05:18:36 AM 
Started by s. anderson - Last post by shepPettibone
It seems like no chance to me to do so when it was the 8, they did a lot of improvements on that in the 10th release. Back then, I tried to do this and that for several times ended up with the soft turned to garbage 3 days after. So I called it a day and edited that PDF through this tool https://w9.pdffiller.com just because I don't know, you upload it, put your media where you want and it's done

 49 
 on: June 08, 2018, 03:18:37 PM 
Started by dduburon - Last post by Derek Read
The server no longer exists. It was phased out then shut down entirely in January 2017.

You have two options:

1. Upgrade to a more recent version. Versions 9 through 13 (current release) use a newer licensing system that does not rely on that obsolete (and very buggy) licensing server. The JustSystems sales team can provide everything you need. It is best to upgrade to the current release unless you have 3rd party software that requires a specific version of XMetaL Author Enterprise. Upgrades are included with the maintenance fees you are paying.

2. If you must use this old version for some reason please contact XMetaL Support.

If you need to run XMetaL Author Enterprise on Windows 8.1 or 10 you will need to upgrade to version 11 or higher as version 11 was the first to support these versions of Windows.

 50 
 on: June 08, 2018, 03:05:43 PM 
Started by 55 - Last post by Derek Read
If you are working with XML then this means your DTD declares elements using uppercase names. To change this you would need to alter the DTD to declare elements using the text case you want them to be in (then adjust the XML to match so that the XML is valid).

If this is an SGML document, and the SGML DTD declares your elements using a case other than uppercase (lowercase or some mixture of upper and lowercase) then check to see if the SGML declarations file includes the naming rule "NAMECASE GENERAL YES", check to see if there is no NAMECASE naming rule (the default for this rule is "YES"), and check to see if there is no declarations file. If so, then element names will be displayed and saved in uppercase. To fix this, confirm that the DTD declares element names in something other than uppercase, that there is a declarations file, and that "NAMECASE GENERAL NO" is present.

If that is the case, and element names still appear in uppercase, then most likely you have run into the same issue reported to XMetaL Support last year where a client was expecting declarations files using the file extension .dcl to be supported by XMetaL Author Essential (it is suspected this is because Arbortext used this for its SGML declarations files whereas XMetaL has always used .dec).

In this case you have two possible options:
1. Check to see that the declarations file has the same file name as the DTD and a .dec file extension (ie: mySGMLDTD.dtd + mySGMLDTD.dec). If that doesn't work, or isn't acceptable for your environment...
2. Install XMetaL Author Essential 13.0.0.029 (current release as of this posting). This version supports SGML declarations files named using either .dec or .dcl file extensions (the file name itself still needs to match the DTD's file name and be in the same folder as the DTD). The internal file format of the SGML declarations file remains unchanged and is still a standard SGML declarations file.

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