[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2152.0. "Spell checking long words under Windows NT" by ZUR01::TOLBA () Thu Apr 24 1997 09:57

Hello,

Customer discovered problems with Spell Checking of long words.
TeamLinks Mail V2.7-1 (english), Windows NT V4.0

Example:
--------
this_is_very_long_message_to_show_the_problem_with_the_spell ing_c hecker


If the above line will be spell checked und Windows 95 it works ok i.e. 
the words this_is_very_long_message_to_show_the_problem_with_the_spell &
ing_c are not known and for the word hecker there are given some alternatives.

Under Windows NT V4.0 or V4.0-2 the first long word:
this_is_very_long_message_to_show_the_problem_with_the_spell
will be automatically replaced through �����������........... characters.

The problem has been reported by Hofmann-La Roche Switzerland. Obviously they 
are using long name expressions from the pharma industrie and for them this 
spell checking problem 'or restriction?' is really very unpleasant.

Is this problem known? Are there any workarounds available beside not using 
spell check under Windows NT? Shall I open an IPMT for this?


Thanks for your feedback and kind regards,
Manuela Tolba, CSC-R�mlang/Switzerland


T.RTitleUserPersonal
Name
DateLines
2152.1Do the spell checking in RTF modebachlr.zko.dec.com::tamara::hoveyThu Apr 24 1997 16:3313
I've reproduced the problem.

NT is handled differently due to some problems with the RTF editor in
text mode on NT.

My only suggestion at the moment is to flip the create message editor
to RTF when doing the spell check and flip it back when done.

Note that I don't think your example will work as you describe because
words longer that 64 characters are skipped; but I still see what you 
mean about very long words being a problem.

This is bug report PTR 11-3-1382 on TeamLinks 3.0 EFT1.