Localized AutoCorrection of Ordinal Numbers (1st 2nd)

From Apache OpenOffice Wiki
Revision as of 11:44, 16 January 2010 by Es (Talk | contribs)

Jump to: navigation, search

This specification is still in discussion.

Abstract

When typing 1st or 2nd in English, the ordinal suffix "st" and "nd"

References

Reference Document Check Location (URL)
Prerequisites <PLEASE ENTER LOCATION HERE>
Product Requirement, RFE, Issue ID (required) AVAILABLE 20348
Accessibility Check (required) <PLEASE ENTER LOCATION HERE>
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

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 IN PROGRESS!!!

Scope

The AutoFormat of ordinal numbers suffixes (Ex: 1st) formats accordingly to the character language and follows the grammatical rules and exceptions of the current language. This function is localized (Dutch, French, Italian, Portuguese and Spanish) and its behavior (Bug fix in English) and user interface will be improved.

General Behavior

The auto superscript of ordinal numbers only works if the language set under “Format – Character” knows this formatting.

Ex: "1st", "1er" will remain unformatted if the character language is German or Spanish for German does not know suffixes for ordinal numbers and because "1s" and "1er" are not Spanish suffixes.

Here is a sum up of the behavior of this function depending on which languages are installed/active:


1. “Is the language set to the current character installed”?

a) YES: go to 2.

b) NO: go to 2.b)

2. “Does the current character language supports ordinal numbers formatting?”

a) YES: apply replacement algorithm

b) NO: do nothing

A not installed language has the same impact on this feature then an installed language which doesn't support this feature: nothing happens.

Localization of the ordinal numbers

Dutch

Rule:

Accept superscript of “e”

Exceptions:

No grammatical check or exception depending on the digit(s) preceding the ordinal notation.

Particularity:

None


French

Rule:

Accept superscript of “e” and “es” after any number

Exceptions:

After “1” (as number! Not as last digit of another number!), accept to superscript only: “er”, “ers”, “re”, “res”

Particularity:

- Accept to superscript “ième” and “ièmes” after the letters “n” and “x”. (can be done using the replacement table of the AutoCorrection)

So replace:

Typed Formatted
nième nième
nièmes nièmes
xième xième
xièmes xièmes


Italian

Rules:

Accept superscript of “a”, “e”, “i”, “o” from 1 to 10

Accept following superscripts AND transformations for any number after 10:

Example:

Typed Formatted
11esimo 11o
11esima 11a
11esimi 11i
11esime 11e

Exceptions:

No grammatical check or exception depending on the digit(s) preceding the ordinal notation.



Portuguese

TBD


Spanish

Rule:

Accept superscript of “a”, “as”, “er”, “o”, “os”

Exceptions:

No grammatical check or exception depending on the digit(s) preceding the ordinal notation.

Particularity:

Accept superscript also “er” for 1 and 3 (as number! Not as digit)


Improvement of the AutoFormat of English ordinal numbers

Rule:

Accept superscript of “th”only, for all numbers

Exceptions ('~' stands for 'other digit(s), if any'):


Typed Formatted
~1st ~1st
~2nd ~2nd
~3rd ~3rd

Exceptions to the above exceptions:


Typed Formatted
~11th ~11th
~12th ~12th
~13th ~13th

UI

Option under "Tools - AutoCorrect - Localized Options"
Default: ON.

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:

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

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

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

QUESTIONS?

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

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

Documentation

Context:
Help called on "Tools - AutoCorrect - Localized Options - Replace 1st, 2nd"

Content:
TBD

Migration

Does not apply.

Configuration

Remember the option "Tools - AutoCorrect - Localized Options - Replace 1st, 2nd" when updating.

File Format

Does not apply.

Open Issues

<State a bulleted list of issues Issue here>

Personal tools