(original) (raw)
��ࡱ�>�� NP����M��������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������7 ��Q!bjbjUU -87|7|�b������l�����������8$:,��+nr�(���'%'%'%J+L+L+L+L+L+L+$9- Y/�p+�'% !'%'%'%p+�%����Y�+�%�%�%'%.����J+�%'%J+�%��%�*+��6+�f ���|N!��� �U%j&+6+�+0�+.+�/�%"�/6+�%�������SC2/WG2 N2265 ISO/IEC JTC 1/SC 2/WG 2 PROPOSAL SUMMARY FORM TO ACCOMPANY SUBMISSIONS FOR ADDITIONS TO THE REPERTOIRE OF ISO/IEC 10646 Please fill Sections A, B and C below. Section D will be filled by SC 2/WG 2. For instructions and guidance for filling in the form please see the document " Principles and Procedures for Allocation of New Characters and Scripts" (HYPERLINK "http://www.dkuug.dk/JTC1/SC2/WG2/prot"http://www.dkuug.dk/JTC1/SC2/WG2/prot) A. Administrative 1. Title: Proposal for Terminal Graphic Symbols in the BMP 2. Requester's name: U.S. 3. Requester type (Member body/Liaison/Individual contribution): Member body 4. Submission date: 2000-09-15 5. Requester's reference (if applicable): WG2 N2265, L2/00-159 (U.S.) 6. This is not a complete proposal. See L2/00-159 for complete, voluminous justification for these characters, and complete references to all original sources and implementing technologies. See WG2 N2265, Working Draft of Tables & Character Names for Proposed Amendment 1 to 10646-1:2000, for exemplary glyphs, complete list of character names, and proposed encoding points. B. Technical - General 1. (Choose one of the following:) b. The proposal is for addition of character(s) to an existing block. Name of the existing block: Superscripts and Subscripts (1) Miscellaneous Technical (7) Block Elements (10) 2. Number of characters in proposal: 18 3. Proposed category (see section II, Character Categories): 4. Proposed Level of Implementation (see clause 15, ISO/IEC 10646-1): Level 1 Is a rationale provided for the choice? Yes If Yes, reference: These characters are explicitly requested for compatibility with preexisting (and mostly old) character terminals. They will enable the better development of software terminal emulations � which is in fact how most �terminals� actually work now. Since they are intended for �character mode� terminal emulation, these characters are designed for fixed cell placement, and are not designed to be combined in the sense meant by �combining characters� in 10646, even though they may be used in juxtaposition with each other to create screen patterns or as pieces of larger glyph images of �characters� on a terminal screen. As such, they are appropriate for Level 1 implementations of 10646. 5. Is a repertoire including character names provided? Yes. See WG2 N2265. If YES, are the names in accordance with the 'character naming guidelines' in Annex K of ISO/IEC 10646-1? Yes Are the character shapes attached in a reviewable form? Yes. See WG2 N2265. 6. Who will provide the appropriate computerized font (ordered preference: True Type, PostScript or 96x96 bit-mapped format) for publishing the standard? The Unicode Consortium. If available now, identify source(s) for the font (include address, e-mail, ftp-site, etc.) and indicate the tools used: This information can be provided by Asmus Freytag, who has the appropriate fonts and tools used to print these characters. 7. References: a. Are references (to other character sets, dictionaries, descriptive texts etc.) provided? Yes Are published examples (such as samples from newspapers, magazines, or other sources) of use of proposed characters attached? No, not in this document. However, see L2/00-159 for a long list of sources and implementations. 8. Special encoding issues: None Does the proposal address other aspects of character data processing (if applicable) such as input, presentation, sorting, searching, indexing, transliteration etc. (if yes please enclose information)? None needed C. Technical - Justification 1. Has this proposal for addition of character(s) been submitted before? No If YES explain. 2. Has contact been made to members of the user community (for example: National Body, user groups of the script or characters, other experts, etc.)? Yes If YES, with whom? Frank da Cruz, head of The Kermit Project at Columbia University, NY, and inventor of Kermit. Frank is the world�s leading expert on computer terminal protocols. If YES, available relevant documents? See L2/00-159. 3. Information on the user community for the proposed characters (for example: size, demographics, information technology use, or publishing use) is included? The repertoire is intended for the implementation of terminal emulation software. The community of people who write such software is relatively small, but the community of people who use terminal emulation software on their computers is still quite large, easily running in the hundreds of thousands. Reference: 4. The context of use for the proposed characters (type of use; common or rare): Somewhat uncommon. These particular characters are not widely used, but are proposed in order to complete the set of characters needed for terminal emulation. Reference: 5. Are the proposed characters in current use by the user community? Yes If YES, where? Existing hardware terminals. 6. After giving due considerations to the principles in N 1352 must the proposed characters be entirely in the BMP? Yes If YES, is a rationale provided? Yes If YES, reference: Each of these characters is a small logical extension of other sets of similar symbolic characters already encoded on the BMP. No new block extensions are required � all of these characters fit neatly into already existing appropriate blocks of symbols. 7. Should the proposed characters be kept together in a contiguous range (rather than being scattered)? No. They should be arranged in 3 separate ranges, as shown in their proposed block affiliations. 8. Can any of the proposed characters be considered a presentation form of an existing character or character sequence? No If YES, is a rationale for its inclusion provided? If YES, reference: 9. Can any of the proposed character(s) be considered to be similar (in appearance or function) to an existing character? Yes If YES, is a rationale for its inclusion provided? Yes. The scan line characters are similar in appearance to the LOW LINE, 203E OVERLINE, and to various dashes. However, they form a coherent set for terminal graphics, designed to span across a character cell at a particular scan height, and should not be unified with existing punctuation characters or box drawing characters. Unification with other characters has already been taken into account in preparing this repertoire from a larger initial set of characters considered for terminal graphics. The scan line characters in this proposal could not reasonably be unified with existing characters. If YES, reference: 10. Does the proposal include use of combining characters and/or use of composite sequences (see clause 4.11 and 4.13 in ISO/IEC 10646-1)? No If YES, is a rationale for such use provided? If YES, reference: Is a list of composite sequences and their corresponding glyph images (graphic symbols) provided? If YES, reference: 11. Does the proposal contain characters with any special properties such as control function or similar semantics? No If YES, describe in detail (include attachment if necessary) D. SC 2/WG 2 Administrative (To be completed by SC 2/WG 2) 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: Summary Proposal Form: Terminal Graphic Characters DATE \@ "MM/dd/yy" 09/18/00 PAGE 1 �����rs���������� !6:;<=~���������������klm������� _ ` a � � � � � � � � � ����������������������������������˴˯������OJQJ CJOJQJhmHnHu5�CJOJQJCJ 0J5�CJ�j5�CJUj5�CJU5�CJjUhmHnHu CJ(OJQJC������!;=������ln���� _ ����������������������������^���d�d$a$$a$$a$� P!��_ a � � � � E Y V � ��?���,� ������������������������ & F � �~= ��z9��!v%�d�d & F � �~= ��z9��!v%�d�d� A D Y B U V � � � � � ��?���(+,� )-.�$%&oqr���1��� ������4�����%()8������������������������������������������������������������� CJOJQJhmHnHu >*OJQJjUhmHnHuOJQJ5�CJOJQJCJ 5�OJQJOJQJM .$&r��1� ����4���)8UW����������������������������d�d � �~= ��z9��!v%�d�d8UVW������pst���KM������HLM����AC����qs����� h i j k � � � � � � � !!"!6!7!?!@!C!D!������������������������������������������������������� j0J-U mHnHu jU CJOJQJ 5�OJQJOJQJ5�CJOJQJCJjUhmHnHuOJQJL��t��N���M���Dr����t������������������������������� � �~= ��z9��!v%�d�d� i k � � � � A!B!N!O!P!Q!��������������,+D!J!K!L!M!Q!����0J-mHnHu j0J-U0J-+0P��/ ��=!��"��#��$��%������D���y������K� ���y������K� Lhttp://www.dkuug.dk/JTC1/SC2/WG2/prot. iD@��D Normal 1$�d�dCJ_HhmH sH tH <A@���< Default Paragraph Font:�O: Definition Term ��B��B Definition List�h��^�h(�O��( Definition6�*�O* H1$@& 5�CJ0KH$&�O& H2$@&5�CJ$&�& H3$@&5�CJ"�" H4$@&5�&�& H5$@&5�CJ&�& H6$@&5�CJ.�. Address ��6�8��8 Blockquote�h�h]�h^�h�O��� CITE6�$�O���$ CODE CJOJQJ$X@��$ Emphasis6�(U@��( Hyperlink>*B*8V@��8 FollowedHyperlink>*B* 0�O���0 Keyboard5�CJOJQJf�Of Preformatted0 �� �# �~= ��z9��!v% CJOJQJf]��fz-Bottom of Form!$$d1$a$"<�CJOJQJ_HhmH sH tH `\��` z-Top of Form"$&d1$a$"<�CJOJQJ_HhmH sH tH $�O��1$ SampleOJQJ W@�A Strong5�0�O��Q0 Typewriter CJOJQJ$�O��a$ Variable6�,�O��q, HTML Markup<�B*"�O���" Comment<�8Y�8 Document Map)-D OJQJHC�H Body Text Indent *��^�� CJOJQJ,@�, Header + ���!, @�, Footer , ���!&)@��& Page NumberQ8����������!;=������ln����_a����EY V � � � ? � � � , � . $&r��1� ����4���)8UW��t��N���M���Dr����t����ik����ABNR�0���0����������(�����������������������������0������0�����(���n��n��n��n��n��n��n��n��n��n� �n��n��n� �n��n�0�n� �n� 0�n��n� �n� �n��n� �n��n��n��n� �n� ������ ��������(�������� ��������� ��� ������������ ��������� ��������������� ��� ��������� ������ ��������� ������ ��� ������������ ������ ��������������������������������(���������������������������0���@+0���@���@,0�� TTaaad� 8D!Q!_ ��Q!P!r��QX����3HQU\^d4���!4����8�&'@����������$&��( �� ��bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"���� ��bB � c �$������Vd����~?"���� ��bB � c �$������Vd����~?"���� ��bB � c �$������Vd����~?"���� ��bB � c �$������Vd����~?"���� ��bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB � c �$������Vd����~?"������bB �! c �$������Vd����~?"������bB �" c �$������Vd����~?"������bB �# c �$������Vd����~?"������bB �$ c �$������Vd����~?"���� ��bB �% c �$������Vd����~?"����!��bB �& c �$������Vd����~?"����"��B �S ���� ?���;���l�_�� � $���U������i��Q��$�t��$�t��$�t��$�t��$�t��$�t ��$�t ��$�t ��$�t ��$�t ��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t��$�t ��$�t!��$�t"��$�t#��$�t$��$�t%��$�t&��$�t� � 79�ORHK? � � � 0��4F8T�OR3333333��CMR��Kenneth W. WhistlerF:\stix\MathSymSumForm.docKenneth W. Whistler6C:\WINNT\TEMP\AutoRecovery save of TerminalSumForm.asdKenneth W. Whistler6C:\WINNT\TEMP\AutoRecovery save of TerminalSumForm.asdKenneth W. Whistler6C:\WINNT\TEMP\AutoRecovery save of TerminalSumForm.asdKenneth W. WhistlerF:\wg2\TerminalSumForm.docKenneth W. Whistler6C:\WINNT\TEMP\AutoRecovery save of TerminalSumForm.asdKenneth W. WhistlerF:\wg2\TerminalSumForm.docKenneth W. WhistlerF:\wg2\TerminalSumForm.docArnold F. Winkler6D:\afwdata\X3L2\X3L2-2000-11\00329-TerminalSumForm.docuniscape+C:\data\WG2\m39\N2265 - TerminalSumForm.doc�~g��:�����������h����h^�h`���o(.�~g���������R�@��tQp@��Unknown������������G��z ��Times New Roman5��Symbol3&� �z ��ArialA&� ��Arial Narrow?5� �z ��Courier New5&� �z!��Tahoma"���hy�I&y�I& |I�/� 2J� (!�J� 2�����Principles and proceduresKenneth W. Whistleruniscape�������Oh��+'��0������� ,8 T ` l x�����Principles and procedures0rinKenneth W. Whistlerennenn Normal.dotW uniscapetW2isMicrosoft Word 9.0@F�#@�%m�@��gN!�@��gN!�/�����՜.��+,��D��՜.��+,��` px����� ���� � �� Sybase, Inc.s72 J� Principles and procedures Title(RZ� _PID_HLINKS GENERATOR�A�[H&http://www.dkuug.dk/JTC1/SC2/WG2/prot+Internet Assistant for Microsoft Word 2.0z ���� !"#$����&'()*+,-./0123456789:;<����>?@ABCD����FGHIJKL��������O����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������Root Entry�������� �F�L}N!�Q�Data ������������1Table��������%�/WordDocument����-8SummaryInformation(������������=DocumentSummaryInformation8��������ECompObj����jObjectPool�������������L}N!��L}N!������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������� ���� �FMicrosoft Word Document MSWordDocWord.Document.8�9�q