Difference between revisions of "Non Breaking Spaces Before Punctuation In French (espaces insécables)"
(→Abstract) |
(→Abstract) |
||
| Line 24: | Line 24: | ||
== Abstract == | == Abstract == | ||
| − | In French language, some punctuation signs like ; : ! ? need to have a (non breaking) space between them and the word placed before them. | + | In French language, some punctuation signs like ; : ! ? need to have a (non breaking) space between them and the word placed before them.<br> |
The current specification describes the automatic insertion of the those spaces over the AutoCorrect Options. | The current specification describes the automatic insertion of the those spaces over the AutoCorrect Options. | ||
Revision as of 15:16, 15 September 2009
This specification is still in discussion.
Please read the Brain-Storming section.
You can also follow the discussion in French on dev@fr.openoffice.org.
Brain-Storming
ES: the goal is to make a balance between "everything we can make perfect" and help as many people as possible who are missing this feature.
- Provocative: Why do we implement this as a core feature while there's already a working extension for this (http://extensions.services.openoffice.org/project/insecable)?
Note: This extension only works for Writer. - Scope: "French". In which country? France, Switzerland, Belgium, Quebec, others? Which references should we have?
- Use always a simple non breaking space (HTML:  ) or follow the subtle differentiations of the French typography rules using a so called "thin space" (espace fine) (HTML: &thinsp - which is a BREAKING space!) depending of the case?
Note: MS-Word seems to (always) use the thin space...- And then re-work the implementation of "Tools - AutoCorrect Options - Custom Quotes" when French is the current character language?
- Shouldn't we avoid to through a very language specific feature into the general AutoCorrect Options dialog? Create a new localized tab page?
References: http://unicode.org/udhr/n/notes_fra.html
Abstract
In French language, some punctuation signs like ; : ! ? need to have a (non breaking) space between them and the word placed before them.
The current specification describes the automatic insertion of the those spaces over the AutoCorrect Options.
Contents
References
| Reference Document | Check | Location (URL) |
| Prerequisites | [passed/failed] | n/a |
| Product Requirement, RFE, Issue ID (required) | [available/not available] | 17169 |
| Accessibility Check (required) | PASSED | |
| 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"
Does not apply - Have I specified visual alternatives for the case that the specified feature includes audio as output?
Does not apply - Are text alternatives for all icons and graphics available?
Does not apply - Don't provide important information in colors alone
(Ex: marking important information hard coded in red)
Does not apply - Does the specified feature respect system settings for font, size, and color for all windows and user interface elements?
Does not apply - 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 - 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:
- 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.>
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>
