Difference between revisions of "AutoCorrect Options - Localized Options"
(→Abstract) |
|||
| Line 9: | Line 9: | ||
<div style="padding: 5px 5px 5px 15px; width: 480px; padding: 10px;"> | <div style="padding: 5px 5px 5px 15px; width: 480px; padding: 10px;"> | ||
Some AutoCorrect options under ''Tools - AutoCorrect Options - Options'' are language dependant.<br> | Some AutoCorrect options under ''Tools - AutoCorrect Options - Options'' are language dependant.<br> | ||
| − | Either they are specific to one language like the insertion of a space before some punctuation marks (See: [[Non_Breaking_Spaces_Before_Punctuation_In_French_%28espaces_ins%C3%A9cables%29|Non Breaking Spaces Before Punctuation In French (espaces insécables)]]) or the correction they execute differs depending of the current language like the formatting of ordinal numbers (See: [[Localized_AutoCorrection_of_Ordinal_Numbers_%281st_2nd%29 | Localized AutoCorrection of Ordinal Numbers (1st 2nd)]]) or the use of custom quotes. | + | Either they are specific to one language like the insertion of a space before some punctuation marks in French (See: [[Non_Breaking_Spaces_Before_Punctuation_In_French_%28espaces_ins%C3%A9cables%29|Non Breaking Spaces Before Punctuation In French (espaces insécables)]]) or the correction they execute differs depending of the current language like the formatting of ordinal numbers (See: [[Localized_AutoCorrection_of_Ordinal_Numbers_%281st_2nd%29 | Localized AutoCorrection of Ordinal Numbers (1st 2nd)]]) or the use of custom quotes. |
Therefore those options have to be grouped into one tabpage which contents varies depending of the current language. | Therefore those options have to be grouped into one tabpage which contents varies depending of the current language. | ||
Revision as of 01:09, 16 January 2010
Abstract
Some AutoCorrect options under Tools - AutoCorrect Options - Options are language dependant.
Either they are specific to one language like the insertion of a space before some punctuation marks in French (See: Non Breaking Spaces Before Punctuation In French (espaces insécables)) or the correction they execute differs depending of the current language like the formatting of ordinal numbers (See: Localized AutoCorrection of Ordinal Numbers (1st 2nd)) or the use of custom quotes.
Therefore those options have to be grouped into one tabpage which contents varies depending of the current language.
References
| Reference Document | Check | Location (URL) |
| Prerequisites | [passed/failed] | n/a |
| Product Requirement, RFE, Issue ID (required) | [available/not available] | <PLEASE ENTER LOCATION HERE> |
| Accessibility Check (required) | See accessibility section for check list | |
| Test case specification (required) | [available/not available] | <PLEASE ENTER LOCATION HERE> |
| IDL Specification | [available/not available] | <PLEASE ENTER LOCATION HERE> |
| Software Specification Rules | n/a | n/a |
| Other, e.g. references to related specs, Product Concept Document | <PLEASE ENTER LOCATION HERE> |
Contacts
| Role | Name | E-Mail Address |
| Developer | Cédric Bosdonnat | cedricbosdo@openoffice.org |
| Quality Assurance | Éric Savary | es@openoffice.org |
| Documentation | Uwe Fischer | ufi@openoffice.org |
| User Experience | Cédric Bosdonnat Éric Savary |
cedricbosdo@openoffice.org es@openoffice.org |
Acronyms and Abbreviations
| Acronym / Abbreviation | Definition |
| <WYSIWYG> | <What You See Is What You Get> |
Detailed Specification
<START TYPING HERE> Help | User Interface Element Templates | Example Spec
Accessibility
Accessibility is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:
- Is the feature fully keyboard accessible?
(Ex: "I can go everywhere and use every function using the keyboard only"
<START TYPING HERE> - Have I specified visual alternatives for the case that the specified feature includes audio as output?
<START TYPING HERE> - Are text alternatives for all icons and graphics available?
<Start typing here> - Don't provide important information in colors alone
(Ex: marking important information hard coded in red)
<START TYPING HERE> - Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
<START TYPING HERE> - Have I ensured that flash rates do not exceed 2 hertz for blinking text, objects, or other elements? In any case, try to avoid flashing UI elements
<START TYPING HERE> - Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.
<START TYPING HERE>
QUESTIONS?
If you need help while designing, implementing or testing the accessibility of the UI, ask/visit:
- The accessibility check list at the OpenOffice.org Wiki
- accessibility@ui.openoffice.org (The accessibility mailing lists, preferred)
- For specific implementation details, architecture: mt@openoffice.org (Malte Timmermann)
- For specific UX and testing questions: es@openoffice.org (Éric Savary)
Migration
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
Configuration
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>
| Configuration | Group | Setting | Type | Default | Comment |
| <e.g. Writer.xcs> | <e.g. Print> | <e.g. Empty Pages> | <e.g. Boolean> | <e.g. True> | <e.g. Specifies the default for Empty Pages> |
Help | Configuration Table Template
File Format
<START TYPING HERE --- If this part is irrelevant state a reason for its absence.> Help
Help | File Format Table Template
Open Issues
<State a bulleted list of issues Issue here>
