Spelling in livelink

Hello allDoes anyone know whether it is possible to add dictionaries of languages other than English to livelink spelling? If so, what format do they need to be and how can this be done? Any help would be greately appreciated. Thank you in advance!Ys

Find more posts tagged with

Comments

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Yes it is possible to add other dictionaries to Livelink.

Currently I haven't figured it out yet if it is possible to support multiple spelling checkers in one Livelink install.

I'm currently working on it my self also, so please also post anything you discover yourself.

To replace the English spell checker in the English Livelink version with your own dictionary:

1. Obtain a dictionary from WinterTree (http://www.wintertree-software.com/)

2. replace {ssceam2.clx, ssceam.tlx} in OTHOME with the files from you language

3. In case you also need to change the user interface of the applet, you need to change messages.properties in the spellchecker.jar file.

What I'm still going to try is to change the spellcheckerUSA.properties file in spellchecker.jar to point to my language files. In that case I don't need to replace the dictionary files in the Livelink install directory, but can just add my own.

The WinterTree applet seem to support the following PARAMs:

These are not supported by the Livelink applet.

If you want to support multiple languages within 1 Livelink installation, I can see the following possible solutions:

1. Register a bug/change request with Open Text support and tell them the Livelink applet doesn't support the MainLexicon{1,2} parameters and wait until it gets changed.

2. Create a different jar for each language with the proper settings in the properties files in the jar file.

3. Use the WinterTree applet directly.

In all cases you need to change the webLingo files that make use of spellchecker.jar. Just do a search for HTML files with spellchecker.jar in them.

Don't change the webLingo files themselves but make use of the HTMLmap functionality in CustomizationsRT to replace them.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 14 februari 2005 8:42
To: eLink Recipient
Subject: Spelling in livelink

Spelling in livelink Posted by ap_stavzeti (Zeti, Stavroula) on 02/14/2005 02:41 AM

Hello all

Does anyone know whether it is possible to add dictionaries of languages other than English to livelink spelling? If so, what format do they need to be and how can this be done? Any help would be greately appreciated. Thank you in advance!

Ys

ATHANASSIOS_FAMELIARIS

I agree Hans. I looked in the spellchecker.jar and noticed the .properties files too. I still don't know exactly how the tlx files are used, since there are no ssceam2.tlx files in OTHOME. There is only one tlx per language, ie ssceam.tlx, sscefr.tlx, etc. I've also noticed that there is a correct.tlx . This is used to replace some words atomatically and I think it is not necessary.Also, I went to wintertree's site and found this url:http://www.wintertree-software.com/dev/spellcheckapplet/technical.htmlThis contains something like an API for their applet which includes a method for adding dictionaries. However, Opentext must be using some other versions as the only methods one can call are show() and userCanceled(). I think that if one appends a word list to ssceam.tlx, the new words will be recognised. However, I wonder how it will recognise upper case and intonation. Any ideas?

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

For each language there is a .tlx and .clx file in the OTHOME\support directory. Sorry for the error in my previous message.

When I look at the jar file, I see that we also have our own Java code. So I expect we have our own applet, but I'm not a java programmer, so I can be wrong.

Currently I've changed my method of working. I no longer replace the ssceam2.tlx and ssceam.clx file. I just copy my own language files to OTHOME\support. Then I change the SpellCheckerUSA.properties file to point to my language files and not the American ones.

I don't know how upper case and intonation are recognized. That is probably an answer you need to get from WinterTree.

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: maandag 14 februari 2005 14:01
To: eLink Recipient
Subject: Observations

Observations Posted by ap_stavzeti (Zeti, Stavroula) on 02/14/2005 07:58 AM
In reply to: RE Spelling in livelink Posted by hstoop (Stoop, Hans) on 02/14/2005 03:12 AM

I agree Hans. I looked in the spellchecker.jar and noticed the .properties files too. I still don't know exactly how the tlx files are used, since there are no ssceam2.tlx files in OTHOME. There is only one tlx per language, ie ssceam.tlx, sscefr.tlx, etc.

I've also noticed that there is a correct.tlx . This is used to replace some words atomatically and I think it is not necessary.

Also, I went to wintertree's site and found this url:

http://www.wintertree-software.com/dev/spellcheckapplet/technical.html

This contains something like an API for their applet which includes a method for adding dictionaries. However, Opentext must be using some other versions as the only methods one can call are show() and userCanceled().

I think that if one appends a word list to ssceam.tlx, the new words will be recognised. However, I wonder how it will recognise upper case and intonation. Any ideas?

ATHANASSIOS_FAMELIARIS

I wrote to wintertree and, naturally, they said I should ask Opentext for support and they will support Opentext. In the meantime, Opentext support (great as usual) has not replied yet.On another note, the sscefr.tlx file contains the lexicon apparently. If the SpellCheckerUSA.properties points to another file, then you loose the english spelling, don't you?This is why I think that appending is the best choice. It worked for me, and somehow it does understand upper case and some intonation. (What is interesting is that the english lexicon has only about 1000 words? Is this to be expected?)What I still can't figure out is the role of the other files. ssceam2.clx appears to be binary. Do you have any idea what it does? Also, there is an accent.tlx which is also a mystery to me.If you have made any progress, please let me know. Thanks!

eLink User

Post has been deleted

Hans_Stoop_(hstoop_(Delete)_1579932)

Message from Hans Stoop <hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

See below.

For extra info, also have a look at http://kiwebline.ki.com/webline/documentation/books/coll_admin/html/spell_checker.htm.

For accent.txl see http://www.wintertree-software.com/support/wintertreespellingserver/curlyapostrophe.html

Hans

From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com]
Sent: woensdag 16 februari 2005 9:24
To: eLink Recipient
Subject: More observations

More observations Posted by ap_stavzeti (Zeti, Stavroula) on 02/16/2005 03:23 AM
In reply to: RE Observations Posted by hstoop (Stoop, Hans) on 02/14/2005 08:38 AM

I wrote to wintertree and, naturally, they said I should ask Opentext for support and they will support Opentext. In the meantime, Opentext support (great as usual) has not replied yet.

On another note, the sscefr.tlx file contains the lexicon apparently. If the SpellCheckerUSA.properties points to another file, then you loose the english spelling, don't you?

[hans] Yes

This is why I think that appending is the best choice. It worked for me, and somehow it does understand upper case and some intonation.

[hans] How do you append them? But this will also mean that any English errors, that are correct French words, are not deteced.

(What is interesting is that the english lexicon has only about 1000 words? Is this to be expected?)

What I still can't figure out is the role of the other files. ssceam2.clx appears to be binary. Do you have any idea what it does? Also, there is an accent.tlx which is also a mystery to me.

If you have made any progress, please let me know. Thanks!