Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Optional bell/flash when invalid input sequence entered|
|Component:||code||Assignee:||AOO issues mailing list <issues>|
|Status:||CONFIRMED ---||QA Contact:|
|Priority:||P5 (lowest)||CC:||arthit, hin.stone, issues, jjc, markpeak|
|Issue Type:||FEATURE||Latest Confirmation in:||---|
|Issue Depends on:|
Description samphan 2005-02-14 12:54:45 UTC
OOo supports a feature called sequence input checking or SIC. Its purpose is to reject the input character that would make an invalid combining character sequence. Currently this is only implemented for Thai but theoretically it can be implemented for any language that has the concept of invalid sequence. The problem with the current implementation is: quietly ignoring the input character does not draw the user's attention that there is something wrong. The user may think that the character typed has been entered into the document successfully. Normally, when you type a character that will make a Thai invalid sequence in Windows XP's Notepad, you'll hear a sound. Therefore you know that you may have to do something, e.g. backspace, before you can type the character. In OOo, the users should be able to setup the SIC to sound a bell or flash the window or do nothing, depends, for example, on an option in Tools/Options/Complex Text Layout/Sequence checking.
Comment 1 arthit 2005-02-19 14:03:48 UTC
Feature related to "Accessibility"?
Comment 2 arthit 2005-04-01 23:58:18 UTC
Comment 3 Martin Hollmichel 2005-05-22 07:36:59 UTC
set target to OOo Later.
Comment 4 falko.tesch 2005-10-20 20:54:03 UTC
FT: I'm leaving so I will re-assign this issue to requirement default user
Comment 5 samphan 2006-01-26 09:41:34 UTC
Arthit <- I don't think this is related to Accessibility. I think any Thai would like to have this feature. It prevents lost of input that would be discarded silently by the sequence checker. Even now that OOo has the new feature for Thai called sequence correct (aka type and replace). However, it currently only works in Writer. It make for less input being rejected, but it still reject input that it can't correct. So users should know when any input is rejected. This feature is still needed.
Comment 6 arthit 2006-01-26 12:25:41 UTC
Yes, it would be nice if a user can (optionally) have this feature. I agree. But what I mean is that, should it be more elegant, if there's a way, for OOo, to let the underlying operating system handle all this "effects" ? for example, OOo capture the "invalid sequence" event, and let the OS know that it happens .. and the OS will be the one who decide how to draw attension from the user. Say, if it happens in OOo on Windows, you should hear a very same sound as it has happen in Notepad on Windows in the same machine. Or if the Windows setting for this case is "flash the window", so OOo should flash the window, according to the Windows setting. For a quick implementation, say, within 2.x, we could handle all the effects by OOo itself. But I think for a long-run, like OOo > 2.5 (imaginary version number): - it will be more elegant, in a system design point-of-view, if OOo delegates this to the OS - it will be more user friendly (no unexpectation, lesser setting required), if OOo acts more like a native app