DOC TYPE:

Expert contribution

TITLE:

Proposal to change glyph shape for U+066C ARABIC THOUSANDS SEPARATOR

SOURCE:

Paul Nelson (Redmond, WA, USA), Assem Hijazi (Dubai), Aiman Copty (Redmond, WA, USA)

PROJECT:

STATUS:

Proposal

ACTION ID:

FYI

DUE DATE:

--

DISTRIBUTION:

Worldwide

MEDIUM:

Paper and web

NO. OF PAGES:

A. Administrative

1. Title

Proposal to change glyph shape for U+006C ARABIC THOUSANDS SEPARATOR

2. Requester’s name

Paul Nelson (Redmond, WA, USA), Assem Hijazi (Dubai), Aiman Copty (Redmond, WA, USA)

3. Requester type

Expert request.

4. Submission date

2000-04-07

5. Requester’s reference

6a. Completion

This is a complete proposal.

6b. More information to be provided?

Only as required for clarification.

B. Technical – General

1a. New script? Name?

No.

1b. Addition of characters to existing block? Name?

No

2. Number of characters

1

3. Proposed category

4. Proposed level of implementation and rationale

5a. Character names included in proposal?

Yes.

5b. Character names in accordance with guidelines?

Yes.

5c. Character shapes reviewable?

Yes.

6a. Who will provide computerized font?

Microsoft.

6b. Font currently available?

Yes.

6c. Font format?

TrueType.

7a. Are references (to other character sets, dictionaries, descriptive texts, etc.) provided?

No

7b. Are published examples (such as samples from newspapers, magazines, or other sources) of use of proposed characters attached?

Yes.

8. Does the proposal address other aspects of character data processing?

 No

C. Technical – Justification

1. Contact with the user community?

Yes. Assem Hijazi is support manager for Microsoft Middle East.

2. Information on the user community?

Native.

3a. The context of use for the proposed characters?

Arabic block scripts (Arabic, Farsi, Urdu, …)

3b. Reference

4a. Proposed characters in current use?

Yes.

4b. Where?

Worldwide.

5a. Characters should be encoded entirely in BMP?

N/A

5b. Rationale

6. Should characters be kept in a continuous range?

N/A

7a. Can the characters be considered a presentation form of an existing character or character sequence?

N/A

7b. Where?

7c. Reference

8a. Can any of the characters be considered to be similar (in appearance or function) to an existing character?

N/A

8b. Where?

8c. Reference

9a. Combining characters or use of composite sequences included?

N/A.

9b. List of composite sequences and their corresponding glyph images provided?

N/A.

10. Characters with any special properties such as control function, etc. included?

N/A

D. SC2/WG2 Administrative

To be completed by SC2/WG2

1. Relevant SC 2/WG 2 document numbers:

2. Status (list of meeting number and corresponding action or disposition)

3. Additional contact to user communities, liaison organizations etc.

4. Assigned category and assigned priority/time frame

Other Comments

Unicode

Glyph

Name

Example

066C

ARABIC THOUSANDS SEPARATOR