Issue 4184: Use of Istring in IDL (ftamftp-ftf) Source: DSTC (Mr. Ted McFadden, mcfadden@dstc.edu.au) Nature: Uncategorized Issue Severity: Summary: The CosFileTransfer module typedef's string to Istring. This was used in the NamingService as a placeholder for an internationalized string type. We would have removed it in the INS FTF if we could have. ;-). Since CosFileTransfer is new the opportunity should be taken to remove IDL constructs that are no longer useful. Resolution: All string references in the IDL have been changed to wstring. Revised Text: All references to the IDL type string have been changed to wstring. Actions taken: January 30, 2001: received issue Discussion: End of Annotations:===== Date: Wed, 31 Jan 2001 00:48:54 +1000 From: Ted McFadden To: issues@omg.org, ftamftp-ftf@omg.org Cc: tmcf@ooc.com.au Subject: ftam/ftp issue: Use of Istring in IDL Message-ID: <20010131004854.G16495@ooc.com.au> Reply-To: Ted McFadden Mail-Followup-To: issues@omg.org, ftamftp-ftf@omg.org Mime-Version: 1.0 Received: from errigal.ooc.com.au (IDENT:root@errigal.ooc.com.au [10.1.1.5]) by janus.ooc.com.au (8.9.3/8.9.3) with ESMTP id AAA08510 for ; Wed, 31 Jan 2001 00:57:43 +1000 Received: (from tmcf@localhost) by errigal.ooc.com.au (8.9.3/8.9.3) id AAA16853 for tmcf@ooc.com.au; Wed, 31 Jan 2001 00:57:43 +1000 Received: from errigal.ooc.com.au (IDENT:root@errigal.ooc.com.au [10.1.1.5]) by janus.ooc.com.au (8.9.3/8.9.3) with ESMTP id AAA08390 for ; Wed, 31 Jan 2001 00:48:54 +1000 Received: (from tmcf@localhost) by errigal.ooc.com.au (8.9.3/8.9.3) id AAA16779 for tmcf@ooc.com.au; Wed, 31 Jan 2001 00:48:54 +1000 X-Mailer: Mutt 1.0i Content-Type: text/plain; charset=us-ascii X-UIDL: ^?ld9pQ5e9$5Fe9"KMd9 Hi, ftam/ftp issue: Use of Istring in IDL ------------------------------------- The CosFileTransfer module typedef's string to Istring. This was used in the NamingService as a placeholder for an internationalized string type. We would have removed it in the INS FTF if we could have. ;-). Since CosFileTransfer is new the opportunity should be taken to remove IDL constructs that are no longer useful. Cheers, Ted -- Ted McFadden tmcf@ooc.com.au Object Oriented Concepts http://www.ooc.com Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill 4169, QLD. Australia Date: Tue, 20 Feb 2001 16:37:00 +1000 From: Ted McFadden To: ftamftp-ftf@omg.org Subject: Comment on ftam/ftp issue 4184: Use of Istring in IDL Message-ID: <20010220163700.C10708@ooc.com.au> Mime-Version: 1.0 X-Mailer: Mutt 1.0i Content-Type: text/plain; charset=us-ascii X-UIDL: "E2!!?~#e9nB,!!SF-e9 Hi, Comment on ftam/ftp issue 4184: Use of Istring in IDL -------------------------------------------- This issue concerned the typedef of string to Istring for `international' string. As noted this typedef doesn't accomplish anything. However the use of the string type for file path names is limiting in environments where file names may not be limited to ISO-latin 1 characters. wstring should be considered to replace string in much of the idl. Cheers, Ted -- Ted McFadden tmcf@ooc.com.au Object Oriented Concepts Inc. - An IONA Company http://www.ooc.com Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill, Brisbane, 4169, QLD. Australia From: "Rutt, T E (Tom)" To: ftamftp-ftf@omg.org, "'Ted McFadden'" Subject: RE: Comment on ftam/ftp issue 4184: Use of Istring in IDL Date: Tue, 20 Feb 2001 18:33:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-UIDL: X=-e9JL!e9MMod9*e>e9 Are you talking about implementations of code set conversion for string? The spec does allow string to carry international code sets if negotiated. What is your point exactly? Tom Rutt terutt@lucent.com ter ---------- From: Ted McFadden [SMTP:tmcf@ooc.com.au] Sent: Tuesday, February 20, 2001 1:37 AM To: ftamftp-ftf@omg.org Subject: Comment on ftam/ftp issue 4184: Use of Istring in IDL Hi, Comment on ftam/ftp issue 4184: Use of Istring in IDL -------------------------------------------- This issue concerned the typedef of string to Istring for `international' string. As noted this typedef doesn't accomplish anything. However the use of the string type for file path names is limiting in environments where file names may not be limited to ISO-latin 1 characters. wstring should be considered to replace string in much of the idl. Cheers, Ted -- Ted McFadden tmcf@ooc.com.au Object Oriented Concepts Inc. - An IONA Company http://www.ooc.com Suite 4, 8 Martha St. +61-7-3324-9633 Camp Hill, Brisbane, 4169, QLD. Australia Date: Wed, 21 Feb 2001 11:17:23 +1000 (EST) From: Michi Henning To: "Rutt, T E (Tom)" cc: ftamftp-ftf@omg.org, "'Ted McFadden'" Subject: RE: Comment on ftam/ftp issue 4184: Use of Istring in IDL In-Reply-To: <4490F7068AC0D111A7120008C72878EC085E69D6@nj7460exch003u.ho.lucent.com> Message-ID: Organization: Object Oriented Concepts MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UIDL: <+>e9J+g!!e@7e9Tlnd9 On Tue, 20 Feb 2001, Rutt, T E (Tom) wrote: > Are you talking about implementations of code set conversion for > string? The spec does allow string to carry international code sets > if negotiated. What is your point exactly? The point here is that a number of file systems permit characters other than ISO Latin-1 as file names. The current spec, however, limits file names to ISO Latin-1, meaning that files containing other characters cannot be dealt with. Cheers, Michi. -- Michi Henning +61 7 3324 9633 Object Oriented Concepts +61 4 1118 2700 (mobile) Suite 4, 8 Martha St +61 7 3324 9799 (fax) Camp Hill 4152 michi@ooc.com.au Brisbane, AUSTRALIA http://www.ooc.com.au/staff/michi-henning.html