Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Don't understand semantics of check-box to control whether Sequence Input Checking is or is not Restricted | ||
---|---|---|---|
Product: | Internationalization | Reporter: | samphan |
Component: | ui | Assignee: | jjc |
Status: | CLOSED FIXED | QA Contact: | issues@l10n <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | arthit, hin.stone, issues, jjc, markpeak |
Version: | 680m79 | Keywords: | oooqa, usability |
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 41707 |
Description
samphan
2005-02-17 07:33:42 UTC
Confirmed. The textual descriptions on the dialog + their positions make it not clear about the purpose of setting. Does this for a "ui" component? (Instead of "l10n") Proposed solution 1: use radio buttons, like this ------ Sequence Checking ( ) not check ( ) basic check ( ) strict check ------ (note: Solaris 9 use these terms .. level 0 (passthrough), level 1 (basic check), level 2 (strict) ) Optionally, if in the future there's a MS Office's "Type and Replace"-equivalent feature, it can be something like ------ Sequence Checking and Replacing ( ) not check ( ) basic check ( ) strict check [ ] insert or replace an existing character to make a valid sequence ------ where the "insert or replace" checkbox will be enabled only if the 2nd or 3rd radio button is selected. Trying it in the latest snapshot confirms Arthit's guess: "restricted" means use WTT 2.0 strict checking rather than WTT 2.0 basic checking. The simplest improvement would be to replace "Restricted" by "Strict" and fix the help file. That's not ideal because I don't think we can expect users to be familiar with WTT 2.0, so a non-technical explanation of basic vs strict is needed. I would suggest something like this. Basic checking is enough to ensure that the characters in the document can all be displayed: it just checks that the sequence of characters in each cell is valid. Strict checking catches additional illegal input sequences spanning multiple cells, which involve leading or following vowels. Maybe a better question is: why offer the user a choice between basic and strict? I think 99% of the time a user would want strict checking. In the other 1% they can simply turn off input sequence checking. Word always does strict input sequence checking. set target to OOo Later. Block 42661 because this change ("Restricted" to "Strict") should be made when the UI support for sequence error correction is added. FT: James and I agreed on renaming it to "Strict" and having it turned on per default. That's given the current broken implementaion of "Strict" gets fixed. Therefore I remove the dependency on issue 42661 (which again is solved in 48117) FT-James: I hand this back to you since the other dependency is to the Thai-related tracking bug. And I don't think that such relation makes any sense. For me I consider this issue as fixed/closed. mark as fixed as ft suggested. The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew |