Pages: « 1 2 3 4 5 6 7 8 9 10 »
 on: May 07, 2018, 06:27:21 PM 
Started by Marvin - Last post by Derek Read
The "user word list" used by Writing Tools is stored here:

%appdata%\Documents\Corel User Files\XMetaL

That's the default location. You can put the files anywhere on your machine and then tell Writing Tools where a particular file is by adding it to Writing Tools for a particular language using Options > User Word Lists.

That setting is stored in the registry as well.

You can point to up to 10 different files for each language. At least I think it's 10. I can't see any reason or need to go beyond 1 or 2. However, what that means is that you could have a file that all users use, different files for different groups, or a combination of multiple files where some group only needs one and another group might use that one plus additional files. I think in the vast majority of cases a single file is enough for all. However, what this does allow is to have a file you install that does not get updated by the user, and leave their own UWL set as the default so they can add their own words to it (when a user adds words to the spell checker they go into the "default" UWL file).

 on: May 07, 2018, 06:16:47 PM 
Started by Marvin - Last post by Derek Read
I'm not sure that is a good example as the CALS table you have listed here is following the CALS specification. If the DTD you are using to validate your documents follows the CALS spec then XMetaL Author will not catch any validation errors (because this table is valid) and it will also render it with the first cell in both rows merged (as the CALS spec states). See attached image.

So, I guess this does mean this Schematron is performing checks that are specific to some additional rules that are otherwise OK according to the CALS spec?

Are you saying that oXygen flags usage of the @morerows attribute as an issue and that you want to create a Schematron for use with XMetaL Author that tells people not to use the @morerows attribute?

 on: May 07, 2018, 06:56:48 AM 
Started by Marvin - Last post by Marvin
Just one more question:
We'd like to maintain a wordlist for our organization.
What's the recommended way to create such a wordlist and install it on all machines? We use a centralized deployment mechanism, so it's no problem to automatically roll this out to all clients.
Thank you.

 on: May 07, 2018, 05:24:08 AM 
Started by Marvin - Last post by Marvin
Thank you so much!

 on: May 07, 2018, 05:12:09 AM 
Started by Marvin - Last post by Marvin
Here's an example of what we're trying to catch:

<table id="table_04B99EE8BBA24339894A7ACD555448B1">
<tgroup cols="2"><colspec colnum="1" colname="col1"
  colwidth="*"/><colspec colnum="2" colname="col2" colwidth="*"/>
<entry colname="col1" morerows="1">
<entry colname="col2">
<entry colname="col1">
<entry colname="col2">

Because of the "morerows" attribute, there is a collision between two cells.
The Schematron detects this in Oxygen, and we'd like to have the same functionality in XMetaL Author Enterprise 13.

(By the way, there is bug in the forum: When I log in to reply, I can't reply straight away. The forum software tells me that I have to wait for 180 seconds between posting, so it obviously treats the login as posting a reply. When I hit reply again after waiting for a few minutes, it also claims I have already posted that ("You already submitted this post!"), so I have to copy my reply, reload the thread and then paste my reply again.)

 on: May 04, 2018, 02:57:08 PM 
Started by Marvin - Last post by Derek Read
I think I've found the original blog posting that lead you to that Schematron:

From what I'm reading here, that Schematron published by DeltaXML (the one you are trying to use) may work with their own software (I'm not sure) but it sounds experimental given some of the comments and instructions included on the GitHub pages.

The blog post suggests the Schematron is essentially checking CALS table validity (not for some additional "business rules" or non-CALS-standards requirements) so it really sounds redundant to run a CALS table that has been validated in XMetaL Author through an additional validation engine. The XML validating parser in XMetaL Author will catch all validation issues with a CALS table (or any other XML) when comparing it to the proper DTD (or XSD).

If you can let me know what the ultimate end goal is that will help us understand your needs better.

 on: May 04, 2018, 02:33:03 PM 
Started by Marvin - Last post by Derek Read
You could try to debug the Schematron code, but I believe much of what we implemented for Schematron is obfuscated (not by us) so it is likely that would be difficult. Stepping through it should be possible to set up with the right breakpoints in place but making sense of what it is doing would probably be hard.

What is the specific reason for using a Schematron to check the validity of CALS tables?
Given that you can check the validity of any XML using XMetaL Author's XML validation engine (automatically) I assume there must be some specific reason for this redundancy?

 on: May 04, 2018, 02:24:04 PM 
Started by Marvin - Last post by Derek Read
These settings are tracked in the registry here (for the default spell checking engine called "Writing Tools"):

In your case you should see a registry string (REG_SZ) called "DefaultTextDialect" set to "UK" and a key named "UK" with various settings inside it.

Make the changes you need to make in the UI on a test machine then observe what is changed there. That is what you will need to set on other user's machines.

Why Corel? The default spelling engine was created by a company purchased by Corel, and Corel was the owner of XMetaL during the time this particular engine was integrated with XMetaL (around 2001/2002). When Corel sold the XMetaL product line we retained the rights to continue using this "Writing Tools" engine.

A few years ago we implemented support for "Hunspell" a popular 3rd party spell checking engine but as many  "dictionaries" for that engine have specific license terms we do not bundle them. This might be of interest to you if you need detailed control over the content in the dictionary files. See:,3011.0.html

 on: May 04, 2018, 02:17:27 AM 
Started by Marvin - Last post by Marvin
It would be great if someone could have a look at the Schematron.

In the meantime, is there a way for me to debug this? It sounds like the problem is in JavaScript code somewhere, can I somehow break on that exception and debug in Visual Studio?

 on: May 04, 2018, 01:38:53 AM 
Started by Marvin - Last post by Marvin
Is there some way to achieve this by editing a configuration file/registry setting, or by using a macro that would be run on startup?

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