From isaak@ljo.dec.com Tue May 30 13:06:45 1995 Received: from inet-gw-2.pa.dec.com by dkuug.dk with SMTP id AA03911 (5.65c8/IDA-1.4.4j for ); Tue, 30 May 1995 23:10:49 +0200 Received: from vanna.ljo.dec.com by inet-gw-2.pa.dec.com (5.65/24Feb95) id AA02402; Tue, 30 May 95 14:06:47 -0700 Received: from csac by vanna.ljo.dec.com; (5.65/1.1.8.2/10Oct94-8.2MPM) id AA10736; Tue, 30 May 1995 16:55:33 -0400 Received: by csac.ljo.dec.com; id AA21940; Tue, 30 May 1995 17:06:45 -0400 Date: Tue, 30 May 1995 17:06:45 -0400 From: JimIsaak Message-Id: <9505302106.AA21940@csac.ljo.dec.com> To: sc22wg15@dkuug.dk Subject: WG20 (I18n) questions, feedback sought by end of June. X-Charset: ASCII X-Char-Esc: 29 [I'm passing this on to WG15 since there seem to be interested parties associated with WG15's work that may not see the WG20 or SC22 distribution ... please feel free to respond directly to WG20 as indicated in the questionaire; I'm not trying to coordinate a WG15 response to this.] =========================== Return-Path: us1rmc::WINKLER%po3.bb.unisys.com Received: by csac.ljo.dec.com; id AA08148; Wed, 24 May 1995 14:21:53 -0400 Date: Wed, 24 May 1995 14:21:52 -0400 Message-Id: <9505241821.AA08148@csac.ljo.dec.com> From: us1rmc::WINKLER%po3.bb.unisys.com (Winkler, Arnold F [BB]) To: sc22 Cc: "'sc22wg20 [SC22/WG20]'" Subject: (SC22.773) Questionnaire for WD#4 of TR 10176-2 To: Members of SC22 From: Arnold Winkler Date: May 24, 1995 Subject: Questionnaire on Working Draft #4 of TR 10176 SC22/WG20 is asking for your help: Part of the work program of WG20 is the new revision of TR 10176, Guidelines for preparation of programming language standards. We try very hard to introduce the internationalization features, needed in today's world, into the Technical Report and subsequently into all programming languages that don't have these features yet. Document SC22/WG20 N333 is our working draft #4 of the revised TR, the text is also available electronically (address see below). In our discussions within WG20 we could not find consistent answers to all issues and therefore the editor developed the questionnaire to support the process of finding agreement. The questionnaire was distributed on the WG20 list and we got a few answers with valuable input to our considerations. WG20 decided in its last meeting in May 95 to invite the members of SC22, especially National Bodies and the convenors of the other working groups, to contribute their groups opinion to the process. We ask you therefore to answer the questions in attached questionnaire for consideration in our next draft. If at all possible, please provide answers asap, but no later than the end of June 1995. Please send your answers to sc22wg20@dkuug.dk Your help in this matter is highly appreciated. Thank you for your efforts and best regards Arnold Winkler (convenor WG20) ======================================================================= ======================================================================= SC22/WG20 N364 April 1995 QUESTIONNAIRE for PDTR 10176.2 =============================== The WD4 for PDTR 10176 is document SC22/WG20 N333 and can also be obtained from the ftp directory of the following sites: 1. tiu.ac.jp iso/sc22wg20 2. dkuug.dk JTC1/SC22/WG20- The document on dkuug.dk is in 3 formats: tr10176.dvi tr10176.ps tr10176.tes.tar ======================================================================= Questionnaire on Working Draft 4 for PDTR 10176 0. About Yourself Please specify yourself ( ) National contribution of ( ) ( ) Liaison contribution from ( ) ( ) Personal contribution of ( ) 1. Character set support 1.1 Which definition of ``character'' is appropriate from the view point of programming language standard? a. A sequence of one or more bytes representing single graphic symbol b. A member of a set of element used for the organization, control, or representation of data 1.2 How deep should this TR discuss about code representation of character? For example, the difference between UCS and UTF-8 is code representation of character. Should this TR includes guideline for both UCS (multi-octet canonical representation) and UTF-8 (single octet multi-byte representation) ? Or should this TR concentrate in the repertoire of character set regardless of their representation? 1.3 Can this TR request programming language standard to provide the character data type (extended character data type) that large enough to store any character supported in an execution environment ? 1.4 Should this TR discuss about multi-byte coded character (a character may be represented using sequential multiple unit of a character data type) support and required functionality to handle the character as logical unit for character string handling? 1.5 Should this TR discuss about presentation of character on a character cell terminal? - presentation width of CKJ ideographs (that usually two display columns) - presentation of combining character 1.6 Should programming language recognize that a combining sequence is equivalent with a corresponding precomposed character? 1.7 If a programming language standard has subtypes of character data type, e.g., kind=n of FORTRAN, should the programming language allow assignment across those subtypes? In the case of numerical value, most programming languages allow assignment from integer data type to real data type, however in the case of character data type, few programming language standards allow inter subtype assignment. 1.8 If a programming language standard has subtypes of character data type, or multiple character data types, should the language standard provides conversion functionality between those data types? 1.9 Should programming language standard has a capability to handle different encoding of character data simultaneously? 1.10 Can programming language standard assume that encoding of source code character set is identical with the execution time coded character set? 1.11 Should programming language standard support character repertoire outside of ISO/IEC 646 invariant as identifier? 1.12 If programming language standard allow character repertoire outside of ISO/IEC 646 invariant set as identifier, what kinds of characters should be excluded for the identifier? 1.13 If source code of a programming language is written in ISO/IEC 10646, should all space characters (ISO/IEC 10646 includes several space characters) has the same functionality with the space character of ISO/IEC 646? 2. Collation 2.1 Can this TR requests programming language standards to support the expected ISO/IEC 10646 base international default ordering standard? 3. Cultural element support 3.1 Can this TR request programming language standard to provide a functionality to switch a set of cultural elements definition (locale in POSIX and C) that cultural sensitive functions of programming language refers to dynamically? 3.2 Should programming language standard support multiple locale simultaneously? 3.3 Should this TR includes guideline for character classification? 3.4 Should this TR includes guideline for character translation/ transliteration, for example upper casing? 3.5 Can this TR request functionality to test if a character is a member of valid identifier? 3.6 What kinds of cultural elements should be supported by programming language standard? 4. Others 4.1 Which annexes in the WD4 are needed, and which annexes are not needed? 4.2 Is there any guidelines that this TR should provide? End of questionnaire, thank you for your efforts !! % ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ====== % Received: from mail1.digital.com by us1rmc.bb.dec.com (5.65/rmc-22feb94) id AA27129; Wed, 24 May 95 14:22:53 -040 % Received: from dkuug.dk by mail1.digital.com; (5.65 EXP 4/12/95 for V3.2/1.0/WV) id AA06120; Wed, 24 May 1995 11:16:40 -070 % Received: by dkuug.dk id AA03298 (5.65c8/IDA-1.4.4j for SC22-list); Wed, 24 May 1995 18:31:10 +020 % Message-Id: <199505241631.AA03298@dkuug.dk> % From: "Winkler, Arnold F [BB]" % X-Sequence: SC22@dkuug.dk 773 % Errors-To: SC22-request@dkuug.dk % To: sc22 % Cc: "'sc22wg20 [SC22/WG20]'" % Subject: (SC22.773) Questionnaire for WD#4 of TR 10176-2 % Date: Wed, 24 May 95 12:26:00 PDT % Encoding: 304 TEXT % X-Mailer: Microsoft Mail V3.0 % X-Charset: ASCII % X-Char-Esc: 29