Issue 2419 - Spellings-checker doesn't recognize: aren't, don't, can't, etc.
Summary: Spellings-checker doesn't recognize: aren't, don't, can't, etc.
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-04 09:18 UTC by brenno
Modified: 2002-11-07 13:40 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description brenno 2001-12-04 09:18:25 UTC
When using the spellingschecker standard sentences like:
* I don't  know
will produce an error. Apparantly the spellingschecker doesn't recognize:
don't, aren't, can't, haven't, etc.
It reads don' and t (as a seperate word).
Comment 1 Unknown 2001-12-04 09:48:04 UTC
Kevin, 

can I re-assign this to you? 

Armin
Comment 2 thomas.lange 2001-12-04 10:51:02 UTC
This is no problem of Kevin.
It's the wordbreak-iterator.
This bug is double to some bug that is already fixed by now.
MRU is familiar with that bug.

TL->MRU: please confirm and close.
Comment 3 brenno 2001-12-04 11:07:35 UTC
Please don't close this too soon! I waited deliberately until the 641
release before reporting this. In this release it wasn't solved yet.
btw compliments on the rapid response.
Comment 4 thomas.lange 2001-12-04 14:21:57 UTC
It should be functional in SRC 641 Q or higher that is build number 
7565 or higher. (Or maybe one minor version earlier.)

->Brenno: Probably your build is older than that.
Try the dialog "Help / About ...Office" and press CTRL-S, CTRL-D, 
CTRL-T. The window content should start to scroll and the first thing 
to be displayed will be the version and build number.
Comment 5 brenno 2001-12-04 15:37:22 UTC
Okay I checked and my version is 641h build 7454
Comment 6 michael.ruess 2001-12-10 14:38:23 UTC
Yes, unfortunately this was fixed after 641h. It will be built in with
the next OpenOffice release (I tested an internal 641-build).
Comment 7 michael.ruess 2002-11-07 13:40:53 UTC
Will work with openOffice 1.0.1