CDR Tickets

Reassigning to ~volker since OCECDR-5107 was his. You didn't mention whether Check Spelling While Typing was enabled. I am unable to reproduce this failure.

Yes, I should have mentioned that  de-selecting Check Spelling While Typing seems to resolve the problem. Somehow, I thought that this problem was resolved with the upgrade to XMetal 17 but apparently not 🙂.

Yes, if I remember correctly, this problem was "fixed" with the upgrade because XMetaL stopped spell-checking on words longer than N characters (don't remember exactly what value of N was used).  That function prevented the crash.

I'm wondering what has changed.

~oseipokuw , could you please add the path (or a screenshot showing) the dictionaries included for the installation that is crashing?

Hi Volker,

The path is   L: \OCPL_Cross\CDR\STEDMANS

~oseipokuw, has the document been modified to remove the long URL?  I don't see it in the document and - needless to say - my XMetaL doesn't crash.

I need to make sure I'm testing with the same version that is causing the crash.

OK, I see the crash now on the previous version which does have the long URL.

~oseipokuw, could you please send me a screenshot of the dictionaries used?

Go to Tools -> Spell Checker..., Click Options -> Main Word Lists

I need to see all the dictionaries in use when XMetaL crashes.

~bkline, since you're XMetaL does not crash, would you be able to get me that information, too?

WT10EM.MOR (see Screenshot 2024-03-07 at 6.23.04 PM).

Thank you, Bob!  This is the default dictionary, just as I expected.

I submitted a service ticket on Thursday and received an automated response that it was received and an engineer "will contact you shortly".

Still waiting for someone to contact me.

I couldn't update the ticket due to the Jira upgrade last week.  Here is the ticket I had submitted to Just Systems:

I am using a standard 64-bit installation on a Windows workstation without any customization.  I need to be able to add additional dictionaries for spell checking but XMetaL is crashing after adding a dictionary file and spellchecking the document. 

The crash is reproducible as follows:

• with a standard installation of XMetaL 17.0, open the template "Meeting.xml" (select "Edit as partial document")

• Edit the text of the Notes element

• With the XMetaL option "Check spelling while typing" enabled, enter a long bogus word, like "abcdefghij". This word will be underlines with red quiggly lines.

• Continue expanding this word to make it 64 characters long.  At this point the quiggly lines will disappear because the spellchecker will not check words longer than this.  

• Continue expanding the word up to 80+ characters without any problem.

This is the default behavior.
Next, attach a dictionary file that is in the *.dic format.  It does not matter if this file is empty, small or large.  I tested with a file having 0 entries, 1 entry or 40,000+ entries.  The result is the same.

• After attaching the *.dic file to the "Main Word Lists..." repeat entering a bogus word

• The word "abcdefghij" will be displayed with squiggly lines as misspelled

• When expanding the word past 64 characters the squiggly line does not always disappear (indicating the stop of spellchecking for this word)

• When expanding the word to 80+ characters, XMetaL will crash

Following the above procedure after including a *.lex dictionary will not cause XMetaL to crash, only when adding a *.dic file does the application crash.

This is a problem because our users often include URLs that are longer than 80 characters in the document. When XMetaL has been setup to spellcheck while typing such a word/URL is spellchecked and therefore causing a crash after loading the document.

Please let me know if you need additional information.

Just Systems responded and provided an updated DLL file to try out.  I've been able to test XMetaL with that new file and couldn't recreate a crash.  The result has been reported back.  We now have to wait for Just Systems to provide us with a new installation file.

Successfully installed on two new laptops and tested for crashes successfully. This is in addition to installing on several other existing laptops. Closing this ticket. Thanks!