Pages: « 1 2 3 4 5 6 7 8 9 10 »
 11 
 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

 12 
 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.

 13 
 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.

 14 
 on: June 07, 2018, 11:18:41 PM 
Started by 55 - Last post by 55
Hi,

I am sure this is a simple fix...I am running Xmetal 12 Author Essential (I upgraded over the top of Xmetal 11) and all tags and attributes are displaying in uppercase. How do I fix this?
Thanks!

 15 
 on: June 06, 2018, 06:00:50 PM 
Started by 55 - Last post by 55
Xmetal 12 appears to have fixed the spellcheck !!

 16 
 on: June 05, 2018, 10:42:19 PM 
Started by 55 - Last post by 55
I installed KB4100403 but it didn't rectify anything for me.

I'll see if Xmetal 12 works because I can't rollback anymore

 17 
 on: May 31, 2018, 03:01:20 PM 
Started by 55 - Last post by Derek Read
I'm unable to reproduce the issue even with "Windows 10 Versions 1803". It could be that Microsoft has altered the update, or it could be that the additional updates they installed at the same time corrected the problem. The only one that appears to be relevant (specific to Windows operations only) is KB4100403.

I've tried removing that update but so far Windows seems pretty adamant that it reinstall it again when I reboot my machine after uninstalling, so I cannot confirm if just updating to version 1803 triggers the issue, or whether having KB4100403 installed corrects it.

 18 
 on: May 31, 2018, 02:07:05 PM 
Started by 55 - Last post by Derek Read
Apparently Microsoft deletes the files required to roll back after 10 days, forcing you to keep update 1803. Something to keep in mind before installing this Windows update.

 19 
 on: May 31, 2018, 01:45:24 PM 
Started by 55 - Last post by Derek Read
Googling a little bit suggests that Windows update 1803 is causing a lot issues for some people, so unless there is a specific feature in there that you need it might be best to roll back and wait to see if Microsoft's next major update (or a patch for this one) doesn't break the spell checker before rolling it out to all users.

 20 
 on: May 31, 2018, 01:41:01 PM 
Started by 55 - Last post by Derek Read
I'll have a look and see if I can reproduce the issue.

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