ISO International Organization for Standardization Organisation Internationale de Normalisation ISO/IEC JTC 1/SC 2/WG 2 Universal Multiple-Octet Coded Character Set (UCS) ISO/IEC JTC 1/SC 2/WG 2 N 1203 Date: 1995-04-18 Title: Unconfirmed Minutes of WG 2 Meeting # 27 in Geneva, Switzerland; 1995-04-03 -- 07 Source: V.S. UMAmaheswaran, Meeting Secretary, Mike Ksar, Convener Action: WG 2 members and Liaison organizations Distribution: ISO/IEC JTC 1/SC 2/WG 2 members and Liaisons 1. Opening and roll call 1.1 Opening Input Document: N 1160 Agenda and call for WG 2 Meeting #27 in Geneva, Switzerland; 3-7 April 1995; Mike Ksar, Convener; 1995-03-06 The 27th meeting of ISO/IEC JTC 1/SC 2/WG 2, hosted by ECMA, was held at the Hotel Metropole in Geneva, Switzerland, 1995- 04-03--07. The meeting was called to order at 09:15h on Monday, 1995-04-03, by the WG 2 convener, Mr. Mike Ksar. He introduced Mr. Jan van den Beld of ECMA. Mr. Jan van den Beld welcomed the delegates to Geneva. "ECMA has made arrangements for this meeting on behalf of the Switzerland member body, SNV. I hope you will have a very productive meeting. I hope it will be a decisive meeting for 10646. Many countries have become aware of the standard, and it will be helpful to get a speedier completion of the 2nd edition. Geneva is famous for its international character. It is a small city of about 200 000 people. Hotel Metropole - the venue for this meeting is the property of city of Geneva. It is kept in its current form to cater to the wishes of a number of famous regular customers at the hotel. Several famous guests have stayed here. A number of restaurants are around the hotel. An information package has been distributed to the delegates. ECMA offices are nearby. Michelle Rossignol from ECMA staff will be assisting us. I also welcome all the delegates along with their companions to a social event hosted by ECMA, on Tuesday, the 4th of April, after 19:00h, at Le Carabin, Blvd. de la Cluse 51, Tel: 3208390." The stated objective of this meeting (see N1160) is to review and take decisions on several, but not necessarily all, repertoire addition proposals that have been submitted. Specific repertoires, Tibetan and Korean Hangul are also on the agenda, for prompt review and to finalize their status and allocation at this meeting. A review of the process used by WG 2, a contribution from Denmark towards speeding up its program of work, and a review of SC 2 ballot results are also on the agenda. Copies of several new documents received after the last mailing were made available to the delegates, courtesy of ECMA. All new written contributions are to be given to the convener to assign a document number and to make sufficient number of copies for the meeting. All contributors are also requested to provide to the convener an electronic copy in Word for Windows readable format. The intent is to place these at the FTP site (being proposed to be set up for WG 2 by the Danish Standards Institute, Denmark) so that all WG 2 members who have an FTP capability can get an electronic copy via the Internet access. 1.2 Roll Call Input Document: N 1151 Updated WG 2 Mailing List, post San Francisco meeting; Mike Ksar, Convener; 1995-03-06 Attendees were requested to make any corrections, or add their names, address, telephone and fax numbers, and e-mail id to the current WG 2 mailing list (N 1151) that was circulated. Thirty two (32) delegates representing sixteen (16) member bodies, and three (3) liaison organizations were present. Singapore was attending the WG 2 meeting for the first time. Mr. Hugh McGregor Ross, UK, the previous editor of 10646, and one of the main contributors to the work of WG 2, was able to attend this meeting. Mr. Dara Hekimi, previous SC 2 WG 3 convener, and a strong supporter of SC 2 standards work, was also present on Monday. Several delegates from various member bodies were attending the WG 2 meeting for the first time.The attendance list (sorted in the order of the country of the member body represented) follows: NAME MEMBER BODY AFFILIATION V.S. Canada; Meeting IBM Canada Umamaheswaran Secretary Fu Yonghe China State language Commission Lha Don China Tibetan language Work Direct Committee Office, Tibet Mao Yong Gang China Chinese Electronics Standardization Institute Nyima Trashi China Tibet University Sonam Dorje China Translation and Editing Office, Tibet Zhang Zhoucai China CCID Keld Simonsen Denmark RAP, DKUUG Sven Thygesen Denmark Kommunedata Alaa Ghoneim Egypt IBM Egypt Michel France Microsoft Europe Suignard Michael Ireland Everson Gunn Teoranta Everson Stefan Fuchs Israel; ITU/T Bezeq Takayuki K. Japan Hewlett-Packard Japan Ltd Sato Akio Kido Japan; IRG IBM Japan Rapporteur Chul-Min Kim Korea Ministry of Culture and Sports Sun Gi Hong Korea Microsoft T.J. Kang Korea Hangul & Computer Co. Ltd. Won Seop Lee Korea Korean Bureau of Standards Johan W. van Netherlands; SC Consultant Wingen 22 Kolbj_rn Norway University Library Aamb_ Jan Van Den SC 2 Secretariat ECMA Beld Teow-Hin Singapore National University of Ngair Singapore Sten G. Sweden IBM Svenska AB Lindberg Dara Hekimi Switzerland Consultant J_rgen Switzerland Digital Equipment Corporation Bettels Hugh McGregor UK Data Systems Consultants Ross Bruce UK; Co-editor Consultant Paterson Arnold USA Unisys Winkler John USA Apple Computer, Inc. McConnell Mike Ksar USA, Convener Hewlett-Packard Company Asmus Freytag USA; Unicode Asmus Inc. Consortium 2. Approval of the agenda (N 1160) Input Document: N 1160 Agenda and call for WG 2 Meeting #27 in Geneva, Switzerland; 3-7 April 1995; Mike Ksar, Convener; 1995-03-06 Mike Ksar described the various items on the proposed agenda in N 1160. Several new documents were added to the agenda. Document N 1338 should be corrected to N 1138 (from SC 18 WG9). The revised agenda shown below was accepted. 1. Opening and roll call 2. Approval of the agenda (N 1160) 3. Approval of the minutes of meeting 26 (San Francisco, CA, USA): N 1117 4. Review action items from previous meeting: N 1117, section 12 5. Review SC 2 ballot results and proposed Disposition of Comments N 1035, N 1036, N 1148, N 1149, N 1152, N 1153, N 1154 6. Repertoire issues: 6.1 Review summary of proposed additions to repertoire N 1116 (Guideline), N 1078R and related submittals Submittals/Resubmittals since N 1078R: Viet Nam: Attachment to N 1092, N 1126, N 1127 Japan: Attachments to N 1044, N 1045, N 1093, N 1094, China: N 1097, Ireland: N 1103R, N 1058, N 1132 Liaison SC 18/WG9: N 1338, Individual Contribution: N 1143 (N 983), N 1144 (N 983 & N 879), N 1145 (N 983), N 1146 (N 985), N 1147 (N 987), N 1079R, N 1104, N 1182, N 1168 6.2 Character Ownership: N 1139 6.3 O-zone allocation: N 1140 6.4 Additions to repertoire Korean (N 1158, N 1170) Mongolian (N 1098, N 1184,N 1192) Tibetan (N 1095, N 1159, N 1185, N 1191) 7. Defect Reports 7.1 Review status of editorial defect reports N 1086, N 1125, N 1128, N 1131, N 1137, N 1141, N 1142, N 1162, N 1163, N 1166, N 1188, N 1189 7.2 Review status of non-editorial defect reports N 1114, N 1129, N 1130, N 1164 8. IRG and Related Items 8.1 Report from WG 2/IRG meeting in Taiwan N 1175, N 1176, N 1177, N 1178, N 1179, N 1180, N 1181, N 1183 8.2 CJK Related Items 9. Liaison reports 9.1 Unicode Consortium N 1197 9.2 AFII N 1161 9.3 SC 18 9.3.1 WG 8 9.3.2 WG 9 N1138 9.4 SC 22 9.4.1 WG 3 9.4.2 WG 20 9.5 SC 21 WG 3 9.6 ITU/T N 1196 10. Other business 10.1 How to speed up process: N 1116, N 1134, N 1157 (contribution from Denmark), N 1190 N 1165, N 1167, N 1171, N 1172, N 1173, N 1174 10.2 Future meetings a. WG 2 meeting no. 28: 26-28 June 1995 (Monday to Wednesday, 2 1/2 days) along with SC 2 and WG 3 in Helsinki, Finland. N 1136, N 1155, N 1156 b. WG 2 meeting no. 29: 6-10 November 1995 in Tokyo, Japan Is another meeting required BEFORE November 1995 (Tokyo)? c. WG 2 meeting no. 30: Week of 1996-04-xx, Canada or Denmark d. WG 2 meeting no. 31: 11. Closing 11.1 Approval of Resolutions 11.2 Adjournment The meeting will reconvene at 09:00h on the following days. The intent is to finish the main business of the meeting by the end of Thursday, and to vote on the resolutions on Friday morning (starting 10:30h) finishing by noon. Since most of the editors of 8859-xx (SC 2/WG 3 projects) are present at this meeting, an ad hoc meeting of the 8859-x editors is arranged for for Monday, starting at 16:30h (for about 2h). Mr. Jan van den Beld, convener of SC 2/WG 3 will chair this meeting. Dr. V.S. Umamaheswaran acted as the meeting secretary. Messrs. Arnold Winkler, Asmus Freytag, Akio Kido, Mike Ksar, Umamaheswaran, Michael Everson, and Mao Yong Gang are appointed to the drafting committee for the meeting resolutions. Messrs. Michael Everson, Takayuki K. Sato, J_rgen Bettels, and Johan van Wingen were appointed to an ad hoc committee to deal with editoiral and non-editorial defect reports (brought up since the last meeting) and prepare dispositions for them. 3. Approval of the minutes of meeting 26 (San Francisco, CA, USA): Input Document: N 1117 Unconfirmed Minutes of Meeting 26, San Francisco, CA; Meeting Secretary - V.S. Umamaheswaran, Meeting Secretary; Mike Ksar, Convener; 1994-10-31 Dr. V.S. Umamaheswaran presented the highlights from the meeting 26, referring to the various sections of N 1117. The minutes, with the following corrections, are accepted. a) Section 9.4 - the second sentence should be -- ' ... from the Hague meeting ..' instead of '.. the Copenhagen meeting'. b) Title of section 12.3 should be '... Meeting 26 .. ' instead of ' ... Meeting 25 ...'. c) Remove the words '..Japanese, and ..' from the action item 11b, assigned to Mr. J. van Wingen, in section 12.3. d) Item 13h, in section 10.2, an action item on all member bodies regarding contribution on sources of characters towards an informative annex was marked DONE. It was pointed out that only Japan has contributed input, and all the other member bodies still have to contribute. This action item will be carried forward. This has been re-instated as an OUTSTANDING action item. Mr. Jan van den Beld explained the procedure used by SC 2 secretariat for dealing with SC 2 ballots, in light of the poor voting responses from the SC 2 P-members. Only 50 % of P members of SC 2 have cast ballots. There are substantial topics being discussed in SC 2 matters. There are 29 P members of SC 2. The secretariat uses a short list of P members (based on past voting record) to decide whether there is Substantial Support (following the new JTC 1 procedures) on ballots. It is not stated clearly as to what is 'substantial support' in JTC 1 procedure. The OCR-B case was cited. The ballot failed because of lack of norms for what is 'substantial support'. The member bodies are requested to be precise in their ballot responses, and ensure that the responses are sent to the secretariat before the closing dates. Also, since the WG 2 meeting in San Francisco, some member bodies seem to have sent the ballot responses to WG 2 convener instead of SC 2 secretariat. Action item: WG 2 delegates are once again requested to encourage their member bodies to cast their ballots in time. Also, WG 2 delegates are requested to encourage their delegates to be prepared for taking national positions at the SC 2 plenary meeting in June 1995. 4. Review action items from previous meeting: N 1117, section 12 Input Document: N 1117 Unconfirmed Minutes of Meeting 26, San Francisco, CA; Meeting Secretary - V.S. Umamaheswaran, Meeting Secretary; Mike Ksar, Convener; 1994-10-31; Section 12. Dr. V.S. Umamaheswaran reviewed the status of outstanding action items, referring to the list under section 12 in document N 1117. Several items were completed, and others are either in progress or still outstanding. The following table shows the status of the various action items. The convener pointed out that if sufficient progress is not made on a specific outstanding action item, it will be deleted from the list of items to be addressed by WG 2. 12.1. Outstanding Items From WG 2 Meeting 24, Washington DC It Assigned to / action (Reference N 954R - Status em resolutions, and N 955 - minutes of Washington DC meeting WG 2-24) 2. Editor - Mr. Mark Davis: d. to include some text on 'what criteria can be COMPLETED. used for defect report on character names' as N 1137 part of the Set of Principles document (reference section 9-a-i.3) Note: Re-assigned to ad hoc group on principles and procedures - reference resolution M26.6. f. to prepare a defect report to correct the names COMPLETED for all the non-presentation form characters N 1128, N that have the term LIGATURE in their names 1130 (from (reference resolution AE-1), excluding those co-editor) under resolution AE-2; (reference resolution AE- 3). 12.2. Outstanding Items From WG 2 Meeting 25 Antalya, Turkey It Assigned to / action (Reference N 1034 - Status em resolutions, and N 1033 - minutes of Antalya meeting WG 2-25, and corrections to these minutes in Annex A of N 1117) 2. Convener (Mr. Mike Ksar): b. to update document N 957-R containing the WG 2 OUTSTANDING program of work - capturing all the comments received under item 8.3 in this set of minutes. 3. Project Editor (Mr. Mark Davis): c. Act on resolution UTF-1. COMPLETED N 1128; pDAM- 4 d. Act on resolutions DR-1 and DR-2. COMPLETED N 1086, N 1114, N 1131 e. Act on resolution pDAM3. COMPLETED pDAM-3 f. Act on resolution PRIN-2. COMPLETED N 1116 4. French and the Netherlands member bodies. are invited to prepare a formal defect report OUTSTANDING on Armenian characters (described in document N 1022). Mr. J.W. van Wingen had volunteered to contribute. 5. Japanese member body a. is requested to forward a set of bit maps and OUTSTANDING /or the outline of the corrected shapes reported in document N 1006 and N 1014 along with a blown-up (96x96) hard copy to the editor. Note: Japan needed more information from the project editor regarding fonts See discussion under section 8.1.2 in WG 2-M26 minutes document N 1117. b. is invited to prepare a defect report to remove DROPPED at the inconsistency regarding annotations in the request character names from Rule 12 in the annex on of Mr. Sato, naming rules in 10646-1. Japan 6. Korean member body is requested to forward the set of bit maps, IN PROGRESS and or the outline of the corrected shapes of the characters in defects in document N 975, along with a blown-up (96x96 bits) hard copy is needed by the editor. 7. Messrs. Joachim Friemelt and Stefan Fuchs is invited to prepare a paper containing ITU/T COMPLETED suggestions for clarification to the current N 1125 naming rules in 10646-1. 8. Indian member body is invited to prepare a defect report asking OUTSTANDING for the appropriate editorial change regarding references to ISCII 1991 - following the JTC 1 Defect Reporting procedures (and forms). 9. Danish member body (Mr. Keld Simonsen) is encouraged to update the information in OUTSTANDING their contribution (Temporary Document) removing the parts that are not relevant to the Annex under resolution TKS-3 from the WG 2 Washington meeting no. 24. 10 Chinese member body . a. is requested to study this possibility of UNDER STUDY composition to reduce the number of characters of the Yi script in document N 965 that needs coding in the BMP. b. is requested that China and Mongolia get OUTSTANDING together and come up with an agreed upon joint proposal between the two by the next WG 2 meeting c. is requested to coordinate the Tibetan script IN PROGRESS requirements by working with other member bodies such as India and other countries such as Bhutan and Sikkim using the Tibetan language and script. 11 Mr. John Clews . is invited to draft and propose a proforma CLOSED; WG 2- incorporating his suggestions for guidelines 26 Ad Hoc for submission of new repertoires to be coded. prepared Note: Resolution M 26.6 taken at this meeting N1116 and makes this action no longer required. N1137 13 All member bodies . d. is invited to nominate a WG 2 expert to be the No Interest; liaison representative from SC 2 WG 2 to SC 29. CLOSED h. is invited to contribute input on sources of OUTSTANDING characters towards developing an informative Japan: N Annex to ISO/IEC 10646-1 for consideration at 1055; Japan: the next SC 2/WG 2 meeting N 1066, 1067, 1068, 1069 Other member bodies are still to contribute. 12.3. New Items From WG 2 Meeting 26, San Francisco, CA, USA It Assigned to / action Status em 1. All WG 2 Experts a. to note that WG 2 experts must be nominated by COMPLETED the member bodies and their intended attendance at the meetings must be conveyed to the convener prior to the meeting. Documents to be discussed at the meeting should be sent to the convener at least 6 weeks prior to a meeting. Documents submitted at the meeting may get considerations only at the next meeting. b. to ensure that their member bodies do return COMPLETED the ballots on pDAM-1 and pDAM-2, before the closing date, if they have not already done so. 2. All Member Bodies a. to revisit their submissions prior to May 93 Several (when 10646-1993 was used as the starting Forms have point), and send a filled Proposal Summary Form been sent for each to the WG 2 convener. in; Others are expected to be submitted. b. to examine all proposals for additions to the OUTSTANDING repertoire (refer to list in document list in N 1078 and in N 1050, and N 1100) and suggest enhancements, corrections etc., if there is any impact on the proposed characters' usage in their user communities. c. to review 1078 along with the noted corrections OUTSTANDING in WG 26 meeting minutes, and send feedback to Mr. Hart for updating the document. Several new contributions received after N 1078 are not included in the document. d. to feedback any specific requirements / OUTSTANDING comments to Japan with reference to document N 1093 on BRAILLE characters proposed by Japan. e. to give feedback to China on their proposal on OUTSTANDING Mongolian in document N 1098. New document N 1184 should be referred to. f. to check the contents of N 1086 with respect to OUTSTANDING the disposition of their editorial defect reports. g. to examine the non-editorial defect reports in OUTSTANDING document N 1114 and take appropriate actions on the suggestions for their dispositions from the ad hoc. h. to provide available information on 'sources of OUTSTANDING fonts' to answer questions received during promotional presentations on the standard, and by the SC 2 secretariat, by implementers of the of the standard. i. All contributors of WG 2 documents are OUTSTANDING encouraged to provide an electronic version of the documents -- preferred format is any one of the formats that is recognized and can be converted by MS Word for Windows. If the documents include any glyphs in RTF format, they are easier for the project editors to use directly. 3. Project Editor / Co-Editor: Mr. Mark Davis / Mr. Bruce Paterson a. With reference to RESOLUTION M26.2, to prepare COMPLETED editorial corrigenda from the instructions to N1131 the editor contained in N 1086; to accumulate these corrigenda with those previously agreed to by WG 2 (document N 1031R); and, to prepare camera ready revised text for submittal to ITTF at a future date. The disposition regarding change request for some APL character names in N 1037 should also be incorporated (though it is listed only in N 1114 and not in N 1086). b. With reference to Resolution M26.3, and with OUTSTANDING N1059 as the draft text of an annex to ISO/IEC 10646-1, to provide pDAM text for SC 2 ballot. 4. WG 2 Convener - Mr. Mike Ksar a. Convey to SC 2 request of WG 2 (with reference COMPLETED to recommendation M 26.1) regarding re- balloting of the six items: N 2480 -Subdivision of JTC 1.02.18 UCS; N 2481 - NP on Character Glyph Model; N 2483 - Request from SHARE Europe for C liaison; N 2511 - Request from Taipei Computer Association for C liaison; N 2512 - Request from Hong Kong Information Technology Federation Ltd. for C liaison; N 2513 - Request from EWOS Technical Computer liaison Group (TLG) subgroup on character sets for C liaison, including a 'distinctive ballot response form'. b. Request SC 2 to confirm WG 2 nomination of Mr. COMPLETED Bruce Paterson as a co-editor (with reference to recommendation M 26.7). c. to mark N 1107, N 1108, N 1110 and N 1113 in COMPLETED the WG 2 document list as WITHDRAWN (by submitter - Mr. Michael Everson, Ireland). d. to respond to liaison statement from SC 18 WG 9 COMPLETED that their contribution in N 1037 has been added to the list of proposals for consideration by WG 2, along with the request to fill the Proposal Summary Form. e. to respond to liaison statement from SC 22 WG 3 COMPLETED that their contribution in N 1037 has been considered. The request to add QUAD character, has been added to the list of proposals for consideration by WG 2, along with the request to fill the Proposal Summary Form. The request to change the names has been dealt with (disposition is in N 1114 under item 1037-2). 5. Meeting Secretary - Dr. V.S. Umamaheswaran a. to update the resolution document N 1118 with COMPLETED all the modifications agreed to during the N 1118 meeting and send it to the convener. b. to prepare (unconfirmed) meeting minutes COMPLETED document N 1117 and send it to the convener. N 1117 6. IRG (Mr. Akio Kido) to take necessary action in IRG with reference OUTSTANDING to resolution M 26.4 regarding 5-column layout of Han block. 7. Ad hoc group on principles and procedures (Messrs. V.S. Umamaheswaran, Sven Thygesen, Peter Edberg and Sten G. Lindberg) With reference to resolution M 26.6 and prepare COMPLETED N 1118, (and a transmittal letter to be sent to N1116, member bodies, liaison organizations and other N1137, N1157 potential submitters of proposals for additional characters to the standard), by end of November 1994 at the latest. 8. Ms. Joan Aliprand - Liaison to TC 46 to take parts related to TC 46 in document N IN PROGRESS 1071 for formal submission as liaison document by TC 46 along with the completed Proposal Summary Form. 9. Mr. Alan Griffee - Liaison to SC 18 WG 8 to convey to SC 18 WG 8 that their Math symbols IN PROGRESS proposal be resubmitted along with the completed Proposal Summary Form. The original request was prior to publication of 10646. 10 Mr. Sven Thygesen . input to Mr. Bruce Paterson proposal to assist COMPLETED in the preparation of technical corrigendum on N1128 AE (reference action item M 24 - 2f on AE) 11 Mr. Johan W. van Wingen . a. to communicate to SC 22 ALGOL working group, OUTSTANDING characters from document N 1071, towards SC 22 ALGOL preparation of a liaison statement to WG 2 group does along with the completed Proposal Summary Form. not exist any more. A contribution on ALGOL is to be discussed at this meeting. b. is invited to prepare contributions on Railway OUTSTANDING users that he volunteered to prepare during the Removed the meeting. words 'Japanese, and'. 12 Mr. Michael Everson . a. to advise the SC 2 chair (Mr. Sten G. Lindberg) OUTSTANDING and the SC 2 secretariat, the names and addresses of contacts regarding Armenian encoding standardization effort. b. With reference to N 1105, Ireland is invited to COMPLETED submit improved glyph (check with editor) as N1162 well as proposed alternative names. c. With reference to N 1109, Ireland is invited to COMPLETED submit their comments as part of the ballot on Ballot technical corrigendum on _. comments on dCOR-1; N1164 13 Mr. Michael Everson and Canada . With reference to document N 1104 on Canadian IN PROGRESS Aboriginal syllabics, to work with Canadian member body (and CASEC) and get agreement on a common position. 14 Mr. Hugh McGregor Ross and Canada . With reference to document N 1073 on Canadian IN PROGRESS Aboriginal syllabics, to work with Canadian member body (and CASEC) and get agreement on a common position. 15 Canada, China, Korea - on Compatibility . Characters With reference to N 1054 R - act on the call COMPLETED for information on an annex on list of N1044 - compatibility characters. OVERLINE - Japan China and Korea in agreement with Japan to replace MACRON by OVERLINE N 1168- Canada 5. Review SC 2 ballot results and proposed Disposition of Comments 5.1 pDAM-1 on UTF-16 Input Documents: N 1035 ISO/IEC 10646-1 Proposed Draft Amendment 1 (UTF-16); Mark Davis, Project Editor; 1994-08-01 N 1148 Nine tables of replies to repeated/extended votes; SC 2 Secretariat, Geneva; 1995-02-22 N 1149 Proposed Disposition of Comments on pDAM1 (UTF-16); Bruce Paterson, Project Co-Editor; 1995-02-24 N 1153 Proposed text for Draft Amendment 1 (UTF-16), post ballot; Bruce Paterson, Project Co-Editor; 1995-02-24 Presentation: Mr. Bruce Paterson presented. Table of replies in N 1148 for ballot on SC 2 N2534 (UTF-16) shows a tally of 12 Yes, 5 No and 3 Abstain (including Denmark's updated 'Negative with comments'). N 1149 contains the disposition of comments. This was distributed as SC 2 N 2551 to SC 2. N 1153 contains the revised pDAM-1 text. Japan's negative vote was based on administrative matter on work items. Japan is requested to reconsider their position. Other comments are on technical or editorial matters of significance. Canada's comments The initial sets of comments were all accepted. The Canadian comment on calling it TF-16 versus UTF-16, based on potential for misinterpretation of UCS to be universal was brought to the attention of the meeting. Another contribution from a Canadian expert on 'Truly Universal UTF-16' was submitted as additional ballot comments to SC 2. This contribution was not in line with Washington resolution. Editor has no authority to act on it. If WG 2 accepts further changes to the resolution then it could be considered. Discussion on Canada's comments: Canadian Universal UTF-16: 1. Dr. V.S. Umamaheswaran explained the Canadian proposal. It is based on the observation that several member bodies including Canada had difficulty accepting the restriction of the range to 1 million, instead of the entire UCS-4. However, at the time the UTF-16 was discussed in Washington, there was no equally elegant alternative proposal to consider. The Canadian proposal was to remove the restriction without sacrificing the principles behind the current pDAM-1, nor requiring reservation of any more code positions than the current S-zone in the BMP. It does involve a change to UTF-16 algorithm and Canada believes that it is not too late to change. 2. Convener: if it is in conflict with the resolution then we may have difficulty accepting it. 3. Mr. Mike Everson: Ireland favours moving on with what we have - do not accept technical improvements. 4. Mr. Keld Simonsen: Denmark has a similar contribution. Have not seen Canadian comments. 5. Mr. J_rgen Bettels: Switzerland believes that the restriction of 1 million is adequate - sees no reason to reopen it. 6. Mr. Bruce Paterson: UK - is not in support of the change. 7. Convener: Would prefer to accept another UTF as a future enhancement. In order to avoid any delays we should accept the current pDAM-1 as it is. Disposition: Canadian Universal UTF-16 is not accepted. Proposed change of the name UTF-16 to TF-16: 1. J_rgen Bettels: UCS may be adequate and it is not used as Universal. 2. Other member bodies were not in support of the Canadian editorial comment. Disposition: TF-16 will be reverted to UTF-16. China's negative ballot: 1. China was objecting to 'mixed length of 2 versus 4 octets'. This is not in alignment with UTF-16 resolution in Washington. Editor cannot resolve this. 2. The note regarding HCS-B encoding in the disposition of comments N 1149 was brought to the attention of the Chinese delegates. N 949R was also referenced. Disposition: The Chinese negative ballot may have to stand. Japan's negative ballot: The procedure matter seems to have been resolved. Japanese think that the corrigendum and the addendum are not in synchronization. Disposition: The Japanese negative ballot may stand. Korean negative ballot: 1. There were no reason given for the NEGATIVE ballot. Editor could not respond. 2. Mr. T.J. Kang: Delegates who are present cannot give a reason for the negative ballot. Original Korean delegates who were at the Washington meeting were not present. Disposition: Korea changes its vote to Positive. Switzerland's negative ballot: 1. 'UTF 16 is considered to be an architecture extension of UCS. It should be integrated into the body of the document as another coding method.' The editor cannot accept this without further instructions from WG 2. 2. Mr. J_rgen Bettels: the comment could have been considered as Editorial instead of Technical. It was felt that UTF-16 would have been considered as an architectural extension than like any other UTFs. We were expecting more support from other member bodies on the same topic 3. Mr. Johan van Wingen: Would have opposed to making it part of the architecture. 4. Mr. Bruce Paterson: UK was more concerned about progress of work, and let the work go ahead. 5. Dr. Asmus Freytag: Unicode Consortium had the same feeling as UK. Disposition: Switzerland changes the vote to Positive with Editorial Comments. US comment no. 3 - 'not only detect the error, what mappings should be done to the error characters.' A Statement about unpaired RC-elements already exists in the document and this should suffice. Disposition: Mr. Arnold Winkler: USA can live with the wordings proposed. Slovenia comments: wanted UTF-16 to be moved to the body of the standard. Same as Switzerland. Mr. Keld Simonsen: Denmark would have accepted it. All other editorial comments - from Greece, UK, and USA were accommodated. Clause 11 wordings in N 1153 The code positions of 32 planes from Plane E0 to Plane FF of Group 00 shall be for Private Use. The code positions of the 32 groups from Group 60 to Group 7F shall be for Private Use. The current proposed text in N 1153 contains the above marked deletion in clause 11 and an equivalent deletion in clause 5. It was not the intent, per Washington resolutions, of deleting the currently permitted PU planes and groups from the standard. Two additional PU planes are added. The text deletion in clause 5 is OK because it was a duplication of what is in Section 11. Annex A wording also has to be verified. This matter was brought to the attention of the editor by Singapore and Canada. The error was also indirectly referenced by comments from USA and from the UK. Disposition: Re-instate the private use groups and planes permitted in the published standard. WG 2 agreed to accept the proposed texts in N 1149 and N 1153 with the corrections noted during the above discussions. All the delegates were requested to review contents of the proposed disposition and pDAM text and feedback to Mr. Bruce Paterson before he leaves on Wednesday. Relevant Resolution: M27.1 (pDAM-1 on UTF-16): Canada NO WG 2 accepts the disposition of ballot comments in N 1149 and the proposed text for DAM-1 on UTF-16 in N 1153 with changing back from TF-16 to UTF-16, and reinstating private use group provision, and instructs its editor to forward corrected N 1153 to SC 2 secretariat for further processing in JTC 1 as an AMENDMENT to ISO/IEC 10646-1: 1993 (E). 5.2 pDAM-2 on UTF-8 Input Documents: N 1036 ISO/IEC 10646-1 Proposed Draft Amendment 2 (UTF-8); Mark Davis, Project Editor; 1994-08-01 N 1148 Nine tables of replies to repeated/extended votes; SC 2 Secretariat, Geneva; 1995-02-22 N 1152 Proposed Disposition of Comments on pDAM2 (UTF-8); Bruce Paterson, Project Co-Editor; 1995-02-23 N 1154 Proposed text from Draft Amendment 2 (UTF-8), post ballot; Bruce Paterson, Project Co-Editor; 1995-02-24 Presentation: Mr. Bruce Paterson, the project co-editor, presented the results of the SC 2 ballot and the disposition of comments on pDAM-2. Nearly all member bodies have approved as presented - the tally was 16 Yes, 1 No and 3 Abstain. The only disapproval was from Japan on the basis that the splitting of work item was not approved. Since then, the work item has been split. Hopefully their objection has been taken care of. SC 2 N 2552 and part of SC 2 N 2564 contain the comments from the different member bodies. Not all of these comments were included in N 1148. N 1152 contains the disposition of comments. Canada, Greece, Switzerland, UK, USA -- all had editorial comments. N 1154 contains the revised text accommodating these comments. If WG 2 accepts N 1154, it will be sent for a DAM ballot (equivalent of DIS) at the JTC 1 level. Discussion: 1. Mr. Keld Simonsen: would like to examine the transformation between UTF-8 and UTF-16 carefully. It was pointed out that such a transformation was not part of pDAM-2. 2. Mr. Takayuki Sato: needed clarification as to what does the Amendment apply to? The published 10646 is the basis. Disposition: WG 2 considers that the work on UTF-8 has been completed. WG 2 accepts the proposed texts in N 1152 and N 1154. These should be forwarded to SC 2 secretariat for processing by JTC 1 as a draft Amendment to ISO/IEC 10646-1 (E). Action Item: WG 2 experts in attendance are requested to encourage their member bodies to support the Amendment on UTF-8 at the JTC 1 level balloting in their countries. Liaison representatives to SC 22/WG 20 and to X/Open also should take note. Relevant Resolution: M27.2 (pDAM-2 on UTF-8): Unanimous WG 2 accepts the disposition of ballot comments in N 1152 and the proposed text for DAM-2 on UTF-8 in N 1154, and instructs its editor to forward N 1154 to SC 2 secretariat for further processing in JTC 1 as an AMENDMENT to ISO/IEC 10646-1: 1993 (E). 5.3 pDAM-3 on C1 controls Input Document: N 1148 Nine tables of replies to repeated/extended votes; SC 2 Secretariat, Geneva; 1995-02-22 C1 Controls - the pDAM was approved with 15 Yes and 1 Abstain. The text was in SC 2 N 2553 - there was no WG 2 document number for this text. Relevant Resolution: M27.3 (pDAM3 on coding of C1 controls): Unanimous WG 2 notes that pDAM-3 ballot on SC 2 N 2553 was positive, and requests SC 2 secretariat to forward the text in SC 2 N 2553 for further processing in JTC 1 as an AMENDMENT to ISO/IEC 10646-1: 1993 (E). 5.4 pDAM-4 on UTF-1 Input Document: N 1148 Nine tables of replies to repeated/extended votes; SC 2 Secretariat, Geneva; 1995-02-22 Presentation: Mr. Bruce Paterson presented. SC 2 N 2554 contains the pDAM- 4 text. There is no WG 2 document number. The tally was 12 Yes, 1 No and 2 Abstain. Canada voted negative. Canada has proposed that the UTF-1 text should be registered first in ISO-IR before it can be removed from 10646. Disposition: The pDAM has been accepted in principle. The editor can extract the text on UTF-1 and register it with ISO, and modify the text of pDAM to reflect Canada's comments. These can be processed in parallel. This will satisfy Canada's comments and should reverse its negative ballot. Relevant Resolution: M27.4 (pDAM4 on removal of UTF-1): Unanimous WG 2 notes that pDAM-4 ballot on SC 2 N 2554 was positive, and requests its editor to: a. Extract the text of annex on UTF-1 and forward it for registration with the ISO Registrar b. Revise the text of SC 2 N 2554 to accommodate the ballot comments from Canada in N 1148, and forward the revised text to SC 2 secretariat for further processing in JTC 1 as an AMENDMENT to ISO/IEC 10646-1: 1993 (E). 5.5 dCOR 1 on AE Input Document: N 1148 Nine tables of replies to repeated/extended votes; SC 2 Secretariat, Geneva; 1995-02-22 Presentation: Mr. Bruce Paterson presented. The tally on the ballot was 10 Yes, 2 No and 2 Abstain. The dCOR text is in the document SC 2 N 2555 - dCOR-1 on ligature AE (there is no WG 2 document). 1. Netherlands had negative comments and had referenced 9 attachments. Netherlands wants a synchronization of changes in all SC 2 and other standards that use the name 'ligature'. Also, it believes that the change should have been processed as a DAM and not a dCOR. 2. Canada had opposed to the change of normative names and had proposed an alternative of an annotation such as (uppercase letter _) etc. 3. Editorial comment that it is called 'ASH' in English language was received from Ireland. Discussion: Canadian negative ballot comments: 1. Mr. Sven Thygesen: Denmark proposed that Canadian proposed compromise approach be taken to satisfy the Canadian requirement. An annotation (ligature AE), for example, be added as an annotation. 2. Mr. Kolbj_rn Aamb_: Norway strongly opposes any wordings that suggests that the character is used as a ligature, due to the number of cases of non-support of the AE in the Nordic Countries such a term has caused in current implementations. 3. Mr. Michel Suignard: French usage of the term 'ligature' exists. 4. Dr. V.S. Umamaheswaran: Queried if the dCOR has been sent to JTC 1's attention. This was checked later with SC 2 secretariat - JTC 1 document N3357 dated 5th January 1995 with a due date of 15 March 1995 was sent for comments to JTC 1. (ACTION for Uma - to check with CAC JTC 1 and SCC in Canada). Disposition: Canadian negative ballot cannot be accommodated. Netherlands negative ballot: It is based on a procedural question. 1. Mr. Johan van Wingen: Should we delay a decision till SC 2 plenary? 2. No - this was an SC 2 ballot. Also, it has been sent to JTC 1 for Comments, following the current JTC 1 procedures. Disposition: Netherlands comments on procedures could not be resolved. Ireland - comments with positive ballot: 1. Mr. Mike Everson: Ireland has proposed additional comments - like word ASH for English. He has also provided evidence of use of the character name as ASH. 2. Mr. Bruce Paterson: Even the members of UK national committee were surprised that such a use existed in English. 3. Dr. Asmus Freytag: Do as little as possible - to enhance the wordings. These long names are being used in several contexts. Disposition: An annotation such as '(or ash)' was accepted. Denmark, Norway, France and Canada - should get together and come up with a consensus on accepting "(ligature AE)" or not. The differences could not be resolved in off-meeting discussions. In the draft resolution prepared by the drafting committee, a choice of two possible wordings was offered in the resolution text, for selection by WG 2 prior to balloting on the resolution itself. LETTER AE (ash, was ligature _) or LETTER AE (ash)*, and corresponding entries in the new informative annex The second option was favoured by the majority of the delegates and was used in the text of the resolution - see below. Relevant Resolutions: M27.5 (New Annex on Character Information): Unanimous WG 2 instructs its editor to create a new informative Annex, to be called "Additional Information on Characters" to contain explanatory information related to characters, for review at the next WG 2 meeting (1995-06-26). The editor is further instructed to revise Annex K on Character Naming Guidelines, to remove any inhibitors to references from the code table to this new Annex. The suggested reference character is an "*" (asterisk) at the end of the character name. The sorted names list in Annex E will not have such annotations. M27.6 (dCOR-1 on _): Canada NO WG 2 instructs its editor to amend each of the names of characters in dCOR-1 (document SC 2 N 2555) as follows: LETTER AE (ash)* and a corresponding entry for each character, in the Annex on Additional Information on Characters regarding the fact that these characters are called 'LIGATURE'-s in the current published standard. WG 2 further instructs its editor to modify and re-order the list of character names in Annex E to reflect the corrections in dCOR- 1. The editor is further instructed to forward the corrected dCOR-1 to the SC 2 secretariat for further processing by ITTF as a Technical Corrigendum to ISO/IEC 10646-1: 1993 (E) (after completion of the annex mentioned under resolution M27.5 above). 6. Repertoire issues: 6.1 Review summary of proposed additions to repertoire 6.1.1 N 1116 (Guideline), N 1078R and related submittals 6.1.1.1 N 1116 Principles and procedures document Input Document: N 1116 Principles and Procedures for Allocation of New Characters and Scripts (Revised N 946); Ad hoc group on Principles and Procedures - Messrs. V.S. Umamaheswaran, Sven Thygesen, Peter Edberg, Sten G. Lindberg; 1995-01-27 The form in N 1116 has been used by several member bodies and experts to submit summary information regarding different proposals. These were used for discussions on different scripts submitted for WG 2 consideration. Discussion: 1. Mr. Takayuki Sato: What are the specifications for the FONTS required to be submitted by the sponsor. 2. Dr. Asmus Freytag: True-type should be suggested as the preferred format. Bit map can be created from the true type. Action item: The ad hoc on principles and procedures should update N1116 to reflect the Fonts specification. Based on discussion under other agenda items later, add an additional entry under WG 2 administrative section to record 'other interested parties consulted'. 6.1.1.2 N 1078R Cross-reference of WG 2 documents Input Document: N 1078R Cross-reference of WG 2 documents to scripts and repertoire issues; (revised N887R and N 990); Edwin Hart, US; 1994-10-07 There was no discussion on this document at this meeting. It needs checking and updating to reflect all new submissions to WG 2. The new administrative tool proposed by Denmark may remove the need for this document. 6.1.2 Viet Nam: Attachment to N 1092, N 1126, N 1127 6.1.2.1 N 1092R: Vietnamese currency symbol 'DONG' Input Document: N 1092 Vietnamese currency symbol in the BMP; Viet Nam, TCVN/TC1; 1994-10-05 Discussion: 1. Mr. Michael Everson: There is no reason to object to this request. 2. Mr. Johan van Wingen: We are opposed to adding any new currency characters. The whole banking world is changing to using three character currency symbols. They only cause confusion. 3. Mr. Michael Everson: It may be true for international banking. Banks are not the only user community being served by the standard. The Vietnamese standard contains this symbol. 4. Mr. Bruce Paterson: There are already 12 currency symbols in the standard. It will be discriminatory not to support it. 5. Mr. J_rgen Bettels: Is Vietnamese proposing adding to a particular position? No - Not in the proposal summary form submitted. Looking at the example of the bank note in the submitted attachment, it looks like the currency symbol on the bank note is Uppercase D with underscore. It does not resemble the glyph submitted for the DONG SYMBOL. 6. Dr. Asmus Freytag: Suggested that we accept the request in principle - and not put on hold. 7. Mr. Michael Everson: The picture of the Bank Note does not even seem to use the symbol. 8. Mr. Takayuki Sato: Will Vietnam be requesting only a single currency symbol? Will there be additional ones? Vietnam was not represented at the meeting - no one could respond. We have to assume that there will be only one. 9. Mr. Mike Ksar: There are some questions about the Glyph Image to be used for this symbol? Additional examples where the symbol is actually used can be requested from Vietnam. Action item: Vietnamese member body is requested to clarify the glyph image to be used in the standard, and provide additional examples of use of the currency symbol with that glyph image. The bank note example attached to the summary form raised more questions than serve as an example. Disposition: WG 2 accepts the request in principle. Row 20 position x'20AB' in the BMP is assigned, with the name DONG SIGN. This is the FIRST new character addition to the BMP assigned by WG 2 since the 1993 published version of the standard. Relevant Resolution: M27.8 (new character requests): Unanimous With reference to N 1092 (from Vietnam), WG 2 instructs its editor to add DONG SIGN at code position 20AB in the BMP, for inclusion in the second edition of ISO/IEC 10646. 6.1.2.2 N 1126 Cham Script Input Document: N 1126 Additions to repertoire, Cham Character set; TCVN, Viet Nam; 1994-10-14 This document was distributed to WG 2 and liaisons in January 95. The document contains a proposal summary form and the draft Vietnamese standard for 8-bit Cham standard coded character set for information interchange (CSCII). Discussion: 1. Mr. Michael Everson: There are some questions on the ordering of characters etc. 2. Mr. Bruce Paterson: The list of names used in CSCII will need changes for incorporation in 10646. For example: on Page 8 - Cham Number SAA etc. is used. 10646 names would be CHAM DIGIT ONE etc. instead of CHAM NUMBER SAA. Similarly, the combining marks would be renamed as 'CHAM COMBINING MARK R' instead of 'COMBINING R' etc. 3. Mr. Johan van Wingen: We should first ensure we have uniform naming conventions for 'DIGITS', 'LETTERS' etc. to ensure consistency in names in 10646. 4. Dr. Asmus Freytag: If it is not already there, Annex K on naming conventions could have such rules. 5. Ireland and Unicode consortium expressed their interest in being added as 'Other interested parties' on the subject (see revised N 1116 form to be prepared by the ad hoc). Disposition: The document has been accepted for further processing. All member bodies and liaison organizations are being alerted to this request, and are requested to review and feedback to Vietnam. Mr. Michael Everson volunteered to assist in compiling the comments and questions to Vietnam and others. Action item: a. Viet Nam is requested to work with Mr. Bruce Paterson. Mr. Everson will compile the comments and questions to send to Vietnam member body. b. Mr. Johan van Wingen is invited to check if conventions used for DIGITS, LETTERS etc. are clearly stated in the standard, and suggest any necessary changes. 6.1.2.3 N 1127 Chu Nom Input Document: N 1127 Vietnamese sample of the exercise to use new WG 2 form for adding Chu Nom to 10646; TCVN, Viet Nam; 1994-10-14 This document contains a proposal summary form for Chu Nom script, along with a contribution 'IRG N097 - Nom Vertical Extension Repertoire ...' containing more details. Discussion: Mr. Akio Kido: This document should be handled in IRG Disposition: The document is referred to IRG. Unicode consortium is interested. Action item: IRG is to consider the Vietnam request for CHU NOM script in N 1127 in its work on Vertical Extension. 6.1.3 Japan: Attachments to N 1044, N 1045, N 1093, N 1094 6.1.3.1 N 1044 Full-Width OVERLINE Input Document: N 1044 Defect Report on 10646 Repertoire (Add FULLWIDTH OVERLINE); Japan; 1994-08-01 Presentation: Mr. Takayuki Sato presented the defect report. The proposal is to add a new character in the block HALFWIDTH and FULLWIDTH FORMS. Current standard has "FFE3 - FULL WIDTH MACRON". The name may need a clarification / referenced note to indicate its use also as an overline. If this is not acceptable, then a new code position will be required. Discussion: 1. Dr. Asmus Freytag: If this is not a new character, but happens to have the wrong name in the standard, we can propose an explanatory note as the suggested solution. There is no known problem with mapping to existing standards. 2. Mr. Takayuki Sato: If this character is not part of any other script then the correction or explanatory note would be acceptable. Otherwise, we should add anew character. 3. Mr. Michel Suignard: There are several other MACRON and OVERLINE characters in other parts of the standard. 4. Mr. Takayuki Sato: After meeting and discussing with delegates from Korea and China, there is confirmation that this character is used only as an OVERLINE and not as a MACRON accent. Disposition: WG 2 accepts that the naming of character was in error. An annotation in the informative annex is accepted instead of changing the name. Relevant Resolution: See resolution M27.7 item a, in section 7.1.3 later. 6.1.3.2 N 1045 ISO 2047 symbols Input Documents: N 1045 Defect Report on 10646 Repertoire (Add ISO 2047 symbols); Japan; 1994-08-01 N 1174 Query on the representation of Control Characters; Michael Everson, Ireland, expert contribution; 1995-03-14 Output Document: An Attachment to N 1174 'Proposed Coding of Symbols From ISO 2047'; Asmus Freytag. N 1045 contains a proposal to add 32 pictorial symbols. If we decide to accept these, then we can investigate which do exist and which are new. N 1174 from Ireland is on the same subject but has a different concern. It contains a proposal to change the alphanumeric glyphs used in 10646 columns 240 -- 242 to the PICTORIAL SYMBOLS of ISO 2047. This will potentially result in two identical looking symbols having two different code positions and names. Presentations: 1. Mr. Takayuki Sato explained document N 1045. Table 43 Row 24 - The shapes are different from those in ISO 2047 standard. Japan's proposal is to add new characters to accommodate the ISO 2047 pictorial symbol glyphs. 2. Mr. Michael Everson: If new characters are not added, Ireland wants the existing alphanumeric glyphs corresponding to (not identical to) ISO 2047 control symbols to be changed to the pictorial symbol glyphs of ISO 2047. Discussion: 1. Dr. Asmus Freytag: if the pictorial symbols are to be added to the standard - an annotation should be added. In terms of changing the shapes it does not seem to buy the standard anything. The missing pictorial symbols can be added to the standard - but naming them with control characters does not seem to be useful. It is not desirable to have a SYMBOL being encoded twice based on its intended usage. 2. Mr. Johan van Wingen: The name of the control character symbols - if they are the same as the CONTROL CHARACTER names, then there is potential confusion with C0 / C1 set. 3. Mr. J_rgen Bettels: the Alphanumeric symbols already exist - with names of control characters appearing in the name. In the pictorial form, it will be reusing existing symbols for multiple purposes. 4. Dr. Asmus Freytag compared the list of pictorial symbols in N 1174 (from ISO 2047) with the symbols that are already encoded in the standard, and created a collection of all the missing pictorial symbols as an attachment document to N 1174. The additional symbols required by SC 18 WG 9 (see discussion on N 1138 under section 6.1.6 later) were also included in this exercise. Note: This attachment and the attachment to N 1138, contain several symbols from different standards. ECMA staff, with the resources available at the ECMA offices, were able to print all the glyphs in these attachments within a very short time, instead of having to cut and paste or having to resort to hand- drawn symbols. This is an example of how ECMA resources can made useful to WG 2 work. Disposition: The ISO 2047 alphanumeric symbols, though with different glyph images, are already in the standard. Some of the pictorial symbols are also encoded, though with different names. WG 2 accepts the missing pictorial symbols with more general purpose use in mind than just for ISO 2047 purposes. The use of the existing pictorial symbols in 10646 by ISO 2047 can be pointed to by explanatory notes. A standing document with a collection of all symbols accepted for encoding in the next edition - with their proposed names, glyph images and tentative code position allocations - will be prepared, to be approved at a later date. Relevant Resolution: See resolution M27.10 (Collection of Symbols) under item 6.1.6 later. 6.1.3.3 N 1093 Braille Input Document: N 1093 Braille Letters; Kohji Shibano, Japanese Expert; 1994- 10-10; plus Attachment. This document was tabled in San Francisco meeting. The attachment - the proposal summary form - was added at this meeting. There is an outstanding action item from Meeting 26 in San Francisco for member bodies to feedback their input on the Japanese contribution; no contributions or comments have been submitted to WG 2. Discussion: 1. There were two views expressed: a. Braille dot patterns are considered as symbols for use in documents, in which case they can qualify for inclusion in 10646 b. They can be regarded as presentation forms for various alphabets, in which case, these do not qualify for inclusion in 10646 for coding. 2. From the information supplied in the proposal summary form, more information on its usage, the fonts for the glyph images, etc. is needed before WG 2 can proceed with the request. Disposition: Await more information. Action Items: a. Member bodies and liaison organizations are to check and input on the topic of Braille. b. The convener is to contact TC173/SC4 for the Braille standard (or CD/DIS) to get more information. 6.1.3.4 N 1094 Symbols from Japanese Printing Industry Input Document: N 1094 Requirement for extension of non-ideographic Japanese characters; Japan, Kohji Shibano; 1994-10-10; plus Attachment. This document lists a set of 2363 miscellaneous symbols used in the Japanese printing industry. The paper was tabled in San Francisco meeting. The proposal summary form attachment is tabled at this meeting. Discussion: 1. This paper is a progress report on collecting printing industry practice in Japan. 2. Japan is still to classify these symbols and address whether these are glyph variants of existing characters, whether they can be composed or they are characters required to be added etc. Disposition: Japanese member body has some more work to do in terms of refining the proposal before WG 2 can consider it. 6.1.4 China: N 1097 Input Document: N 1097 Proposing to supplement with the special script and character for Uighur, Kazakh and Kirghiz in Arabic; China; 1994-10 Chinese member body withdraws this proposal. 6.1.5 Ireland: N 1103R, N 1058, N 1132 6.1.5.1 N 1103R: Ogham Script Input Document: N 1103R Proposal for coding Ogham script; Ireland, Michael Everson; 1994-10-11 Presentation: Mr. Michael Everson introduced the document. It consists of a proposal summary form and attachments with several exhibits on the use of Ogham script. The proposal is to add 27 characters in either Category B or D (per N 1116). Ogham is an archaic script used in specialized contexts. It is only used for pedagogic text in Ireland. There are stones with carvings - carved bottom to top - using this script. Its use is primarily by scholarly communities - transcribed left to right - and its computerized form is slowly spreading with the use of computers in the educational institutions. Discussion: 1. The information provided is complete enough for WG 2 to accept the repertoire of characters, their names and glyph images. It was accepted as a Category D script. 2. The question of when these characters will be coded was raised. Early 1996 was accepted as a target date for encoding decision by WG 2. 3. There was a general discussion about which categories will be encoded by WG 2, when etc. Whether a national body contribution will be given higher priority compared to individual experts (for example); whether the script is used by an official language of a state versus it is for scholarly use worldwide, etc. 4. Also WG 2 will have to plan a schedule of work so that submitters of scripts will know when they can expect their contributions, once accepted, encoded in the standard. Disposition: WG 2 accepts the proposed repertoire and names. The script is classified as Category D. Code position assignment will be on hold until 1996. Category A proposals must take higher priority. Action items: a. The ad hoc on principles and procedures should examine N 1116 and update the guidelines as needed to address some of the prioritization concerns. b. Convener has to address the schedule related questions and update the program of work of WG 2 accordingly. Relevant Resolution: M27.9 (Ogham script): Unanimous With reference to N1103R, WG 2 accepts the repertoire and character names for Ogham script for inclusion in second edition of ISO/IEC 10646, as a Category D script. Its encoding is to be decided in 1996. 6.1.5.2 N 1058, N1132 - Irish Gaelic characters Input Documents: N 1058 Proposal for support of Irish Gaelic characters; Michael Everson, Ireland; 1994-08-23 N 1132 Proposal Summary for document N 1058 (Proposal for support of Irish Gaelic characters); Michael Everson, Ireland; National position; 1994-11-16 Presentation: Mr. Michael Everson presented. There are 3 characters proposed to be added to support Gaelic script. They have alternate Glyph representations depending on their use with Roman or Gaelic scripts. The first character will be part of the Registration proposal to ECMA. The SEIMHIU characters are non-spacing with two different glyph possibilities. In Gaelic text it looks like a DOT above. In the Roman script version, these appear as an h or H. To facilitate easy bi-directional transcription between Gaelic and its Romanized equivalent, two different versions of dot above (SEIMHIU) are proposed. Document N1132 lists all the combinations glyph images in the Gaelic script using the 'SEIMHIU' diacritic. Discussion: Dr. V.S. Umamaheswaran: which characters are being proposed? There are two glyphs - one combining and the other non- combining - shown for the same character. If one has to have both combining and non-combining property - depending on the context - it breaks the current character model in 10646. Disposition: Mr. Everson to revise the proposal based on the concerns raised during the meeting. Action item: All the delegates were asked to feedback their questions and concerns to Mr. Everson 6.1.6 Liaison SC 18/WG9: N 1138 Input Document: N 1138 Proposal to add new characters (Keyboard related) to 10646; Liaison statement from SC 18/WG9 to SC 2/WG 2, Alain LaBont_; 1995-01-30 Output Document: An Attachment to N 1138 'Proposed Coding of Symbols From ISO 9995'; Asmus Freytag. Presentation: Dr. V.S. Umamaheswaran presented the document. SC 18 WG9 had submitted the proposal for 29 additional symbols from the keyboard standards ISO/IEC 9959-xx. The document has been with WG 2 since the Washington meeting. A proposal summary form has been submitted by SC 18/WG9 liaison representative Mr. Alain LaBont_, Canada. Discussion: 1. A spelling error 'DISCONTINOUOUS' for item 13 on page 4 was identified. 2. WG 2 accepts the repertoire. it will be accumulated with other symbols (such as from N 1045 paper), and will be finalized at a later date. 3. Mr. Hugh Ross: Did not see any reason for postponing the code point assignments. 4. Dr. Asmus Freytag: Would like to examine all the symbols and will try to unify the symbols with those that are in the standard, required by other submissions (such as N 1045, N 1174, etc.) and make them of greater utility than for specific standards use. For example: 'Reversed Question mark of ISO 2047' - is a candidate to be unified with the Arabic question mark. In the process of doing this, the final names arrived at may not be the same as requested by the proposal, in which case, we may resort to parenthetical annotation or entry in the new informative annex to signify such uses. Disposition: The symbols from N 1138 were accepted by WG 2. An attachment to N 1138 was created by Dr. Asmus Freytag - with some names changed to more closely reflect the shape than its use or function. Where applicable, some annotations were included. The rationale for the name change is based on the potential for use of these symbols in wider contexts. Action item: The convener is to convey the status of their request in N 1138 to SC 18/WG9, along with the attachment to N 1138 that was generated at this meeting. Resolution: M27.10 (Collection of Symbols): Unanimous With reference to N 1138 and N1045, WG 2 will assemble a collection of symbols that have been accepted for inclusion in the standard, with tentative names and tentative coding assignments, to be approved at a later date. The initial members of this collection are in attachment to N 1138, and in attachment to N1174. 6.1.7 Individual Contributions from Mr. H. McG. Ross 6.1.7.1 N 1143 (N 983) Latin letters for African languages Input Documents: N 983 Individual Characters for First Addendum; Hugh McG Ross, UK.; 1994-03-23 N 1143 Latin letters for African languages - proposal summary form for N 983; Hugh McG Ross, U.K., individual contribution; 1995-02-01 Presentation: Mr. Hugh Ross presented the document. Document N 1143 is the proposal summary form with an attachment summarizing the request and referencing document N 983. 20 characters are proposed. Seven letter pairs are required for use in Yoruba, the national language of Nigeria. Three letter pairs are used in Hausa, a lingua franca of several Central African states. The missing grave symbol in N1143 attachment, in the glyphs for two of the characters - 'O with vertical line below and grave' - were pointed out. Some of these characters were in the first DP of 10646, but got lost. Dr. Michael Mann, London University, has given great assistance to identify the Latin languages used in Africa. These characters are required in level 1 in 10646. Discussion: 1. Mr. Mike Ksar: The contribution N 983 has been in WG 2 for comments for a long time. We should support the proposal. 2. Dr. Asmus Freytag: If the requirement is to use simple equipment and software, will we be better off encoding them as fully composed characters than using combinations? Are there any existing codes using precomposed characters? Not known. 3. Mr. Johan van Wingen: Would like to see some official confirmation from the Nigerian government to support the proposal. 4. Mr. Sven Thygesen: Have there been contacts with the countries. Yes - through university channels. 5. Are there any existing codes using precomposed characters? Not known. 6. Mr. Mike Ksar: Why these characters were not included in original standard? 7. Mr. Ross: Several proposals have been made 'ahead of their time' to this committee, and this is one of those. Action items: a. Unicode Consortium is to examine N1143 and feedback to Mr. Ross - for action at Helsinki. b. The convener or Mr. Ross is to check sources in the Nigerian government (for Yoruba), and other governments (for Hausa) to get their supportive statements. 6.1.7.2 N 1144 (N 983 & N 879) Additional Arabic letter and symbols Input Documents: N 879 Suggestion Concerning Addendum to ISO 10646; Hugh McG Ross; 31 March 1993 N 983 Individual Characters for First Addendum; Hugh McG Ross, UK.; 1994-03-23 N 1144 Additional Arabic letter and symbols - proposal summary form for N 879 and N 983; Hugh McG Ross, U.K., individual contribution; 1995-02-01 Presentation: N 1144 contains a proposal summary form and an attachment containing the summary of the requested characters from N 879 and N 983. These characters are considered to have been left out from 10646. The proposal includes: Two quotation marks from Iranian ISIRI Farsi standard. Five forms for the letter GAAF. Of these the Initial and medial forms were deleted from the list during the presentation, leaving three for consideration. Arabic Letter BBEH for Sindhi and TEHEH with BAR for Urdu. Discussion: Mr. Alaa Ghoneim: The opening and closing quotation marks are, in current implementations, considered to be Font Variants in different Arabic countries. Arabic Letter GAAF - could be considered as a font variant of Arabic Letter GAF. The glyph in 10646 for letter GAF does not have the small squiggle (looks like an s) in the middle of the glyph image is in 10646. The same applies to the Sindhi letter BBEH ? 06D0 is called the letter B? It may be that the 10646 shape is different. Mr. Michel Suignard: Would the two shapes for GAAF both appear at the same time in a string? - Not known. Mr. Ross - The Library of Congress document is the reference. The answers can be found there. Disposition: WG 2 considers these characters to be glyph variants of existing characters. Alaa Ghoneim will assist Mr. Ross to prepare informative notes or annotations to be included in the new annex on additional information on characters for the different shapes for the quotation marks, the GAAF forms and the letter BBEH. Mr. Ross is to get the needed confirmation regarding Arabic Letter TEHEH with bar for Urdu. 6.1.7.3 N 1145 (N 983) Two Armenian Symbols Input Documents: N 983 Individual Characters for First Addendum; Hugh McG Ross, UK.; 1994-03-23 N 1145 Two Armenian symbols - proposal summary form for N 983; Hugh McG Ross, U.K., individual contribution; 1995-02-01 Presentation: Mr. Hugh Ross presented. N1145 contains the proposal summary form with a reference to N 983 and summarizing the two proposed combining characters required for Armenian, with SGML Draft TR 9573-15 as the source reference. This document is put forward as a suggestion. Mr. Ross will have no objection to await input from Armenian national authorities if one comes up in the future. Discussion: Mr. Johan van Wingen: Netherlands will be an interested party. Official Association for Armenian Studies, Netherlands will be contacted. SGML TR 9573-15 is considered to be an unreliable source of reference due to several negative comments from several member bodies. Disposition: On Hold till WG 2 hears from Armenia. 6.1.7.4 N 1146 (N 985) Extra Electrotechnical Symbols Input Documents: N 985 Electrotechnical Symbols for First Addendum; Hugh McG Ross, UK.; 1994-03-28 N 1146 Extra Electrotechnical Symbols - proposal summary form for N 985; Hugh McG Ross, U.K., individual contribution; 1995-02-01 Presentation: Mr. Hugh Ross presented. N 1146 is the proposal summary form referencing document N 985. Ten additional symbols are proposed to be added to complement the IEC Technical Symbols list. Disposition: WG 2 accepts these symbols and they are to be added to the symbols to be considered for encoding in 10646. The appropriate IEC TC should be included as an interested party on the subject. 6.1.7.5 N 1147 (N 987) Subscript Ten Input Documents: N 987 A real test for updating of 10646-1; Peter Fenwick, UK.; March 1994 N 1147 Add Subscript Ten - proposal summary form for N 987; Hugh McG Ross, U.K., individual contribution; 1995-02-01 Presentation: Mr. Hugh Ross presented. N 1147 contains the proposal summary form to add 'SUBSCRIPT TEN' referencing N 987. Discussion: 1. Mr. Johan van Wingen: quoted from a paper from ALGOL - SC 22 decided to withdraw ALGOL(?). ISO 1538 (?) is no more. There is no justification. 2. Mr. Michael Everson: ALGOL may not be the only justification. It may be required for example LOG 10. 3. Dr. Asmus Freytag: One possible reason is that it is needed in plain text. The other possible reason is for compatibility - for example with ALGOL. Neither of these seem to be the case. Unicode consortium is not interested. Disposition: Unless there is more justification for inclusion, there seems to be no interest in adding this character to the standard at this time. The proposal is not accepted. 6.1.8 N 1079R, N1079R2, N 1195 Hebrew cantillation marks Input Documents: N 1079R plus R2 Proposed addition of Hebrew cantillation marks to 10646; SII, Israel; 1994-09 N 1195 Hebrew cantillation marks in ISO/IEC 10646-1; Standardization Institution of Israel (SII); April 1995 (Note: N 1195 consolidates N 1079, N1079R and N1079R2 contents into a single document (R2 was NOT a replacement for R)). Presentation: Mr. Stefan Fuchs presented. Thirty one (31) cantillation marks used in religious texts in Israel taken from Israel national standard 1311 part 2 are proposed. Two are spacing. Others are combining. N 1195 contains the relevant background information. Electronic Fonts form are available and will be provided at a later date. Discussion: Comments and questions were raised by Messrs. Michel Suignard, Mike Ksar, V.S. Umamaheswaran, Michael Everson and Alaa Ghoneim. The following is a summary of the points raised: 1. There is a need to clarify whether the proposed Cantillation mark upper dot has a different property compared to existing upper dot. For example, does it have some inherent directional property similar to other Hebrew characters? If not, why should it not be unified with the existing upper dot? 2. There is a need to clarify that only the two columns 059, 05A and the code position 05C4 are being proposed, removing the ambiguity as to what currently exists and what is being proposed as new. 3. Israel standard uses 'accent' in the names of characters in the list instead of the term 'mark'. These names are in the English versions of the national standard also. 4. Characters at locations 5BD, 5BE and 5BF seem to be in different order in the Israeli standard 1311 part 2 (Exhibit Table 1 in N 1195), from those in Table 14 Row 5 of 10646. Also the glyphs are not consistent between the two. The intent of the Israeli standard was to be the same as the 10646 standard. 5. Answer to question 8 in the proposal summary form regarding compositions is not provided. A list of intended use of combinations and their corresponding glyph images is requested as additional information. Disposition: Mr. Stefan Fuchs will provide answers to various questions raised at the meeting by the next WG 2 meeting. 6.1.9 N 1104 (addition) Canadian Syllabics Input Document: Addition to N 1104 Proposed Unified Canadian Syllabic Character Set Repertoire, version 2.0 (Comment on WG N984); Michael Everson, Ireland, expert contribution; 1994-10-11 This document was tabled as missing part of N 1104 for circulation to WG 2. It was not discussed at this meeting. It will be taken up as part of discussions on Canadian Syllabics in the future. 6.1.10 N 1168 Sources of Compatibility Characters Input Document: N 1168 Sources of Compatibility Characters submitted from Canada; V.S. Umamaheswaran, Canada, expert contribution; 1995-03-11 This document was input in response to one of the action items from WG 2 Meeting 27 in San Francisco. An annex is to be prepared by WG2 using the information in this document as one of the inputs. The document was not discussed at this meeting. 6.1.11 N 1182 Kang Xi Radicals Input Document: N 1182 Proposed to add 210 Kang Xi Radicals, TCA; 1995-03-23 N 1182 - from TCA - a liaison contribution and has been tabled for information at this meeting. It will be considered at the next meeting. Action item: WG 2 requests IRG to review the TCA contribution and give their evaluation to WG 2 by the next WG 2 meeting 6.2 Character Ownership Input Document: N 1139 Character Ownership; Japan national body, Takayuki K. Sato; 1995-01-27 Presentation: Mr. Takayuki M. Sato presented the document. The proposal is to have an owner assigned for each character in 10646 WG 2 is faced with request for new characters or changes to existing shape or name etc. In several cases, WG 2 is unable to assess whether other countries or user groups may be affected or not. Some countries sometimes reject acceptance of a character proposed by another country even without attending the WG 2 meetings. The document proposes the rights of the owner etc. Discussion: 1. Mr. Michel Suignard: Has objection to the concept of ownership of any character. The rights of the owner as outlined in this document is far-reaching. It is a good idea to have a 'sponsor', and some information as to how a character got introduced into the standard. 2. Mr. J_rgen Bettels: The reason for the proposals are given in the paper. Proposal by country A being challenged by country B - can still be the case whether or not either country is made the owner, sponsor etc. 3. Dr. Asmus Freytag: Welcomes the thoughts put into this document by Japan. Rarer the character, the idea of owner or sponsorship is good. A level of comfort is needed at WG 2 in being able to look at a proposal, and accept it after reviewing the usage of the character etc. However, assigning special rights to some owner may not solve the problems identified. 4. There are two items: Modifications and deletions - WG 2 should not even consider this - if it is a mistake leave it alone. So let us leave it out of the discussion. Only additions are to be considered. The notion that a particular script belongs to a particular member body is not quite in line with the past experience. The ranking of liaison members below the member bodies is not acceptable from Unicode consortium point of view. Ad hoc groups on different topics have been the vehicle set up for dealing with various matters. The responsibility for any script cannot be left with any single group, a member body, for example. WG 2 should not give up its responsibility of deciding on a script's acceptance and whether or not it is in accordance with the principles behind the standard. 5. Mr. Michael Everson: The question of expertise and responsibility is more central than the ownership question. The idea of WG 2 maintaining a database of what characters are there and who was the original sponsor etc. should perhaps be resurrected. 6. Mr. Johan van Wingen: There are two separate topics. The first topic addresses the requirement: for new characters proposed, whether WG 2 believes it has sufficient rationale to accept them. Such characters may be needed by a population in one country or some migrant population in another country. The other topic is to know where a character originated - for example, characters in current 10646. Some clarification as to why a character is included in a standard is probably useful. Several cases can be handled by using the ad hoc group approach - with appropriate expertise in the group. In some cases, the member bodies of different countries, for example Georgia, was not even consulted. 7. Mr. Mike Ksar: issue is not what is in the standard. What do we do with new proposals? For example, a migrant population's needs or some country who is recognized as the owner of some script? 8. Dr. V.S. Umamaheswaran: May be a group of 'interested parties' for a script should be recognized, and a 'keeper of the script' should be recognized and assigned the role of being the monitor. 9. Mr. Michael Everson: Cited the example of Sinhalese - who is the owner? 10. Mr. Takayuki Sato: the spirit of the Japanese proposal is -- 'do not give freedom to any organization that is not considered to be a sponsor or an interested party to scuttle legitimate proposals'. 11. Mr. Sven Thygesen: Through the procedure document (for example N1116F form) or the administrative tools, we could identify the member bodies who are interested and make the group of interested parties responsible. 12. Mr. Mike Ksar: What if an expert disagrees with a national body position? He/she has to work with the member body. WG 2 is not ready to relinquish its responsibility of decision making. Let us understand that we will be addressing only new scripts. WG 2 has to be comfortable that the sponsor is legitimate and competent enough to be able to assist WG 2 in its decisions. We should also document the fact that we have tried to reach all known interested parties on a specific script. We should not make a statement that only a particular member body or another specific group has the sole ownership over any specific script. We should be able to identify a source of a script that we can reliably depend on for its legitimacy etc. The N 1116 form may be modified if needed to keep track of such information. 13. Mr. Bruce Paterson: N 1116F - the form contains WG 2 related information -- Document number and status are the current entries in this section. We can add another section here to keep track of a List of Interested Parties (or organizations) before we can make a decision on the subject proposed, in addition to the originator of the proposal. 14. Mr. Sven Thygesen: Supported the suggestion by Mr. Paterson. The sponsor should be also asked a question -' have any other experts or users of the script been consulted and identify the list?'. 15. Mr. Johan van Wingen: We could identify the groups who have been consulted including learned bodies. 16. Dr. Asmus Freytag: It is a good idea to have list of sources consulted on specific scripts. The sources can be anyone of member bodies, liaison organizations, experts on a particular script, a language interest group etc. We can keep track from WG 2 point of view. 17. Mr. Michael Everson: Question to Mr. Sato - do you see a distinction between the responsibility of WG 2 versus the proposer of a script/character? 18. Mr. Takayuki Sato: the original sponsor of a character should have a larger voice in some of the decisions being made. 19. Mr. Mike Ksar: The sponsor should have a greater responsibility in assisting WG 2 to progress the work. The decision making is still WG 2's. Disposition: Add a subsection under WG 2 administration items in the proposal summary form N 1116F - to list all the parties consulted or who would be interested in the characters proposed, and who WG 2 has received feedback from as the subject proposal progresses through WG 2. Action item: This will be an action item to ad hoc on Process and procedures to update N 1116 to address the concerns in N 1139 and the discussion at the meeting. N1202 was the document number assigned to the modified form N1116F and the revised N1116. Note: This item was in the form of a draft resolution "WG 2 accepts the revised Proposal Summary Form in n 1202", however, it was removed from the final list of resolutions in favour of the action item above. 6.3 O-zone allocation Input Document: N 1140 Reserve 4K of O-zone code space for linkage area with composite sequence; Japan national body, Takayuki K. Sato; 1995-01-09 Presentation: Mr. Takayuki Sato presented the document. The proposal is to reserve about 4k space in O-zone. The 4K space can be reserved for any purpose at all - one of the uses being the link to composite sequences. The proposed 4K space may or may not be enough - it is just arbitrary. Discussion: 1. Mr. Mike Ksar: does it mean that this 4k will be permanently allocated? 2. Mr. Takayuki Sato: once we get confidence in technology then we can go ahead and use it. It will be temporarily reserved. 3. Mr. Johan van Wingen: we have a similar space requirement for Sorting purposes - in the BMP. 4. Mr. Bruce Paterson: the private use zone already has 24 rows available and it should be more than enough for such purposes. 5. Mr. Johan van Wingen: if the definition of PU includes such use it should be OK. 6. Mr. Michel Suignard: is the composition proposed any thing new? Is the PU zone not adequate? 7. Dr. Asmus Freytag: we are not close enough to using up the space - the 4k space may not be in danger of being used up. One could either use PU space or by using other technology for equivalencing without ever using the BMP. An intermediate code can be used - and it will NOT be UCS. The technical need for the case proposed does not seem to be there. 8. Mr. T.J. Kang: In some implementations the data is stored (in files) in UCS encoding. In the memory for temporary processing one could use any coding at all without having to reserve spaces in the standard - without having a better understanding of the need for the proposed reserved space. The requirement is not clear. 9. Mr. Takayuki Sato: If our projection is that we are not going to use all of O zone now, then it is OK. The message is NOT to use up all of O zone right now. The question that may be asked of WG2 would be - 'why are you not using it?'. One possible answer can be 'for linking to composite sequences', for example. 10. Mr. Mike Ksar: Before we allocate any code points to O zone we should be careful not to use ALL of it. WG 2 may want to keep some unassigned for catering to technologies still to come. We do not know how much space will be needed - 4K has been suggested by Japan. Disposition: No specific action for this meeting. WG 2 should keep in mind that all of the O-zone is not used up - based on N 1140. The lower numbered 4K code positions of O-zone should be kept unallocated as long as possible. 6.4 Additions to repertoire 6.4.1 Korean Hangul Syllables Input Documents: N 848 Modified Korean position; Korea; 2 July 1992 N 1158 Korean national position for adding Hangul characters; Korean national body; 1995-03-03 N 1170 Canadian Position on Korean Proposal in N 1158 for adding Hangul characters; Standards Council of Canada; 1993- 03-10 Output Documents: N 1198 Working draft of proposed draft amendment to ISO/IEC 10646-1: 1993(E); Korean Bureau of Standardization (KBS); 1995-04-05 N 1199 Background on Korean Coding; Korean Bureau of Standardization (Under Preparation) Presentation: 1. Mr. Won Seop Lee from KBS presented the document N 1158. He gave a brief background behind the proposal from KBS. In July 1992, 11172 modern Hangul syllables were presented to WG 2. At the end of the Seoul editing meeting of WG 2, 4516 syllables were left out of 10646. Since then KBS has published the national standard - KSC 5601 with the full 11172 characters. 2. Mr. T.J. Kang explained further. The proposal in Annex D of N 848 is complete and all the information is given there. It is considered to be Category A. The character names are given and are in accordance with Annex K. The character shapes are legible. An updated Proposal Summary Form will be prepared and submitted. At the Seoul meeting, Korean national body made a mistake, and other member bodies also made a mistake. Of the 11172 characters having only 6656 characters is quite useless. At that time, the Korean National standard did not include these - but a few months after publication of 10646 the additional characters were added in the national standard. It is unfortunate that the current set is inadequate for Korean users for everyday needs. We must have the full character set. We would like to be given the opportunity to rectify the mistake and do the right thing. This is what the proposal contains. Discussion: (Note: The following is a record of all the dialogue that I have captured during the meeting. Due to the sensitivity associated with this particular item, being a historical first, and hopefully the last, in terms of what WG 2 has been asked to do by the Korean member body, I thought I will leave it unabridged, for you all to read. My machine did quit temporarily though - and I was able to fill the gap with notes from Mr. Michael Everson. ---- V.S. Umamaheswaran.) 1. Mr. Akio Kido: Question - according to N 1158 - it is category A - there is no combinations etc. 2. Mr. T.J. Kang: There are already duplication - the existing 6656 characters can be composed by using Jamo components. The proposal is for Level 1 implementation - i.e. fully composed characters. 3. Mr. Takayuki Sato: You would like to keep the combining Jamos - it may be useless. 4. Mr. T.J. Kang: No. Some implementations may use the Jamos, others may use fully composed characters. 5. Mr. Mike Ksar: Is the proposal to Deprecate the existing 6656 characters? 6. Mr. T.J. Kang: What does it mean to deprecate? Korea does not care if the existing 6656 character positions are there or not. 7. Dr. Asmus Freytag: Clarification - combining Jamos in 10646 can in fact be used to access not only the 11172 but also a larger repertoire of ancient Hangul. The Jamos are not being proposed to be withdrawn. 8. Mr. Michael Everson: Can the deprecated code positions be used for other purposes. 9. Mr. Bruce Paterson: Other standards have the practice of having up to one edition - still good for one extra edition. 10. Mr. Johan van Wingen: the meaning of deprecation is that they are slated for removal for the next edition. 11. Dr. Asmus Freytag: under ordinary circumstances - we should not have deprecation as a normal practice. Unlike other non- coding related standards, we cannot practice it. We should not follow the FORTRAN lead. 12. Mr. Arnold Winkler: This is a character set - which seems to have been designed for people who are using them. 13. Mr. T.J. Kang: I would assume that there is no implementation that really cares for it. 14. Mr. Michael Everson: Would it be acceptable to simply add 4516 characters? 15. Mr. T.J. Kang: Korean national committee had a long discussion. We come to the conclusion that such a proposal will not be acceptable. The Korean national standard has them in a specific order. Having a large character set not in the desired order is not considered to be beneficial. 16. Mr. Mike Ksar: The 6656 characters are not in the right order - even if they are there. The additional 4500+ characters may be in order, but the others are not. 17. Mr. Sun Gi Hong: when the Jamo characters were proposed the intent was to support specifically the old Hangul. It was not the intent to create the modern Hangul. The full set is not creatable using the Jamos. 18. Mr. Teow-Hin Ngair: Singapore have implementations using the existing Korean code positions. There are implementations that will be impacted. An effort will have to be made to compensate all existing implementations to provide the cross reference facility etc. 19. Mr. T.J. Kang: Korea would like to commend Singapore for using the existing set; even in Korea they have not used it. The set has a subset of an existing standard - supplementary A and B were created but never accepted by users. Supplementary A was chosen based on frequency of use. At SEOUL meeting we managed to get somehow 7000 character space - after set A was chosen some 1800 characters were picked at random making the subset B useless. The transition can be more than well supported by Korea. 20. Mr. Mike Ksar: Korean national body will need to supply the necessary cross mapping mechanisms etc. 21. Dr. Asmus Freytag: Unicode consortium would like to take part in assisting the cross mapping tables. The consortium went through two phases - one was to whether or not to accept the extra characters. The other one was to whether or not to re- assign them. Normal procedure is that ordering is not important in the standard of 10646. Korean happens to be a special case - the ordering relates to a way to get at the constituent parts. The amount of extra resources needed to carry the equivalent ordering related information can be quite significant, and it is prevalent to be able to get at the equivalent components. In the Korean case, the ordering is not simply for the purposes of collation etc. but also for transforming between fully composed form and its components. 22. Mr. Takayuki Sato: this problem is well known from Seoul meeting. This issue has been discussed at the Seoul meeting. That meeting was editorial - Korean proposal could not be entertained. One solution from Korea is on the table. Has Korea alternate proposals? 23. Mr. Akio Kido: From the conformance point of view - one could claim conformance to existing 10646 -- but if deprecation is permitted how can conformance be claimed? The collation and ordering if is accepted in principle as the rationale for re- shuffling, then will WG 2 accept the reshuffling? 24. Mr. Mike Ksar: claims of conformance will be to a specific year or version of the standard. Collation and ordering is a different story. 25. Mr. Akio Kido: JTC 1/SC 22 has the practice of obsolescence notification. This may be a mechanism to consider. 26. Mr. Zhang Zhoucai: China has the same concerns as Japan with respect to ideographs. Question to Korea - is there a way of composing the 11172 characters? Yes: there are 240 Jamos components that can be used. 27. Mr. T.J. Kang: 9 characters were added explicitly at the request of Korean users in China. If a survey is done now, there will be more characters in use today. The Korean proposal is for a CLOSED set and KBS is not planning to come back with any more as part of the repertoire. All additions will be using only the Jamos composition method. Regarding compliance - we would like to have the seal of compliance to 10646. However, for selling to customers in Korea, having seal of approval to 10646 without accepting current Korean proposal will be of no use in Korea. KBS were so serious that they were ready to create an alternate 10646 if 10646 did not accommodate the Korean needs. Of several alternatives, Korea has chosen one rational method to order the characters in the standard. 28. Mr. Mao Yong Gang: China has a similar requirement for Yi - large, middle and small character set. Looks like the proposals were rejected. 29. Mr. Mike Ksar: pointed out that the characters were NOT REJECTED. There have been feedback on the presentation - but not rejected. 30. Mr. Zhang Zhoucai: China has requirement for additional 5000 + characters to be added to BMP. Tibetan proposal is not yet solidified. China's concern is that addition of characters is not just related to Hangul. It is a MAJOR change. 31. Mr. Takayuki Sato: The impression given is that the current set of characters are not ordered. Within each block of characters there is a natural order. However, when the blocks are combined together, the natural order within the blocks become useless. 32. Mr. Akio Kido: Clarification - Ordering within 10646 code table - is it within the scope of WG 2? The ordering work for processing is within the scope of SC 22. The question is whether ordering within the code table is significant to the work of SC 22 - a question should be asked to SC 22. There is also a statement in 10646 that no characters will be removed. 33. Mr. Mike Ksar: If someone is impacted by deletion of removal etc. the person who has implemented by 10646 should not be adversely hurt. Conversion tables have been developed using existing 10646 definitions. The existing conversions do convert data and store them. 34. Dr. Asmus Freytag: One can take an existing practice of computerization in a country and migrate to using new standards. One should minimize the potential obstacles that might be in its way. 35. Mr. Akio Kido: Clarification: Category 1 means no combining sequences. Level 1 is what Koreans want. 36. Mr. Arnold Winkler: We should go to JTC 1 and ask to make these characters immediately available. 37. Mr. Michael Everson: Is it acceptable to Korea to add 4516 characters without reordering? 38. Mr. T.J. Kang: No, this is not wise. It does not help make 10646 directly useable (or acceptable) in Korea. 39. Mr. Michael Everson: We should support Korea in correcting what they themselves have called a serious mistake. 6656 useless characters serve no purpose. Current implementation of Hangul is no good. I propose that we seriously consider Arnold Winkler's proposal to correct this situation. I understand China's concern about the implications of adding 4516 characters. In this case I would like to propose that the newly liberated areas be allocated to Category D script sand would offer Ogham as the first tenants in the newly-vacated space. 40. Mr. Bruce Paterson: The UK requirements is that we need ONE international standard, no divergence. The standard must be stable and final by July of this year. Is there a migration path for KSC 5601 to the new standard? (Answer: yes) 41. Dr. V.S. Umamaheswaran: Explained document N 1170 - the Canadian member body position. No objections to accepting the additional 4516 characters and their encoding in the BMP. But Canada is against moving the existing 6656 characters to another contiguous area along with new 4516 characters, simply for the reason of implementation convenience. 42. Mr. T.J. Kang: Some early implementations are not fully using 6656 characters. These will have to migrate and will be penalized. However, they will need to migrate anyway to support full KSC 5601 sooner or later. If they are currently using Jamo components they are not impacted. Otherwise, they will have impact. 43. Mr. Mike Ksar: One should not forget the databases to migrate. 44. Mr. John McConnell: what about interchange, between composite and precomposed syllables? From the conformance point of view - which is the preferred one - the fully composed 11172 characters or composition using the existing Jamos? 45. Mr. J_rgen Bettels: Switzerland has no issue in accepting the Korean position. However, if deprecation will lead to keeping 6656 characters locked up, as in indicated by Canada, it will not be acceptable. 46. Mr. Johan van Wingen: Procedurally -- The question to be answered is 'No deprecation' is OK or not? Will this undermine the confidence in ISO standards? 47. Mr. Mike Ksar: Perhaps this indicates a willingness of ISO bodies to BEND to meet new requirements than being RIGID. 48. Mr. Johan van Wingen: Will it lead to 'DAMage claims'? Perhaps. Is this setting up a PRECEDENCE - Yes. 49. Mr. Mike Ksar: If the Canadian position is taken as consensus to this group, we must help the Koreans to utilize the space for the two coding areas. 50. Mr. Sven Thygesen: will this decision have implications to Japan or China or other character sets? 51. Mr. Mike Ksar: No, this should not happen. The only other potential case that he can think of is that of ISCII. But all proposals must be considered on their own merits. If what is in 10646 is unusable, we must be flexible enough to handle it adequately. 52. Mr. Sven Thygesen: Denmark favours Mr. Arnold Winkler's approach, removal of characters. 53. Dr. Asmus Freytag: The 'ordering' is a confused issue. Korean is a closed repertoire and ideographic is not. Ordering only makes sense in helping to find the pieces as you are processing. Ideographic as analogy is completely out of place here. In Unicode they were quite skeptical about precomposed syllables in general. They wanted to see the 4516 new codes, and they also wish to have natural ordering. IF consensus can be reached on that, Unicode Consortium says this is an emergency procedure that addresses a grave problem in a particular script that has some historical problems. It is not the precondition for this kind of change in general. Unicode Consortium wants a decision in a predictable time frame. July would be a good time frame (as UK says). We do not want to lose the unity and the momentum we have had following on from the merger. (This is very important to Unicode) 54. Mr. Bruce Paterson: Ordering is normally seen as dictionary ordering; the Korean ordering may match the dictionary to make the conversion algorithm simple. For conversion between precomposed and combining Jamos, the motivation is completely different. 55. Dr. V.S. Umamaheswaran: For input and output processes, UniHan has similar requirements. In the case of Korean the issue of ordering is a tradeoff with the trans-coding issue. 56. Mr. Bruce Paterson: The question of ordering is thought of as a human sees them in a book. In the case of Korean it is a little bit different - not a dictionary look up necessarily - it is for the purposes of converting between Jamos and getting the composite. 57. Mr. Teow-Hin Ngair: The ordering is similar but not the same as the ideographic ordering. 58. Mr. Sun Gi Hong: The intrinsic nature is such that the ordering is maintained. By looking at the code point one can decide what form it is. 59. Dr. V.S. Umamaheswaran: is the penalty of accepting or not accepting the Korean proposal - just a matter of Trans-coding? Yes. 60. Mr. Akio Kido: We have in IRG a similar situation - if the Korean proposal for coding also is accepted along with the ordering - WG 2 will be setting up a precedence. IRG members will be having a similar expectation from WG 2. 61. Mr. Mike Ksar: This proposal should be taken in its own context. Interim Summary: (The delegates had an evening to think over all the discussions on this item. The discussion resumed the following day - Wednesday AM.) Mr. Mike Ksar: Proposal from Korea is to remove existing code positions for 6656 characters in 10646 and allocate 11172 characters in BMP. Several views were expressed - should we deprecate or not, should ordering be an issue. Existing code positions are individually ordered within each block but not collectively. Korea would give migration assistance / tools for those who might have implemented current standard. Singapore, UK and Japan had indicated that they may be affected. The ordering issue of Hangul is not related to the ordering of IRG Han characters. The two are unrelated. Further Discussion: 1. Mr. Zhang Zhoucai: Clarification of the requirement: Korea wants to add 4516 characters; second move the existing 6658; and move them to a contiguous area with correct ordering. This is not clearly stated in the paper. 2. Mr. Mike Ksar: The net of the paper is as summarized earlier. 3. Mr. T.J. Kang: Yes - the requirement is in line with Mr. Zhang Zhoucai's summary. 4. Mr. Zhang Zhoucai: Is a similar process be applicable to other scripts? 5. Mr. Mike Ksar: If what is in the standard is not usable and if we have to move it -- for example, ISCII equivalence -- it will be a similar situation. However, it will not be applicable in general for all scripts - for ex: IRG HAN sets. However, simply for ordering, it will not be allowed. The standard clearly states that it will not reallocate code positions. 6. Mr. Zhang Zhoucai: It seems to be inconsistent. 7. Mr. J_rgen Bettels: Korean delegation clearly admitted that the initial allocation was a mistake. However, the situation is not quite the same for CJK. 8. Kolbj_rn Aamb_: Addition of a hole in the standard is disastrous. The vacated positions would be a problem. 9. Dr. V.S. Umamaheswaran: The impact on existing implementations should not be underestimated. 10. Mr. T.J. Kang: I can understand the implications on existing implementations. Korea is willing to assist with code conversion and migration tools. The reason we want to have proper ordering is to avoid the conversions if possible for the future. 11. Dr. V.S. Umamaheswaran: Ordering seems to be required only by some applications - many applications do not seem to be dependent on the ordering. 12. Mr. Zhang Zhoucai: China is faced with a similar situation with Han characters. Most frequently used ideographs are in the BMP. To correct the mistake in the current standard, Korean situation is similar to the Han situation? 13. Mr. T.J. Kang: We tried before - now we are back requesting WG 2 to rectify the unsatisfactory situation. 14. The proposal was originally made to WG 2, but they got rejected. The cost of implementing the scattered set proved to be too much for the implementations. 15. Mr. Mike Ksar: We wanted Korea to agree with WG 2 - in order to proceed with the 10646 publication we agreed to include only those that had been standardized nationally at that time - we could not give them the full set at the time of publication. 16. Mr. Akio Kido: We are discussing different points -- first we should agree on 'accept or not' the additional characters. Then we should decide the coding issues. There are several questions: Ordering, Deprecation, in BMP or not, etc. 17. Sun Gi Hong: The ordering has many different views -- better term is closed set. U, M and A are typed in. The intrinsic structure is created as a closed set. Then we have to delete one syllable - we have to go back to the fully composed character in the closed set. There is a hit on the inputting and editing process. Existing implementations have to be re-engineered. 18. Mr. Michael Everson: Ordering seems to impact several aspects of processing. The costs may be larger in the longer run to use trans-coding. 19. Dr. V.S. Umamaheswaran: There must be a way to use an intermediate private code or existing national 11172 standard as closed set and use trans-coding to the 10646 world for data store etc. 20. Mr. T.J. Kang explained the three dimensional model of the closed set: C1xVxCf = 19x21x22 = 11 172. By picking a point of C1, V and CF by using a simple arithmetic to get to the code position. The deletion example of removing a syllable in the input processing etc. was presented to explain the relative ease of processing for input/output processes. The trans-coding of data will involve 22K of resources and additional performance constraints. 21. Mr. Michel Suignard: There seems to be no question about need for additional 4516 characters. The ordering issue is certainly related to performance area and it seems better to have the same order for both 10646 as well as the closed set. 22. Mr. Kolbj_rn Aamb_: The trans-coding resources can be added for the Korean version. 23. Mr. Mike Ksar: The customers do have to pay for the additional resources. 24. Mr. J_rgen Bettels: The 3 dimensional model raises the questions - are all the combinations used? The system has not changed since 1933. Some 5 Jamos were deprecated There is a change in the choice of software and hardware in the country. 25. Mr. Teow-Hin Ngair: Between the old and new national standards - there is a change. 26. Mr. T.J. Kang: the study conducted by the Korean Ministry have mapping tables to assist in the migration of the customers of existing code positions. 27. Mr. Zhang Zhoucai: Question - are all the 11172 characters modern Hangul? Is the proposed coding only for presentation or for storage etc. 28. Mr. Mike Ksar: The impression is for BOTH. Some implementations may choose to compose, others may like to keep them as precomposed. Towards a Consensus: Mr. Mike Ksar: We would like get some consensus by dividing the question into three separate items: Q 1: Does WG 2 accept the request for the additional 4516 characters from Korea to the repertoire of 10646? Mr. Zhang Zhoucai: clarification - repertoire or coding also? Only addition to repertoire for this question. Q 2: These additional characters are being requested to be included in BMP. Does WG 2 accept this request? China: We cannot support the addition into BMP of the script proposed in isolation till all the scripts that are candidates for addition to O-zone are examined together. If we are to take a ballot position we would abstain. Q 3: Whether we want to MOVE the existing 6656 characters in the standard and move them to a contiguous area along with the new 4516? 1. Canada: NO - in the position paper N 1170. 2. Netherlands: Wholesale replacement into a contiguous block is favoured. Any other solution will be undesirable. We have to delete the existing 6656 characters. 3. Japan: The proposal now is beyond just the addition of 4516 characters. We are talking about moving the existing 6656 characters. Abstains at this time. We would like to examine the code space availability in BMP before we end up in adding 11K. 4. UK: Abstains on this resolution. We would like to see this matter settled by no later than July. 5. Ireland: There is no wisdom in adding characters without putting them in the proper order. 21000+ are available for encoding - it will leave about 16656 characters for future standardization. 6. China: We would like to have a better understanding of the principle of allocation of characters in the BMP - the contiguous allocation is a sensitive issue. We would like to request WG 2 to make some principles as to how to deal with contiguousness of general script requirements. We cannot do it only for a single script. 7. Singapore: We agree to the reallocation. But it is conditional to availability of necessary migration tools. 8. Switzerland: If it is REMOVAL we are in favour. But if it is deprecation, we are against. 9. Mr. Akio Kido: IRG members have not discussed this issue. IRG's position is abstain at this time. 10. Denmark: The spare area of about 16K - Denmark will support the resolution 11. France: In favour of reordering. 12. US: Arnold Winkler - will accept the reordering. 13. Unicode Consortium: Liaison statement would be to support the removal of existing code positions. 14. Norway: It puts us in a situation of undermining the confidence in the standardization process. Each case has to be taken on a case by case basis. Norway abstains. 15. Egypt: Abstains on this issue. We need to understand the allocation of other scripts in BMP., and will await the IRG position. 16. Sweden: Abstain 17. Canada: A related question - are we permitted to REMOVE than DEPRECATE? 18. UK: Deprecation is not a part of the procedure in JTC 1. In order to give some stability to the standards, it is advanced warning to the users. 19. Switzerland: Are we trying to redefine the zones? NO. Disposition: Korean member body is requested to prepare draft text for a pDAM to remove existing 6656 modern Hangul, and allocate 11172 positions starting at the end of O-zone above the S-zone (following the definition in pDAM-1). The editor is instructed to prepare a pDAM-5 addressing the resolutions on the Korean proposal. The pDAM will identify the deletions and additions to the standard reflecting the Korean proposal, with assistance from the Korean member body -- within 3 weeks and forward it to SC 2 secretariat for an SC 2 ballot. Korean member body is also requested to prepare a background document describing the rationale for their proposal in more detail capturing all the discussions at this meeting. This background paper should be sent along with the pDAM-5 for ballot as information to member bodies of SC 2. Objection was raised by Denmark that WG 2 should have the option of seeing a draft of pDAM before it goes out for ballot. N 1198 was created by Korean member body (with assistance from Dr. Asmus Freytag). N 1198 will be used as part of the instructions to the editor. Draft Resolution: The resolution related to the removal and reassigning of the existing 6656 Hangul syllables proved to be the most difficult one to be addressed. The first draft resolution had the following wording after some suggested corrections during the discussion: "With reference to N 1158, WG 2 resolves to remove the existing 6656 Hangul syllables from (3400-4DFF) in the A- Zone and encode them together with the new 4516 syllables in a contiguous space in a normal order from AC00 to D7A3. WG 2 further resolves that the vacated code positions 3400-4DFF can be used for future standardization." This draft resolution text got a vote of 7 Yes, 2 No, and 6 Abstains - not enough to pass. Further Discussion on the resolution: 1. Mr. Alaa Ghoneim, Egypt, volunteered to explain that his abstention was based on the word 'removal' without giving any warning or time to migrate to existing users of the code positions being moved and potentially other characters being assigned to the vacated positions. Mr. Ghoneim asked Korean delegation if they will be willing to withdraw their request to have contiguous encoding. Korea replied NO. This led to further discussions and several delegates were now willing to accept a form of limited deprecation which they had opposed earlier. 2. Mr. J_rgen Bettels: Switzerland had argued against deprecation earlier, but could live with deprecation for a short period of time. Another option would be to give the existing 6656 characters new names in their new positions. He also expressed the possibility that ITTF can take a position that 'dates of effectiveness' worded in pDAM-s will not be acceptable per ISO procedures. 3. Mr. Zhang Zhoucai: China has the concern that if deprecation is chosen, for the duration in which these 6656 code positions will be locked, no other characters can be assigned to them. They have large groups of characters to be encoded in the BMP and they will not be able to use these positions right away. 4. Dr. Asmus Freytag: Unicode consortium will be concerned with the duplicate coding. A limited period of deprecation to assist with migration will be acceptable. The overriding concern is not to allow continuation of processing using the current encoding. 5. Mr. Takayuki Sato He would like to see a clear schedule for the deprecation period. An ad hoc group of delegates drafted revised wording for the resolution. This text was refined with some discussion on how much time would be required for migration period, and when the vacated code positions will be freed up for new assignments etc. The final text was balloted on (see M27.13 - after renumbering - below). Relevant Resolutions: M27.11 (Hangul): UK Abstains With reference to N1158, WG 2 resolves to accept Korean request to add 4516 additional Hangul syllables into ISO/IEC 10646. M27.12 (Hangul): China and UK Abstain With reference to N1158, WG 2 further resolves to encode these 4516 Hangul syllables in the BMP. M27.13 (Hangul): Canada and China NO; Sweden, Singapore; Norway, UK and Egypt ABSTAIN; US, France, Denmark, Korea, Ireland, Israel, Switzerland, and Japan YES With reference to N1158, WG 2 resolves to encode in a contiguous space 11172 Hangul characters containing 4516 Hangul syllables of M27.12 above as well as the 6656 Hangul syllables to complete the repertoire in the code positions from AC00 to D7A3. WG 2 further resolves to remove the existing 6658 Hangul syllables from 3400 to 4DFF effective April 1998. These vacated codes become available for future standardization after that time. M27.14 (Hangul): Canada NO; China, Egypt, Norway, Sweden, and UK Abstain All others Yes WG 2 instructs its editor to prepare a pDAM-5 based on the working draft in N1198 and forward it to SC 2 for further processing along with the background document N1199 (under preparation). 6.4.2 Mongolian Input Documents: N 1184 Proposal for encoding Mongolian script on BMP of ISO/IEC 10646; China; 1995.03.28 N 1192 Proposal Summary Form on Mongolian, China; 1995-03-28 Presentation: Mr. Y.G. Mao presented. Mongolian, Xibe and Todo are integrated in the proposal. About 160 symbols are requested after unification of these. Without the unification we need about 420 coding positions. Unification has been done. N 1192 has the Proposal Summary Form. The fonts should be supplied by China member body. Discussion: 1. Mr. Takayuki Sato: it looks like there are Initial, Middle and Final forms in the current proposal. Some justification is requested as to why separate forms should be encoded rather than a single form. If they are not presentation form the names should be changed to indicate that. China will revise the document based on this comment from Japan. 2. Dr. V.S. Umamaheswaran: A clarification question was asked - how do you distinguish between strings of the three Mongolian, Xibe and Todo if they all appear in the same plain text? 3. Mr. Mao: Currently there is no requirement to do it - if there is, it will be using Font Switching or using Language Switching. 4. Michael Everson: He has reviewed the Chinese proposal and is interested in working with China. China was referred to N 968 of January 1994, a contribution from Mongolia. 5. There is a contribution to WG 3 on Mongolian also. 6. China has written letters to try and contact someone in Mongolia. So far they have not had any response. 7. Dr. Asmus Freytag: Unicode Consortium is also considering the topic. 8. Unicode consortium is requested to feedback to China and Ireland their comments / proposal on The next Unicode consortium meeting is in June 1995. China would like to get the proposal finalized and accepted by June meeting. Action item: Mongolia, Ireland and Unicode consortium should be added as Interested Parties and should be consulted. Relevant Resolution: RESOLUTION M27.22 (cooperation on Mongolian and Tibetan): Unanimous WG 2 encourages China to cooperate with Mongolia, U.K., Ireland, the Unicode Consortium, and other Mongolian experts to arrive at an agreed-upon final proposal for the Mongolian script in ISO/IEC 10646. WG 2 further encourages China to cooperate with Bhutan, Sikkim, India, U.K., Ireland, the Unicode Consortium, and other Tibetan experts to arrive at an agreed-upon final proposal for the Tibetan script in ISO/IEC 10646. 6.4.3 Tibetan Input Documents: N 1095 Proposal for encoding Tibetan script on BMP; China, Nima Zhaxi; 1994-09 N 1159 New consolidated Tibetan Proposal; BSI and Unicode Consortium; 1995-03-10 N 1185 Proposal for encoding Tibetan script on BMP of ISO/IEC 10646; China; 1995-03-xx (Replaces N 1095) N 1191 Proposal Summary Form on Tibetan, China; 1995-03-28 Presentations: Professor Nyima Trashi - presented the Chinese contribution N 1185. N 1191 contains the proposal summary form. N1095 was submitted in San Francisco. Further discussions within China among experts resulted in several changes. Discussions are being held with Messrs. Michael Everson and McGregor Ross. Contributions from Unicode consortium is also considered. Mr. McGregor Ross presented the BSI, Unicode consortium contribution N 1159. Mr. Peter Lofting, under contract with Unicode consortium, has done the background research work. The output of his work would be in the form of a technical report to the consortium. The code table and names of characters are included in the paper with permission of Unicode consortium. N 808 (1992, UK) and N 1095 (China, 1994) were the reference documents. Tibetan script is one of the most complex scripts that we have -- if we can get Tibetan script into 10646 in a sensible way all other scripts will be easier. N 1072 contains the coding conventions used. There are 11 conventions out of which 9 are listed on page 2 of the paper. There are close relationships between other Indic scripts and Tibetan, with some differences also. There is close harmony between N 1095 and UK work. N 1159 is a superset of N 808, N 1095 and a few additional characters. The proposal can be used with either Level 2 or Level 3. Level 3 allows for alternative spellings - however, it leads to ambiguities in interchange. In Level 2 some of the characters may have to be restricted. All other Indic scripts fit in Half a Row. Tibetan will require a full row. The characters are grouped together in a convenient way for the user. The arrangement and grouping of characters differ from the China proposal. Some open issues are identified in item 10, but are detailed in the report to Unicode consortium. Hopefully the Technical Report will be made available to WG 2 at the earliest. A dialog between UK, Unicode experts, China experts - hopefully will bring a common agreement. Discussion: 1. Mr. Y.G. Mao: China - thanks UK for their work. There are lots of commonality between the Chinese and BSI/Unicode proposals. However, there are some differences to be ironed out. There seems to be some discussion in Unicode consortium on some of these characters. China would like to be kept in the loop for the discussions. 2. Dr. Asmus Freytag: Unicode is a little bit behind schedule on its finalization of the draft tables. The consortium can circulate the document for comments etc. to China if they prefer. 3. Mr. Zhang Zhoucai: Chinese experts are willing to attend the Unicode meeting. We would still like have some information interchange prior to the meeting. 4. Dr. V.S. Umamaheswaran: What about Sikkim, Bhutan, India etc.? 5. Mr. Ross: Mr. Lofting has worked with Bhutan. He is in close touch with people in India. 6. Mr. Mike Ksar: the request is to ensure that China, Unicode or Mr. Ross - close the loop with other countries like Sikkim, Bhutan and India. 7. Mr. Takayuki K. Sato: Request updating of N 1192 - to reflect that item 5 - shows that there is more work to be done. 8. Mr. Michael Everson: Glad to see the progress of work in Tibetan. The item on transcription of Sanskrit from Indic script to Tibetan script is of interest. Ireland would like to be kept in the list of interested parties also. 9. Mr. Mike Ksar: thanked China, UK, and Unicode consortium for the work done so far. Hopefully a final, agreed upon proposal be made at the Helsinki meeting. Relevant Resolution: See resolution M27.25 in section 6.4.2 above. 7. Defect Reports 7.1 Review status of editorial defect reports Input Documents: N 1125 Revision of character naming guidelines, annex K; J. Friemelt and S. Fuchs, personal contribution; 1994-10 N 1128 Response to Defect Reports on 10646, subject: Ligature _; Bruce Paterson; 1994-11-10 N 1141 Clarify character shape of 03DE (GREEK LETTER KOPPA); Japan national body, Takayuki K. Sato; 1995-01-11 N 1163 Proposal Summary for WG 2 N 1106 (Defect Report, missing Latin character; Ireland; 1994-10-11); Michael Everson, Ireland, national position; 1995-03-10 Note: The above input documents do not seem to have been addressed by the ad hoc on defect reports during this meeting. They are carried forward for the next meeting. The ad hoc group on defect reports considered several input documents and prepared their dispositions in N 1193 and N 1194 for consideration by the meeting. Only new defect reports since San Francisco meeting were addressed by the ad hoc group. 7.1.1 N1193 - Disposition of Editorial Defects Input Documents: N 1142 Proposed correction on 10646 (Defect Report - Editorial); Japan national body, Takayuki K. Sato; 1995-01- 11 N 1188 Defect Report; Clarification - Separate the basic and extended Arabic blocks; Alaa Ghoneim, Egypt; 1995-04-03 N 1189 Defect Report; Error in Glyph in Table 116 - Location x'FCFA'; Alaa Ghoneim, Egypt; 1995-04-03 Output Document: N 1193 Disposition of Editorial Defect Reports and Instructions to the Editors of ISO/IEC 10646-1, Geneva, April 3-7, 1995; J. Bettels, M. Everson, T.K. Sato, J. van Wingen, A. Winkler; April 6. 1995 Presentation: Mr. Arnold Winkler presented the dispositions in N 1193. The document addressed defect reports in N 1142, N 1188 and N 1189. a) Defect items N 1142-1, N1142-2, N 1142-3 - editorial clarifications / corrections from Japan are all accepted. b) Defect items N 1188-1, through N1188-6: presenting the Arabic character blocks differently in the standard - are proposed to be accepted as editorial defects, with recommended dispositions. Discussion: i) The shapes of characters etc. are acceptable. In general the block names of Arabic characters should not be changed nor the range of code positions within each block. Tunisia had a negative ballot and their objections were not accepted at that time. The impacted code point ranges are not used. ii) Mr. Michel Suignard: This should not be considered as editorial change. Change in the range of code points in a block of positions. iii) Mr. Mike Ksar: Another option is to add another block name. iv) Mr. Alaa Ghoneim: Change requested is COSMETIC with addition of BASIC and EXTENDED shown on the charts. Disposition: All accepted as editorial changes. c) N 1189 -Correcting an Arabic Glyph Image - accepted. Relevant Resolution: See resolution M27.7 item b, in section 7.1.3 later. 7.1.2 N1194 - Disposition of Non-Editorial Defects Input Documents: N 1105 Defect Report - Character names in Latin Extended-B; Ireland; 1994-10-11 N 1162 Input document to WG 2 N 1105 (Defect Report - Character names in Latin Extended-B; Ireland; 1994-10-11); Michael Everson, Ireland national position; 1995-03-10 N 1166 Proposal Summary for HWAIR and WYNN; Michael Everson, Ireland, national position; 1995-03-10 Output Document: N 1194 Disposition of Non-Editorial Defect Reports for ISO/IEC 10646-1, Geneva, April 3-7, 1995; J. Bettels, M. Everson, T.K. Sato, J. van Wingen, A. Winkler; April 6. 1995 Presentation: Mr. Arnold Winkler presented the document N 1194. It addressed the defect reports in N 1162, N 1164 and N 1166. Each of the items in this list had problems reaching consensus within the ad hoc. a) N 1162 and N 1105: There is no such thing as LATIN LETTER OI. The recommendation is to place explanatory text into the informative annex. In the draft resolution associated with this item, the following choice of words were offered for selection by the meeting before voting on the resolution: 01A2 LATIN CAPITAL LETTER OI (gha) or 01A2 LATIN CAPITAL LETTER OI*, with corresponding entry in the new informative annex. The first option was favoured by the majority of the delegates and was selected for the text of the resolution (see resolution M27.7 item c, in section 7.1.3 later). b) N 1164 (was acknowledged in N 1130) is to place the proposed names in the informative annex. c) N 1166-1 is for new characters. d) N 1166-2 will be necessary to change the names in case N 1166-1 is accepted. A lead into the informative annex to indicate that 'the names in this standard - should not be used to derive the properties or meanings or semantics etc.'. A caution to the users of the names in the standard should be set. The names of characters in 10646 are arbitrary strings of characters. Discussion: i) Mr. Michael Everson there seems to be inconsistency in making rulings about when to change the standard and when not to change the standard. ii) Dr. Asmus Freytag: The standard is full of historical errors and accidents. The informative annex proposed in earlier discussion should be used to take care of these things. iii) Mr. Hugh McGregor Ross: several of the names of characters in the standard were assembled by Mr. Ross. At the final editing stage Mr. Hekimi and Mr. Hasegawa got together and a set of names were put together. One has to accept the fact these names are not necessarily logically thought out. With the only exception of the single case of AE, WG 2 must not entertain any changes in names. iv) Mr. Mike Ksar: One should not open up the Pandora's box of changing names because of one's preference. The guiding principle must be not to change the names. v) Mr. Alaa Ghoneim: He fully supports the position - alternative names can be supported in the proposed informative annex. vi) Mr. Johan van Wingen: The concept, the naming conventions etc. were all started in WG 3. The list of names from WG 3 standards were copied from that work. No changes to names should be allowed to those in 10367 within in WG 3. If one character change is allowed (ligature to letter AE) then it has opened up the door already. vii) Mr. J_rgen Bettels: This group has to arrive at an agreement on whether 'all the names within the standard are to be considered an identifier' or not. viii) Mr. Michael Everson: Annex K permits annotations. Is it consistent to have something in parenthesis or all must be in an Annex? Does that make or break the names? ix) Mr. Mike Ksar: If the parenthetical annotation is too long, it may be relegated to annex. x) Dr. Asmus Freytag: The goal is not to clutter the Long Names. The name list creation is to create a list of identifiers. xi) Mr. Johan van Wingen: Preference is not to change at all. Even if one change takes place we cannot control. xii) Mr. Sven Thygesen: Even if we decide NOT TO CHANGE any characters, requests for changes will be always made to WG 2. xiii) Mr. Michael Everson: Current 10646 has clauses in the standard that refers to the names used in the standard. The Canadian contribution N 1171 lists the various clauses where the names are referenced in the standard. Disposition: N 1194 - items 1 and 2 are accepted as editorial; items 3 and 4 are for decision at Helsinki. Relevant Resolution: See resolution M27.7 item c, in section 7.1.3 later. 7.1.3 N 1131 - 10646 Editorial Corrigenda - Cumulative List Input Documents: N 1086 Updated Defect Report (Updated 1031R); Arnold Winkler et al, WG 2 ad hoc; 1994-10-10 N 1131 10646 Editorial Corrigenda - Cumulative List; Bruce Paterson; 1994-12-18 Presentation: Mr. Bruce Paterson presented the document N 1131. Contents of N 1086 is folded into N 1131. A consolidation of all the editorial changes along with proposed text is presented for review. The document was circulated in January mailing. This meeting will be time for confirmation. Each document number with the defect report and the disposition of the defect report are identified. Wherever there is a discrepancy between the defect report and their resolution it has been marked with ASTERISKS along with the member body name requesting the change. This document is intended to be the standing document towards the next edition of the standard. It is suggested that this list be consulted prior to any new defect reports etc. are presented. The document is available in diskette form from Bruce Paterson. All comments are to be brought to the attention of Mr. Paterson. Disposition: The document N 1131 be accepted as the STANDING DOCUMENT to be used in conjunction with current 10646 standard. Relevant Resolutions: (The following resolution addresses several new and old defect reports): RESOLUTION M27.7 (defect report disposition): Unanimous WG 2 instructs its editor to prepare editorial corrigenda on the following items: a. With reference to concerns expressed in N1044: FFE3 FULL WIDTH MACRON* with a corresponding entry in the Annex on Additional Information on Characters. b. Follow the instructions to the editor contained in N1193. c. With reference to concerns expressed in N1162, add the parenthetical annotations as below: 01A2 LATIN CAPITAL LETTER OI (gha) 01A3 LATIN SMALL LETTER OI (gha) d. With reference to N1129 on APL characters: 234A APL FUNCTION SYMBOL DOWN TACK UNDERBAR* 234E APL FUNCTION SYMBOL DOWN TACK JOT* 2351 APL FUNCTION SYMBOL UP TACK OVERBAR* 2355 APL FUNCTION SYMBOL UP TACK JOT* 2361 APL FUNCTION SYMBOL UP TACK DIAERESIS* The parenthetical notations such as (name inconsistent with 22A5 UP TACK) proposed for 234A in N1129 are to be replaced with equivalent entries in the Annex on Additional Information on Characters for each of the above. e. With reference to N1112, add a note in Annex K on naming conventions to recognize exceptions such as when the digit 9 has been used in non-ideographic character names with examples of current usage. The editor is instructed to add the corrigenda related to items a through e above, to N1131. WG 2 further instructs its editor to finalize the contents of N1131 as a collection of editorial changes and forward it to SC 2 secretariat for further processing by ITTF as editorial corrigenda to ISO/IEC 10646-1: 1993 (E) (after completion of the annex mentioned under resolution M27.5 above). 7.1.4 N 1137: Principles for Handling Defects on Character Names Input Document: N 1137 Handling of Defect Reports on Character Names; Ad hoc group on Principles and Procedures - Messrs. V.S. Umamaheswaran, Sven Thygesen, Peter Edberg, Sten G. Lindberg; 1995-01-27 Action item: Use of the new informative annex on additional information on characters should be reflected in N 1137. For example: Item a in N 1137. 7.2 Review status of non-editorial defect reports Input Documents: N 1087 Suggested additions to repertoire of APL; SC 22/WG 3; 1994-10-07 N 1111 Defect Report - 4 reports , rename some Cyrillic characters table 11 - row 4; Ireland; 1994-10-11 N 1112 Defect report, rename general punctuation characters;; Ireland; 1994-10-11 N 1114 Summary of technical defect reports; Arnold Winkler et al, ad hoc editing group;1994-10-12 N 1129 Editorial Improvements to Character Names of APL Functional Symbols; Bruce Paterson; 1994-11-24 N 1130 Draft DEFECT REPORT on names of LIGATURE characters; Bruce Paterson; 1994-11-24 N 1164 Comment on WG N 1130, Draft Defect Report on names of ligature characters, Michael Everson, Ireland, expert contribution; 1995-03-10 Presentation: Mr. Arnold Winkler presented: N 1114 - Several of the defect reports in N 1114 are requests for new characters. a) N 1044 - Full Width OVERLINE - Proposal Summary Form has been submitted by Japan. See item 6.1.1 above. b) N 1045 - ISO 2047 symbols - See item 6.1.2 above. c) N 1079R - Hebrew cantillation marks - see item 6.1.8 above i) N 1087-2 - Editor will provide parenthesized names. Refer to N 1129 for proposal from co-editor. a) N 1129 recommends changes to five other APL characters instead of changing names as proposed in N 1087. b) Dr. Asmus Freytag: 10646 should make use of 'notes' to point to 'what the current name is' versus 'what other usage may want it to be called' etc. Explanatory notes can be collected in a separate informative annex to accommodate various problems that are encountered as the standard gets wider usage. d) A reference to the Annex will be contained in the code tables, and the annex will be sorted on the basis of the code positions. The N 1087 items will be accommodated by this approach. e) N1087-3 See under 9.4.2 below. APL group has not yet submitted the proposal summary form. f) N1105 - refer to N 1162 under 7.12 above. g) N 1106 --- N 1163 under 7.1(this document was not addressed at this meeting - should have been addressed a new character submission, instead of a defect report). h) N 1109 - see AE dCOR resolution under item 5.5 above. i) N1111-P1 - rejected j) N1111-P2 - Deletion of unnecessary parenthesized name qualifiers from' 0402, 0407, 040B ...' A draft resolution was prepared as part of the editorial instructions. However, the convener pointed out that such a removal can cause problems with Slovenia - if they are not consulted ahead of time. The resolution was rescinded. Action item: Convener to check with Slovenia prior to taking action on this defect report. k) N 1111-P3 ; N 1130 was prepared by the editor in response to Washington meeting on names with Ligatures excluding AE, and N 1164 (Ireland) i) Dr. Asmus Freytag: 'Thou shalt not change the Normative Parts of the names' should be up held. Even if they are historically wrong - they should be kept unchanged. The informative annex should be used instead to highlight the anomalies or changes etc. This is to protect already existing implementations who have used these as fixed tokens (long identifiers). ii) Mr. Johan van Wingen: Can we apply this to AE also? iii) Mr. Mike Ksar: Cannot do this on AE - dCOR. iv) The proposal of Annex as a solution is not considered a satisfactory solution for the list in this item. Action item: Ireland, Netherlands and editor - to get together and resolve a satisfactory solution to dealing with this defect report. l) N 1111-P4 - Editorial - See the item for N 1111-P2 above. Cannot be done till the convener checks with Slovenia. m) N 1112 - '9' instead of 'NINE' in names: Can a modification to annex K to recognize exceptions satisfy the defect report, instead of changing the names? A new Annex with explanatory notes can be an alternative. Even though the recommendation by ad hoc in San Francisco is to accept the 'name changes' for Four code positions, alternative method should be avoided. Dr. Asmus Freytag: The names in current list are being parsed by software and should not be changed as much as possible. Disposition: Editor should add a note to Annex on naming conventions to recognize exceptions where digit such as '9' have been used, with the four code positions as example. Relevant Resolution: See resolution M27.7 items d and e, in section 7.1.3 earlier. 8. IRG and Related Items 8.1 Report from WG 2/IRG meeting in Taiwan Input Documents: N 1175 Meeting report of IRG 4th meeting in Taipei; Akio Kido, Rapporteur of IRG; 1995-03-22 N 1176 Nomination of the next Rapporteur of IRG; IRG; 1995-03- 22 N 1177 IRG work schedule; IRG; 1995-03-22 N 1178 Proposal summary form for category A repertoire of CJKV Unified Ideographs; IRG; 1995-03-22 N 1179 Proposal summary form for category B2 repertoire of CJKV Unified Ideographs; IRG; 1995-03-22 N 1180 Proposal summary information of IRG Horizontal/Internal supplementation work; IRG; 1995-03-22 N 1181 Volunteer offering for preparation of final text of CJKV Unified Ideographs part of ISO/IEC 10646-1 second edition; IRG; 1995-03-22 N 1183 Discussion on Ideographic components and composition; Zhang Zhoucai; 1995-03-14 Presentation: Mr. Akio Kido, the outgoing IRG Rapporteur, presented the report in N 1175. There are 6 items requesting resolutions from WG 2. (Please refer to N 1175 for all the details). a) IRG has nominated Mr. Zhang Zhoucai to be the next Rapporteur. Mr. Zhoucai has been one of the major contributors for the unification of Han - was an editor of the unified Han part of 10646. Mr. Zhoucai's nomination was accepted by WG 2 unanimously. The term of office is usually from plenary to plenary. IRG meets next in August. SC 2 plenary is in June 1995. Akio will transfer his role to Mr. Zhoucai effective this meeting. b) IRG work schedule:: The work has been delayed by about 6 months. The revised schedule is in N 1177. The proposal is to submit Horizontal/Internal supplementation proposal, and the first draft of Vertical extensions to WG 2-28; and the second draft of vertical extension by WG 2-29. There will be one more IRG meeting scheduled for August 1995 in Seoul. WG 2 accepted the schedule and approves its next meeting in August -- 21--25, 1995, in Seoul. c) N 1178, N 1179 and N 1180 - are proposal summary forms for different CJKV Unified ideographs. About 10000 Category A (1178), 25000 Category B2 (N 1179) and Horizontal supplementation are indicated in N 1180. The proposal summary forms are PRELIMINARY. Additional information will be supplied by IRG. These are not to be entertained at this meeting. The information will be updated to be more specific, with a consensus on the specific repertoire of the ideographs. A suggestion for code position allocations, if there are any specific requirements for having in the BMP etc., will be identified. Some prioritization effort has to be done. d) N 1181 contains a volunteering statement to assist with the preparation of next edition of 10646-1. China is willingly to do the work. The volunteer offer was welcomed by WG 2, to assist the Editor of 10646 in preparing the next edition of the standard. However, at this time this recommendation will not be forwarded to SC 2. The national bodies should take the responsibility for verifying the final code tables. IRG should work with WG 2 editors and not with ITTF. i) Mr. Takayuki Sato: WG 2 has to give some instructions to IRG to let IRG meet its aggressive schedule. ii) Mr. Zhang Zhoucai, China, requested some directions from WG 2 to IRG, with reference to N 1178, to place priority on the collection of 10000+ Han characters for encoding. Relevant Resolutions: M27.15 (on IRG items): by Acclamation WG 2 accepts the IRG nomination of Mr. Zhang Zhoucai as the next Rapporteur of IRG, and wishes him all success. M27.16 (on IRG items): by Acclamation WG 2 resolves to thank Mr. Akio Kido for his excellent work as Rapporteur of IRG. M27.17 (on IRG items): Unanimous WG 2 instructs IRG to classify IRG's category A vertical extension repertoire N1178 into several priority groups for WG 2's consideration for inclusion or non-inclusion into the BMP. M27.18 (on IRG items): Unanimous WG 2 approves IRG's development schedule for its extension repertoire proposal with the following instructions. 1. Put the highest priority on completion of its vertical extension proposal to be included in the BMP (Refer to N1178, N1179) 2. Singapore's ideographic extension input should be taken into account for the IRG's extension proposal for the second edition of ISO/IEC 10646. The Singapore requirements should be input to IRG, by the end of April 1995. 3. Freeze source repertoires for consideration of IRG's extension proposal for the second edition of ISO/IEC 10646 after due consideration of Singapore's input. M27.19 (on IRG items): Unanimous WG 2 approves that the IRG continues its activity, and instructs the WG 2 convener to ask SC 2 for confirmation of the continuation of IRG activities. M27.20 (on IRG items): Unanimous WG 2 approves that the IRG to holds its fifth meeting in Korea in from 21-25 August 1995. 8.2 CJK Related Items 8.2.1 Discussion on IRG work The following discussion was based on the proposal summary forms described by Mr. Akio Kido as part of the IRG meeting report under item 8.1 above. 1. Mr. Takayuki Sato: As per WG 2 direction to IRG, the collection of repertoire of new Han characters is finished. This list should be frozen. The members of IRG have a tendency to bring additional requirements at each meeting. IRG should instruct its members to 'freeze the list of characters for inclusion in the 2nd edition'. The source code list may be open. However, in order to meet its schedule IRG should fix the repertoire to be included in the next edition of 10646, giving due consideration. 2. Mr. Teow-Hin Ngair: Singapore, as a new IRG member, have some requirements. If these are to be included in the planned submission to the next WG 2 meeting - it has to be done in an ad hoc manner prior to the Helsinki WG 2 meeting, since IRG will not be meeting prior to August. 3. Convener: If there are any requirements from Singapore, the currently frozen IRG repertoire should be opened up to include these requirements. Singapore is requested to contact Mr. Mao, the chief editor for IRG, and let their requirements known. The deadline for submitting machine readable information is May 25th. Action item: Before end of April, Singapore and IRG Rapporteur will work together and ensure that any of Singapore's requirements are accommodated 8.2.2 N1183 Ideographic Components and Composition Input Document: N 1183 Discussion on Ideographic components and composition; Zhang Zhoucai; 1995-03-14 Action item: WG 2 members should take note of N 1183 requesting participation on the discussion on composition scheme. 9. Liaison reports 9.1 Unicode Consortium Input Document: N 1197 Liaison report, The Unicode Consortium; The Unicode Consortium; 1995-04-05 Presentation: Dr. Asmus Freytag presented. There were two highlights. 1. The second edition of the Unicode Standard is being prepared. Expected to be published by end of the year. Some discussion as to what should be included took place within the Consortium. Items that are in progress in WG 2 will be marked as 'in proposal' stage. It should not be mis-interpreted as divergence from WG 2 work. 2. 14 and 15 September 1995, Unicode Consortium will be holding a conference in the San Francisco area. Participation is welcome from WG 2 members. Unicode participates in the WG 2 work, and contributors to WG 2 work are requested to contact Unicode consortium also. Discussion: 1. Mr. Mike Everson: The Unicode technical reports are being referenced in some WG 2 contributions. It would help if the reports are circulated to WG 2 also for reference. 2. Dr. V.S. Umamaheswaran: WG 2 documents are being sent to Unicode Consortium, but these do not seem to be surfaced at the UTC meetings. WG 2 liaison to UTC does not seem to be working well. 3. Mr. Mike Ksar: Request to Unicode Consortium is to take a look at the documents from WG 2 and some one in the consortium has to take on the role. Need a volunteer to be WG 2 liaison to Unicode Consortium. So far it has been Mr. Mark Davis. He may not be able to continue in its role. The US member body may be consulted. Action Items: a. N1165 and N 1167 refer to Tech Reports from Unicode. Dr. Asmus Freytag will ensure that these technical reports are made available to WG 2 members including Member bodies. b. Convener to address the concern over the liaison from WG 2 to Unicode consortium and working with the Unicode Consortium, ensure some one is appointed to the role. 9.2 AFII Input Document: N 1161 AFII liaison statement to WG 2 meeting # 27 in Geneva, Switzerland; Alan W. Griffee, AFII President; 1995-03-15 Presentation: The convener presented the highlights: The font collections available have been reported. A CD ROM version is being planned in July time frame. 9.3 SC 18 9.3.1 SC 18/WG 8 No Liaison Report was available at this meeting. 9.3.2 SC 18/WG 9 N 1138 is a request from SC 18/WG9, and is addressed under repertoire item 6.1.6. 9.4 SC 22 9.4.1 SC 22/WG 20 Internationalization Verbal Report: Mr. Arnold Winkler reported. Next meeting is in Paris next month. SC 22 plenary is in September, Annapolis. There is nothing to report from the San Francisco meeting. SC 22 has produced a document called Framework for Internationalization. Several coded character related items are described therein. There are errors in that document. Would it be useful for WG 20 to send their document for review ? No. The WG 2 members participating in SC 22/WG 20 are requested to rectify the errors. 9.4.2 SC 22/WG 3 APL No liaison report at this meeting. Action item: With reference to disposition of N 1087-3 in N 1114, SC 22/WG 3 was to provide a proposal summary form to WG 2. The convener should respond to SC 22/WG 3 (APL) alerting of this requirement from WG 2. 9.5 SC 21 WG 3 No liaison report was available at this meeting. 9.6 ITU/T Input Documents: N 1196 Liaison statement about ITU-T activity on character sets and coding; Stefan Fuchs (ITU-T SG8 Q.17 Rapporteur); April 1995 N 1125 Revision of character naming guidelines, annex K; J. Friemelt and S. Fuchs, personal contribution; 1994-10 Presentation: Mr. Stefan Fuchs presented the liaison report. 1. One of the activities of ITU/T-SG8 is character coding for Telematic services. There are several CCITT recommendations in place. The paper relates these to relevant JTC 1 standards. 2. T.61 (new edition approved two weeks ago). T.51 contains several registered collections. T.53 is mainly based on 6429- 1992 edition, with ITU specific additions (not yet in ISO). 3. Teletex services, though have disappeared in practice, the recommendations do exist. T.61 is being referenced in other standards --such as 'TELETEX STRING' or 'T.61 STRING' of ASN.1. The deletion of T.61 will have to consider such current uses. 4. Two NWI were approved - multiple byte coding for Telematic services - awaiting input from members; based on 10646 and different conversions between existing codes. The second work item is on Character Sorting Requirements for Telematic services. 5. See .N 1196 for a list of ITU-T recommendations corresponding to ISO standards dealing with coded characters. 6. ITU/T SG8 will like to maintain the close cooperation with SC 2 WG 2 and WG 3. N 1125 was prepared at WG 2 meeting 26 in San Francisco. It will be discussed at Helsinki meeting Action item: Mr. Stefan Fuchs was to examine the annex for dealing with names. He was requested to bring a new contribution consolidating the previous proposals, in light of the new proposed annex for additional information on character names etc. 10. Other business 10.1 How to speed up process 10.1.1 ECM/TC1 - WG 2 Joint Standards Development Input Documents: N 1134 E-mail message proposing creation of an ECMA TC committee to process next edition of 10646 using Fast Track; Mike Ksar and J_rgen Bettels; 1995-01-12 N 1169 Canadian position on N 1134 - Proposal for joint ECMA- TC1/WG 2 Progression of next edition of 10646; Standards Council of Canada; 1995-03-09 Presentation: Mr. Mike Ksar explained the proposal in N 1134. Within ECMA, which is also working on coded character set standards, a joint working group is proposed with WG 2 to speed up the process of publishing the next edition of 10646. The proposal was to have a joint technical committee and to have ECMA play a more active role in the creation of the next edition of the standard. The documents produced will be made available to the members of the community. ECMA facilities (like meeting locations), Technical Editing resources, distributing the documents, on-line standards distribution etc. become accessible. Some of the members of ECMA as joint members can contribute more actively. This would mean more meetings to synchronize with ECMA TC The joint meetings call for another meeting in September 95. Mr. Jan van den Beld explained a little bit more about ECMA, its organization and processes. An ECMA memento publication is available - copies were made available to the meeting - with different categories of membership etc. described. ECMA is an international organizations. ECMA is by definition open for all non-profit organizations. Small and big companies can also join. ECMA is itself a non-profit organization. In each TC the individual members have equal rights at the TC level. There is a vote one per person - versus -ISO's one per national member body. TC1 meetings can be easily organized with less procedures. They can be held anywhere in the world. ECMA is involved in several standards arenas. ECMA could provide more resources - for example, new CRC of 10646. At least one small step has been taken in ECMA - ECMA has become a member of AFII, giving it the access to its data base. It makes it possible for them to get the fonts from the ACCESS data base. An example of the resource is the secretarial support. ECMA standards developed could be submitted to FAST Track at JTC 1 level. This procedure can be used as an option. Having an equivalent standard from ECMA, any number of copies, free of copyright, free of charge - is available. They are placed on an FTP with free access. Requests for ECMA standards can be from non ECMA members, individual members etc. and are made available free of charge. A new version of the document will need to be created as an ECMA standard mainly to avoid conflict with 10646 standards from the copyright point of view. The process ECMA follows for developing standards is -- first some technical committee in ECMA agrees to a work item. It goes to the general assembly for approval. Each member company has one vote - each ECMA standard must pass by 2/3 majority at the assembly. The technical committee is responsible for creating such standards. TC1 - exists since 1962. Most of the TC1 members are also members of WG 2. They meet as many times as needed. Fast tracking is never an ECMA's one sided action. 90 percent of the standards have been with intensive interaction with the receiving parties such as SC 2 WG 3, before being fast tracked. Several other JTC 1 SCs have requested ECMA to create standards and fast track them. The references within ECMA standards are to ECMA standards. Fast tracked versions will remove and replace these references. In the area of Corporate Telecommunications - ECMA produces standards and distributes to all member companies and to SC6 etc. There are also simpler procedures. All comments received are aligned with the ISO standards. Discussion: a) Mr. Kolbj_rn Aamb_: If ECMA will publish the standard, will it allow a Loose Leaf format? b) Mr. Jan van den Beld: There are other standards for example Industrial Safety has forms - available in loose leaf form. c) Dr. Asmus Freytag: Glad to know that ECMA is joining AFII. Unicode consortium is linked with WG 2. Unicode Consortium and ECMA could have a formal relationship between them to build up the confidence. Could also have joint ECMA / Unicode joint meetings. Another outlet getting additional resources would be welcome. Initial reaction was not so positive. The place of decision making should be within WG 2. The procedures to follow should be that of JTC 1. d) Mr. Jan van den Beld: ECMA is the only organization having a guideline to cooperate with Consortia. At least 3 members of ECMA should also be members of that consortium. e) Mr. Sven Thygesen: We should have a discussion at the SC 2 plenary. The proposal for a maintenance agency in Denmark's contribution N 1157 is also relevant in this bigger picture. We should take a broader view of the whole question. f) Mr. Ross - UK representative to WG 2 meetings is sponsored (financially supported) by BSI and British Government. Whether such sponsorship will be impacted by the fact that ECMA is an industrial organization is not clear. g) Some of the concerns fed back to the convener are: i) ECMA may end up in producing yet another 10646 standard ii) The procedure of developing a standard in ECMA and then Fast Tracking it in JTC1 is of concern also. Document N 1169 from Canada expresses this concern. It will bypass the CD stage of JTC 1 procedure. ECMA Council meets twice a year - approving work items etc. which is not the same as JTC 1 way of approving work items etc. iii) If ECMA standards are made available free of charge then ISO standards or Unicode publications may be undercut from sales point of view. Mike Ksar assured that they are complementary and are NOT replacements for each other. The original proposal is to have joint meeting with ECMA TC in trying to develop standards jointly between ECMA and WG2. One of the observations was: ECMA TC1 meetings can be held back to back and after the WG 2 meetings so the minutes of TC1 meeting can be based on the WG 2 meeting results. Action item: Mr. Mike Ksar is to prepare a revised proposal for the joint working of ECMA TC1 and WG2 for discussion at the next WG 2 meeting taking into consideration the input received so far and the comments at the meeting. 10.1.2 Danish Proposal for WG 2 Administration Tools Input Documents: N 1116 Principles and Procedures for Allocation of New Characters and Scripts (Revised N 946); Ad hoc group on Principles and Procedures - Messrs. V.S. Umamaheswaran, Sven Thygesen, Peter Edberg, Sten G. Lindberg; 1995-01-27 N 1157 Proposed SC 2/WG 2 administrative procedures and tools to enhance processing of SC 2/WG 2 program of work; Sven Thygesen, DS, Denmark; 1995-03-06 N 1190 Use of E-mail etc. in SC 2/WG 2; Keld Simonsen; 1995- 04-02 Presentation: Mr. Sven Thygesen introduced the document N 1157. This is a DRAFT document containing the basis for administrative tools that are proposed for managing the WG 2 work. It addresses the procedural requirements, tools etc. that can assist WG 2 in speeding up the work within WG 2. The proposal is also to set up a distribution mechanism for administrative and working documents for WG 2 members. Hopefully, this will speed up the review and feedback cycles, potentially making the face to face meetings more productive and to the point. The concept of a maintenance agency has been raised. The work with ECMA makes it a potential candidate for being the maintenance agency. An EXCEL data base, following on from the proposal made in San Francisco, is part of the administrative tools. A DEMO of the HTML WWW set up by Messrs. Keld Simonsen and Sven Thygesen was made. One may have to consider other viewer programs than NETSCAPE. A natural language description of the standard should be added. On the Internet, the access is PUBLIC. There is also COPYRIGHT information. There is an e mail address to answer to questions. What goes into the public data base is under the control of the convener. There will be a link to the Unicode home page. The procedures document N 1116 was also shown. Hyperlinks are set up to different sections of 1116. 1. The WG 2 document register will be there. The convener will have access control on the FTP distribution list. The FTP access will be for all documents made available in electronic form to the convener, and also for discussion on different topics to WG 2 members who have e-mail access. 2. The Excel data base was shown to maintain a running status of the work items. Its access via the Web was also demonstrated. 3. Mr. Mike Ksar: the somewhat rigid process of JTC 1 does exist. The entry of documents should be under the control and review of the convener. There may be a need for Open WEB site in addition to the closed / controlled site. The COST of using the Site should be FREE for all WG 2 members. 4. The WG2 home page will be experimental for sometime to come. The convener requested Danish standards to please ensure that the information is not made PUBLIC as yet. Relevant Resolution: M27.24 (thanks to Denmark): by Acclamation WG2 thanks the Danish delegation for the preparation of a WWW home page for WG2 and the presentation thereof to WG2. WG2 appreciates the Danish offer to set up an E-mail reflector site. N 1190: Mr. Keld Simonsen explained his short paper. An E-mail List has been created for distribution of documents within WG 2. It will be an INFORMAL communication vehicle. The documents can be posted by the convener only. Any document sent to the convener in MS Word format - diskette or using uuencoded format - can be sent to the convener. The font contents and variations are the main stumbling blocks. Bit Maps can be created and sent. Action Item: Convener and Denmark (Keld and Sven) will work together and establish the rules and guidelines related to the world wide web and to the FTP site proposed. 10.2 New business 10.2.1 Normativeness and Translatability of 10646-Names Input Document: N 1171 Normativeness of names from the English version of 10646-1 in non-English versions of the standard; Standards Council of Canada; 1995-03-21 Presentation: Dr. V.S. Umamaheswaran presented the document. The document requests WG 2 for a clear statement regarding the Normativeness of Translation of Names in 10646. Various relevant clauses from 10646 where some form of conformance related to character names or character collection names were also summarized in the document. Canada and France are working on a French translation of 10646 - including translations for the Character Names in 10646. Discussion: 1. Mr. Johan van Wingen: English names in English context, and French names in French context should be OK. 2. Mr. Mike Ksar: We should fix the clauses if the standard is weak in this area - to disallow the translation. 3. Mr. J_rgen Bettels: There are other standards using the long names, and for interoperability they may break. 4. Dr. Asmus Freytag: Simple proposal - List in the standard - all possible names for characters in all languages could be added in annex. 5. Mr. Mike Everson: The problem is hinged on whether the name is a name or an identifier. Considering the naming convention restriction, there seems to be an intention of being 'identifier'. If one wishes to use Long Identifiers the names in the English Names in the standard is used. The concern is based on if there is an application that uses these names. 6. Dr. Umamaheswaran: Reminded the group that there are equivalent naming conventions (similar to Annex K) for French names in SC 2. It has been long standing SC 2 practice to allow translations into the official ISO languages (if there are enough resources to do the translations). Some standards do have French versions and the names between these and the French 10646 have to be maintained just like between the English versions. 7. Mr. Takayuki Sato: Japan in its translation - JIS version equivalent of 10646 - they had a discussion of translation. We should treat them as Long Identifiers - and not translatable names Since it is used for identifiers, they decided not to translate. It is an International Alphabet string. Within the Japanese version they used the existing long strings. 8. Mr. Zhang Zhoucai: China did not translate the NAMES. 9. Korea: They have not done the translation. Their names are based on the ROMANIZATION of Korean characters. There is no intent to change. 10. Mr. Sven Thygesen: Danish version has one cover sheet, with an extract of the standard but covers the contents of the standard. 11. Mr. Kolbj_rn Aamb_: When you use transliteration, ISO transliteration is used. 12. Mr. Johan van Wingen: There is a difference in Romanization and Transliteration. 13. Mr. Michel Suignard: What other countries are doing about translation is not binding on those who want to translate especially in one of the ISO languages. However. considering the fact that these names are used as LONG IDENTIFIERS, an equivalency list may be adequate. 14. Mr. J_rgen Bettels: these are considered as LONG IDENTIFIERS and not NAMES. 15. Mr. Sten Lindberg: Swedish member body - is translating the names for different purposes. 16. Mr. Arnold Winkler: We are digging at the foundation of the standard by talking about short and long identifiers. Why cant we come up with short identifiers for example Uxxxx?. 17. Mr. J_rgen Bettels: In principle, it is a nice idea. The thing that is missing is the alignment of character names across standards. 18. Mr. Arnold Winkler: We make a recommendation - as WG 2 members - to SC 2. Short identifiers previously discussed all had some language characters etc. as part of it. Now that 10646 has been stabilized - Uxxxx etc. are candidates. 19. Mr. Keld Simonsen: Short identifiers have been rejected by SC 2 and is being used by SC 22. 20. Dr. Asmus Freytag: Unicode will be in favour of calling them LONG IDENTIFIERS. Empathize with difference between Short IDs being friendly or not etc. As an option propose U+xxxx etc. as an alternative. 21. Messrs. Everson and Umamaheswaran are to draft resolutions and present to WG 2. Two draft resolutions were presented to the WG 2 meeting. One of them (see M27.21 later) was voted on. The second one, WG 2 members felt that sufficient discussion had not taken place - though the Canadian contribution N 1171 had pointed the items out. The following draft resolution was therefore removed from the final list of resolutions. It was suggested that the subject may be brought up again at the next WG 2 meeting or at the SC 2 level. "In order to address the concerns regarding the normativeness of character names and character collection names within the standard with regard to conformance statements, WG2 instructs its editor to prepare a pDAM-6 with the following amendments: Clause 13.1 'limited subset', paragraph 2, page 8: "A claim of conformance referring to a limited subset shall list the graphic characters in the subset by the names of graphic characters or code positions defined in ISO/IEC 10646." Clause 13.2 'selected subset', paragraph 2, page 8: "A claim of conformance referring to a selected subset shall list the collections chosen using the collection number as defined in Annex A of ISO/IEC 10646." Relevant Resolution: M27.21 (on translatability of unique names): Unanimous In response to the Canadian NB request for clarification (N1171), WG 2 has strong reservations as to whether character names and character collection names may be translated in non-English language versions of IS0/IEC 10646 despite current SC 2 practice. WG 2 informs the Canadian NB that it was not the original intention of WG 2 that unique names in ISO/IEC 10646 be translatable because of their potential use as long identifiers. However, in order to address the concerns expressed regarding the use of these terms as identifiers, the editor is instructed to add the following paragraph to Clause 12 as editorial clarification: "When the unique names in this standard are used as identifiers, the unique names from the English language version of this standard shall be used." 10.2.2 Other Documents Input Documents: N 1165 Names of Ethiopian characters; Michael Everson, Ireland, expert contribution; 1995-03-11 N 1167 Names of Burmese characters; Michael Everson, Ireland, expert contribution; 1995-03-12 N 1172 Proposal for encoding the Cherokee script; Michael Everson, Ireland, expert contribution; 1995-03-14 N 1173 Proposal and draft for New Work Item: PostScript-type aliases to 10646 character names; Michael Everson, Ireland, expert contribution; 1995-03-12 N 1174 Query on the representation of Control Characters; Michael Everson, Ireland, expert contribution; 1995-03-14 The above documents were not discussed at this meeting. They are carried forward for discussion at meeting 28. 10.3 Future meetings Input Documents: N 1136 Logistics information on SC 2 plenary and SC 2/WG 2 & WG 3 meetings in Helsinki; Martti Lahti, Finnish Data Communication Association; 1994-12-02 N 1155 1st draft agenda for 5th Plenary Meeting of JTC 1/SC 2- Helsinki, Finland; SC 2 Secretariat; 1995-02-22 N 1156 Venue for the Plenary Meeting of JTC 1/SC 2 and its WGs - Helsinki, Finland; The Finnish Data Communication Association (FDCA) under the auspices of the Finnish Standards Association - SFS; 1995-02-22 At first it was thought that we may need another meeting between the Helsinki meeting and the Tokyo meeting. The time difference was not sufficient to justify this. Instead, meeting no. 30 at the end of January 1996, in the West Coast area of USA will be arranged. a. WG 2 meeting no. 28: 1995-06-26--28 (Monday to Wednesday, 2 1/2 days) along with SC 2 and WG 3 in Helsinki, Finland. Caution: there is a potential hotel booking problem for the Sunday prior to the start of the meeting. This is being addressed by the member body and SC 2 secretariat. Alternative arrangements are being made and members will be informed as soon as possible. b. WG 2 meeting no. 29: 1995-11-06--10, Tokyo, Japan c. WG 2 meeting no. 30 1996-01-xx-xx (End) in USA d. WG 2 meeting no. 31: Week of 1996-04-xx, in Canada or Denmark Action item: Convener: WG 2 status report to the SC 2 Helsinki plenary is to be prepared. 11. Closing 11.1 Approval of Resolutions Output Document: N1204 Resolutions of WG 2 Meeting 27, Geneva, Switzerland, April 3--7, 1995;1995-04-07 The resolutions drafting committee had prepared a set of 32 resolutions based on the notes taken down by the secretary during the meeting. Of these 32, three draft resolutions and part of one resolution were removed from the final set and were either postponed to be addressed later or were relegated to action items. The final list of approved resolutions are in document N 1204. They are also scattered under the different sections of these minutes marked as 'Relevant Resolutions'. The first draft text for one of the resolutions on the Korean Hangul proposal raised a lot of discussion. See the discussions captured as 'Draft Resolution' in section 6.4.1 above. A reworded resolution was finally adopted. A draft resolution on clarification of 'conformance statements related to names' was also postponed. See under item 10.2.1 above. 11.1.1 Appreciation: The following is a list of resolutions concerning appreciation of different groups and individuals. M27.23 (thanks to ECMA): by Acclamation WG2 thanks ECMA and its staff for hosting the meeting, providing secretarial and administrative support and especially for its outstanding hospitality. M27.25 (thanks to drafting committee): by Acclamation WG2 thanks the drafting committee V.S. Umamaheswaran, Michael Everson, Akio Kido, Mao Yong Gang, Takayuki K. Sato, and Arnold F. Winkler. M27.26 (welcome to new participants): by Acclamation WG2 welcomes the first time participants from China, Korea, Singapore, and the US and appreciates their valuable contributions. M27.27 (thanks to secretary): by Acclamation WG2 thanks V.S. Umamaheswaran for taking the minutes. M27.28 (thanks to defect reports subcommittee): by Acclamation WG2 thanks the members of the defect reports subcommittee (Michael Everson, Takayuki K. Sato, J_rgen Bettels, Johan van Wingen, and Arnold F. Winkler) for preparing the dispositions of defect reports. M27.29 (thanks to Hugh Ross): by Acclamation WG2 extends its appreciation to Hugh Ross for attending the meeting and contributing his extensive experience and knowledge to our efforts. 11.2 Adjournment The meeting was adjourned at 15:45h. 12. Action Items All individuals, member bodies and liaison organizations are requested to take prompt necessary steps to complete the action items identified against them in the following tables to avoid undue delays in WG 2's progression of work. 12.1 Outstanding Items From WG 2 Meeting 25 Antalya, Turkey It Assigned to / action (Reference N 1034 - Status em resolutions, and N 1033 - minutes of Antalya meeting WG 2-25, and corrections to these minutes in Annex A of N 1117) 2. Convener (Mr. Mike Ksar): b. to update document N 957-R containing the WG 2 OUTSTANDING program of work - capturing all the comments received under item 8.3 in this set of minutes. 4. French and the Netherlands member bodies. are invited to prepare a formal defect report OUTSTANDING on Armenian characters (described in document N 1022). Mr. J.W. van Wingen had volunteered to contribute. 5. Japanese member body a. is requested to forward a set of bit maps and OUTSTANDING /or the outline of the corrected shapes reported in document N 1006 and N 1014 along with a blown-up (96x96) hard copy to the editor. Note: Japan needed more information from the project editor regarding fonts See discussion under section 8.1.2 in WG 2-M26 minutes document N 1117. 6. Korean member body is requested to forward the set of bit maps, IN PROGRESS and or the outline of the corrected shapes of the characters in defects in document N 975, along with a blown-up (96x96 bits) hard copy is needed by the editor. 8. Indian member body is invited to prepare a defect report asking OUTSTANDING for the appropriate editorial change regarding references to ISCII 1991 - following the JTC 1 Defect Reporting procedures (and forms). 9. Danish member body (Mr. Keld Simonsen) is encouraged to update the information in OUTSTANDING their contribution (Temporary Document) removing the parts that are not relevant to the Annex under resolution TKS-3 from the WG 2 Washington meeting no. 24. 10 Chinese member body . a. is requested to study this possibility of UNDER STUDY composition to reduce the number of characters of the Yi script in document N 965 that needs coding in the BMP. b. is requested that China and Mongolia get OUTSTANDING together and come up with an agreed upon joint proposal between the two by the next WG 2 meeting c. is requested to coordinate the Tibetan script IN PROGRESS requirements by working with other member bodies such as India and other countries such as Bhutan and Sikkim using the Tibetan language and script. 13 All member bodies . h. is invited to contribute input on sources of OUTSTANDING characters towards developing an informative Japan: N Annex to ISO/IEC 10646-1 for consideration at 1055; Japan: the next SC 2/WG 2 meeting N 1066, 1067, 1068, 1069 Other member bodies are still to contribute. 12.2 Outstanding Items From WG 2 Meeting 26, San Francisco, CA, USA It Assigned to / action Status em 2. All Member Bodies a. to revisit their submissions prior to May 93 IN PROGRESS (when 10646-1993 was used as the starting Several point), and send a filled Proposal Summary Form Forms have for each to the WG 2 convener. been sent in; Others are expected to be submitted. b. to examine all proposals for additions to the OUTSTANDING repertoire (refer to list in document list in N 1078 and in N 1050, and N 1100) and suggest enhancements, corrections etc., if there is any impact on the proposed characters' usage in their user communities. c. to review 1078 along with the noted corrections OUTSTANDING in WG 26 meeting minutes, and send feedback to Mr. Hart for updating the document. Several new contributions received after N 1078 are not included in the document. d. to feedback any specific requirements / OUTSTANDING comments to Japan with reference to document N 1093 on BRAILLE characters proposed by Japan. e. to give feedback to China on their proposal on OUTSTANDING Mongolian in document N 1098. New document N 1184 should be referred to. f. to check the contents of N 1086 with respect to OUTSTANDING the disposition of their editorial defect reports. g. to examine the non-editorial defect reports in OUTSTANDING document N 1114 and take appropriate actions on the suggestions for their dispositions from the ad hoc. h. to provide available information on 'sources of OUTSTANDING fonts' to answer questions received during promotional presentations on the standard, and by the SC 2 secretariat, by implementers of the of the standard. i. All contributors of WG 2 documents are OUTSTANDING encouraged to provide an electronic version of the documents -- preferred format is any one of the formats that is recognized and can be converted by MS Word for Windows. If the documents include any glyphs in RTF format, they are easier for the project editors to use directly. 3. Project Editor / Co-Editor: Mr. Mark Davis / Mr. Bruce Paterson b. With reference to Resolution M26.3, and with OUTSTANDING N1059 as the draft text of an annex to ISO/IEC 10646-1, to provide pDAM text for SC 2 ballot. 6. IRG (Mr. Akio Kido) to take necessary action in IRG with reference OUTSTANDING to resolution M 26.4 regarding 5-column layout of Han block. 8. Ms. Joan Aliprand - Liaison to TC 46 to take parts related to TC 46 in document N IN PROGRESS 1071 for formal submission as liaison document by TC 46 along with the completed Proposal Summary Form. 9. Mr. Alan Griffee - Liaison to SC 18 WG 8 to convey to SC 18 WG 8 that their Math symbols IN PROGRESS proposal be resubmitted along with the completed Proposal Summary Form. The original request was prior to publication of 10646. 11 Mr. Johan W. van Wingen . a. to communicate to SC 22 ALGOL working group, OUTSTANDING characters from document N 1071, towards SC 22 ALGOL preparation of a liaison statement to WG 2 group does along with the completed Proposal Summary Form. not exist any more. A contribution on ALGOL is to be discussed at this meeting. b. is invited to prepare contributions on Railway OUTSTANDING. users that he volunteered to prepare during the meeting. 12 Mr. Michael Everson . a. to advise the SC 2 chair (Mr. Sten G. Lindberg) OUTSTANDING and the SC 2 secretariat, the names and addresses of contacts regarding Armenian encoding standardization effort. 13 Mr. Michael Everson and Canada . With reference to document N 1104 on Canadian IN PROGRESS Aboriginal syllabics, to work with Canadian member body (and CASEC) and get agreement on a common position. 14 Mr. Hugh McGregor Ross and Canada . With reference to document N 1073 on Canadian IN PROGRESS Aboriginal syllabics, to work with Canadian member body (and CASEC) and get agreement on a common position. 12.3 New Items From WG 2 Meeting 27, Geneva, Switzerland Item Assigned to / action (Reference Meeting 27 Resolutions Stat document N 1204 and Unconfirmed Meeting 27 Document N us 1203 - this document you are reading) 1. Meeting Secretary - Dr. V.S. Umamaheswaran a. to finalize the document N 1204 containing the adopted meeting resolutions and send a plain text and MS WORD formatted versions to the convener as soon as possible, for electronic distribution by the convener to the WG 2 membership and to SC 2.. b. to finalize the document N 1203, the unconfirmed meeting minutes as soon as possible and send to the convener for distribution to WG 2 membership. 2. Convener, Mr.Mike Ksar a. to contact TC173/SC4 to get more information on their Braille standard (CD/DIS). b. to address the schedule related questions for the second edition of 10646, and update the program of work of WG 2 accordingly. c. to advise SC 2 of acceptance of IRG nomination of Mr. Zhang Zhoucai as the new IRG rapporteur for the next term of office. d. to advise SC 2 of the confirmation of IRG activities and schedule of work. e. to address the concern over the effectiveness of liaison representation from WG 2 to the Unicode Consortium. f. to advise SC 18/WG 9 on the action taken by WG 2 on their liaison document N 1138. g. with reference to disposition of N 1087-3 in N 1114, SC 22/WG 3 was to provide a proposal summary form to WG 2. The convener should respond to SC 22/WG 3 (APL) alerting of this requirement from WG 2. h. to prepare the WG 2 report for the SC 2 plenary meeting in Helsinki, the week of 26 June 1995. I to prepare a revised proposal for the joint working of ECMA TC1 and WG2 for discussion at the next WG 2 meeting taking into consideration the input received so far and the comments at the meeting. 3. WG2 project editor and co-editor a. to take the necessary actions in accordance with the following resolutions: 1. M27.1 - pDAM 1 on UTF-16 - updating and further processing as a DAM in JTC 1 2. M27.2 - pDAM 2 on UTF-8 - further processing as a DAM in JTC 1. 3. M 27.3 - pDAM 3 on C1 controls - further processing as a DAM in JTC 1 4. M27.4 - pDAM 4 on UTF-1 - registering UTF-1 with ISO-IR; updating and further processing as a DAM in JTC 1. 5. M27.14 - pDAM-5 on Hangul Syllabics - prepare pDAM-5 based on N 1198 and forward to SC 2 for further processing in SC2 along with N 1199 (to be prepared by Korean member body). b. per resolution M 27.5, to draft the text of a new informative annex 'Additional Information on Characters' for review at meeting 28, end of June 95. This annex will have initial entries for various characters indexed by the code positions, that are needed for various other resolutions from meeting 27, that have explanatory information for different characters. See also minute item 7.1.2-d on a cautionary note to the users of the names in the standard. c. per resolution M 27.6, to update the names of the different characters in dCOR-1 on _, and to re-order the list of names in Annex E appropriately. d. per resolution M27.7 - defect report dispositions, to prepare editorial corrigenda text and add to the collection in N 1131; getting it ready for forwarding to ITTF as editorial corrigenda, along with the informative annex per resolution M 27.5. e. per resolution M27.8, add the DONG SIGN at code position 20AB in the BMP, for the second edition of the standard. A standing document of all such accepted characters, their names and code positions should be started to be able to prepare the text of the second edition (schedule to be decided by WG 2). f. per resolution M27.21, to prepare editorial corrigendum text regarding use of 10646 names as identifiers. 4. Ad hoc group on Principles and Procedures (Mr. Sven Thygesen - lead) a. to update the principles and procedures document N 1116 and the proposal summary form N 1116F and create the revised document N 1202 reflecting all the suggestions for improvements made during the meeting - - see minutes item 6.1.1.1, 6.1.5.1, 6.2 and discussions under item 10.1.2. b. to update N 1078R with any new scripts that have been submitted for consideration after the last update of N 1078. The updated document may be issued as a new document and reflected in the database being set up for administrative tracking purposes. 5. IRG Rapporteur and IRG a. to consider Vietnam's request for CHU NOM script in N 1127 in its work on Vertical Extension. b. to review the TCA contribution N 1182 and give their evaluation to WG 2 for consideration at the next WG 2 meeting c. to classify IRG's category A vertical extension repertoire N1178 into several priority groups for WG 2's consideration for inclusion or non-inclusion into the BMP d. to take into account of Singapore's ideographic extension input for the IRG's extension proposal for the second edition of ISO/IEC 10646. e. to freeze source repertoires for consideration of IRG's extension proposal for the second edition of ISO/IEC 10646 after due consideration of Singapore's input. 6. Vietnamese Member Body, Mr. Michael Everson and Mr. Bruce Paterson to work with the co-editor Mr. Bruce Paterson to answer the various questions that were raised during the meeting on the proposal for Cham script The questions and comments are being assembled by Mr. Everson, Ireland, on behalf of WG 2 and will be forwarded to the Vietnamese member body. 7. Korean Bureau of Standards to prepare N 1999 - supportive background document for pDAM-5 (N 1998) on Hangul, addressing all the concerns raised during the discussions at the meeting 27 in Geneva and forward it to the convener as soon as possible. This document will be forwarded along with pDAM-5 text prepared by the editor as information accompanying the SC 2 ballot. 8. Chinese member body a. is encouraged to cooperate with Mongolia, U.K., Ireland, the Unicode Consortium, and other Mongolian experts to arrive at an agreed-upon final proposal for the Mongolian script - see resolution M27.22 b. is encouraged to cooperate with Bhutan, Sikkim, India, U.K., Ireland, the Unicode Consortium, and other Tibetan experts to arrive at an agreed-upon final proposal for the Tibetan script - see resolution M27.22.. 9. Singapore member body is invited to input their ideographic character requirements to IRG, by the end of April 1995. 10. Unicode Consortium, Dr. Asmus Freytag a. to get Unicode Consortium feedback on N 1143 - on Latin characters for Yoruba and Hausa - to Mr. Hugh Ross, to enable WG 2 to decide at its next meeting.. b. to ensure that appropriate Unicode technical reports are distributed to WG 2 11. Mr. Michael Everson, Ireland a. to compile the questions and concerns on Cham script in cooperation with Mr. Bruce Paterson, the co-editor, and forward to the Vietnamese member body for their response by the next WG 2 meeting. b. to revise the proposal for additional Irish Gaelic characters in N 1058 and N 1132 12. Mr. Johan van WIngen, Netherlands is invited to examine the standard for the need for any statements regarding conventions used for naming characters such as 'digits', 'letters', etc. and propose clarification texts -- see minutes item 6.1.2.2. 13. Mr. Hugh Ross, UK a. to get supportive requirements statements on his proposal for Yoruba and Hausa from the appropriate governments in Africa. b. to get the needed confirmation regarding Arabic Letter TEHEH with bar for Urdu (proposed in N 1144). 14. Mr. Alaa Ghoneim, Egypt to assist Mr. Hugh Ross in preparing the appropriate explanatory texts for the Farsi quotation marks, GAAF and BBEH in Mr. Ross's proposal in N 1144. 15. Mr. Stefan Fuchs, Israel a. to provide additional clarification on N1195 - proposal for Hebrew cantillation for consideration at the next WG 2 meeting. b. to bring a new contribution consolidating the previous proposals on conventions used for names in 10646, in light of the new proposed annex for additional information on character names etc. c. to inform ECMA TC1 that ECMA TC1 meetings may be held back to back and after the WG 2 meetings so the minutes of TC1 meeting can be based on the WG 2 meeting results. d. to work with Danish Standards and establish the rules and guidelines related to the world wide web on WG 2 and the proposed FTP site for distribution of WG 2 documents. 16. All member bodies, liaisons and individual experts a. are encouraged to take note of N 1183 from China on and participate in the discussion on ideographic components and composition. b. are encouraged to submit an electronic copy of their input in a format that can be read by MS WORD for WINDOWS to the convener, for placing electronic distribution to WG 2 via the FTP site being set up for WG 2 use by the Danish Standards Institute. c. Meeting Secretary - V.S. Umamaheswaran d. to finalize the document N 1204 containing the adopted resolutions and send to the convener for distribution to WG 2 membership - in plain text format and in MS WORD format.. e. to finalize the document N 1203 containing the unconfirmed meeting minutes and send to the convener for distribution to WG 2. 17. All WG2 experts and Liaison Representatives in attendance at Meeting 27 a. are once again requested to encourage their member bodies to cast their ballots in time b. are requested to encourage their delegates to the next SC 2 plenary in June 1995, to be prepared for taking national positions at the meeting. c. are requested to encourage their member bodies to support the different Amendments to ISO/IEC 10646-1: 1993 at the JTC 1 level balloting in their national committees d. to reflect the use of the new annex on additional information characters in document N 1137 - handling of defect reports on character names. -- END OF UNCONFIRMED MINUTES OF MEETING 27 OF ISO/IEC JTC 1/SC 2/WG 2 --