AutoCorrect Options - Localized Options

From Apache OpenOffice Wiki
Revision as of 22:23, 15 January 2010 by TJFrazier (Talk | contribs)

Jump to: navigation, search


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 (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.


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>


Role Name E-Mail Address
Developer Cédric Bosdonnat
Quality Assurance Éric Savary
Documentation Uwe Fischer
User Experience Cédric Bosdonnat
Éric Savary

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 is the responsibility of the I-Team, beginning with UX, DEV and QA, to ensure that the following requirements are fulfilled:

  1. Is the feature fully keyboard accessible?
    (Ex: "I can go everywhere and use every function using the keyboard only"

  2. Have I specified visual alternatives for the case that the specified feature includes audio as output?
  3. Are text alternatives for all icons and graphics available?
    <Start typing here>
  4. Don't provide important information in colors alone
    (Ex: marking important information hard coded in red)

  5. Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
  6. 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
  7. Ensure that assistive technology (AT) (like ZoomText or Orca) is able to read everything.


If you need help while designing, implementing or testing the accessibility of the UI, ask/visit:

  1. The accessibility check list at the Wiki
  2. (The accessibility mailing lists, preferred)
  3. For specific implementation details, architecture: (Malte Timmermann)
  4. For specific UX and testing questions: (Éric Savary)


<START TYPING HERE --- If this part is irrelevant state a reason for its absence.>


<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>

Personal tools