Chinese Numbering

OpenOffice.org 2.0

Document - ID	Specification Owner	Last Change	Status
	Falko Tesch	Not yet stared	--
Conforms to	http://www.openoffice.org/issues/show_bug.cgi?id=20131
Applies to	Writer and Impress
Task ID(s)	20131
Category	Feature

Abstract

Chinese numbering system is very formal and complicated, and the software should accurately reflect that numbering system. The current bullets are numerical and should be expanded to include Chinese numbering system.

i-Team Members (The specification Owner is part of the i-Team)

	Name	E-mail Address
User Experience	Falko Tesch	Ft@openoffice.org
Development	Karl Hong	Khong@openoffice.org
Quality Assurance	Ulf Ströhler	Us@openoffice.org
Documentation	Uwe Fischer	Ufi@openoffice.org

Approved for Implementation

	Approved by	Date
User Experience	<Name>	<Date>
Development		
Quality Assurance		
Documentation		
String Review		

Document Change History

Rev. Level	Change	Initials	Date
1.0	First draft	FT	31.03.2004

Contents

Glossary	1

1	Motivation	1

2	User Scenarios	1

3	Goals	1

4	Requirements and Dependencies	1

4.1	Requirements	1

4.2	Technical Dependencies	1

5	Competitive Analyses	1

6	Detailed Specification	1

6.1	Error Conditions	2

7	Future Tasks	2

8	Notes	2

9	References	2

Glossary

Term	Description
<Term 1>	

Motivation

Chinese numbering system is very formal and complicated, and the software should accurately reflect that numbering system. The current bullets are numerical and should be expanded to include Chinese numbering system.

User Scenarios

In China official document need to be in a stric traditional Chinese layout.

With OpenOffice.org it is currently not possible to create a proper numbering according to the needed rules.

Goals

<The goals section must be short but also provide a clear statement of the goals, to achieve with this feature, project or task. A clear statement in this section gives Development, Quality Assurance and Documentation guidance.>

Requirements and Dependencies

Requirements

<State the requirement(s) of this feature here.>

Technical Dependencies

<Are there any technical dependencies for this feature? Does the implementation of this feature create any technical dependencies to other program parts?>

Competitive Analyses

<Describe or reference to solutions which are already on the market. Describe what is done well or what is done bad.>

Detailed Specification

<First of all the concept section should give the audience an overview of how the new feature will work. When this is done this section has to cover the necessary things to finish this feature. This is the crucial part of the specification. If images are used in the concept, it is very important that these images provide a caption. The caption should be short and has to describe shortly the image. UI Mockups has to provide a caption too, if possible the mockups shouldn't be scaled and our standard user interface font, Andale Sans UI has to be used for strings on dialogs.>

<String Lists>

<Dialogs providing strings which have to be translated, have to be accompanied by a table containing the strings used in the image (English or German or both) Strings have to include mnemonics and the item for which the string is used. Mnemonics have to be visualized by a ~ - symbol in front of the letter which has to be displayed mnemonic.>

String list

Item	English	German	Comments
Button	~Delete	~Entfernen	

Tab Order

<If necessary Describe or visualize the tabbing order. The description of the tab order has to contain which control has the initial focus.>

Key Board Shortcuts

<Key Board shortcuts used in dialogs have to be listed in a table with a small description.>

Error Conditions

<List all error conditions, and the action the system takes about them. If an alert box comes up, which kind is it? Include exact text of messages, or say what points need to be covered. Error Messages need a string list>

Future Tasks

<If there are features which couldn't be implemented but have to be implemented in the future. State these in here with a description why the feature couldn't be implemented right now.>

Notes

<Questions will arise during the writing of the specification. State these in here.>

References

<Give references to related documentation, such as engineering designs, technical specs, and other sources for related units. Also include links to documents that other sections in this spec need to refer to, such as user opinions usability test reports.>

Required - Give references to related documentation, such as engineering designs, technical specs, and other sources for related units. Also include links to documents that other sections in this spec need to refer to, such as user opinions usability test reports.

Chinese Numbering

Page 2

http://specs.openoffice.org/g11n/chinese_numbering/chinese_numbering.sxw

Chinese Numbering

Falko Tesch

2004-03-30T13:54:48