From is@sac.sfbay.sun.com Fri Dec 11 18:12:07 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBC2C623007809 for ; Fri, 11 Dec 2009 18:12:07 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBC2C1dc003529; Fri, 11 Dec 2009 20:12:06 -0600 (CST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUI00I0POS5VY00@nwk-avmta-1.sfbay.Sun.COM>; Fri, 11 Dec 2009 18:12:05 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUI00DXSOS5AXA0@nwk-avmta-1.sfbay.Sun.COM>; Fri, 11 Dec 2009 18:12:05 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBC2C43i001344; Fri, 11 Dec 2009 18:12:04 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBC2C3RC007802; Fri, 11 Dec 2009 18:12:03 -0800 (PST) Received: (from is@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id nBC2C3Q9007798; Fri, 11 Dec 2009 18:12:03 -0800 (PST) Date: Fri, 11 Dec 2009 18:12:03 -0800 (PST) From: Ienup Sung Subject: Date/time conversion specification compatibility [PSARC/2009/677 FastTrack timeout 12/18/2009] To: PSARC-ext@sun.com Cc: i18n-discuss@opensolaris.org Message-id: <200912120212.nBC2C3Q9007798@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 2404 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Date/time conversion specification compatibility 1.2. Name of Document Author/Supplier: Author: Ienup Sung 1.3 Date of This Document: 11 December, 2009 4. Technical Description OVERVIEW This case extends the support for conversion specifications available at libc date/time format conversion functions so that they will be more compatible with other platforms such as glibc based Linux distros, MacOS X, and FreeBSD. (Related compatibility CRs are shown at [1].) In more detail, ascftime(3C), cftime(3C), strftime(3C), and wcsftime(3C) will recognize and support 5 new conversion specifications (%+, %P, %s, %OB, %OV), 5 optional flag characters (#, -, 0, ^, _) governing padding and case conversion behaviors, and optional field width as described in [2]. Also, getdate(3C) and strptime(3C) will recognize and support 9 new conversion specifications (%F, %g, %G, %k, %l, %P, %u, %V, %z) as described at [2]. INTERFACE STABILITY AND RELEASE BINDING This project imports no notable interfaces. This project exports: Interface Stability Note --------- --------- ---- ascftime(3C), Committed See strftime.3c at [2] for first 3 API. cftime(3C), There is no update on the wcsftime(3C) strftime(3C), and man page; refer to strftime(3C) as wcsftime(3C) usual. getdate(3C) Committed [2] strptime(3C) Committed [2] This project asks for Micro/Patch release binding. REFERENCES [1] Related CRs: 6486542 strftime(3c) needs to support GNU extension in %-m and %-d 6794314 strptime() does not parse '%l' 6597268 strptime() should support %F and %z [2] Updated man pages in flat text with change bars indicating the changed portions and also corresponding diff files at the materials directory of the case: getdate.3c getdate.3c.diff strftime.3c strftime.3c.diff strptime.3c strptime.3c.diff 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: G11N 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From John.Fischer@sun.com Sun Dec 13 20:21:57 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBE4Lvfd006997 for ; Sun, 13 Dec 2009 20:21:57 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBE4LuqM003276 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Sun, 13 Dec 2009 22:21:57 -0600 (CST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUM00L0BK4LV000@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 13 Dec 2009 21:21:57 -0700 (MST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUM00I8NK4J3CA0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 13 Dec 2009 21:21:55 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nBE4Ltge019028 for ; Mon, 14 Dec 2009 04:21:55 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUM00K00K4GJB00@mail-amer.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Sun, 13 Dec 2009 21:21:55 -0700 (MST) Received: from [192.168.10.7] ([unknown] [76.20.56.122]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUM009XZK4IXXB0@mail-amer.sun.com>; Sun, 13 Dec 2009 21:21:55 -0700 (MST) Date: Sun, 13 Dec 2009 20:21:49 -0800 From: John Fischer Subject: Re: Date/time conversion specification compatibility [PSARC/2009/677 FastTrack timeout 12/18/2009] In-reply-to: <200912120212.nBC2C3Q9007798@sac.sfbay.sun.com> Sender: John.Fischer@sun.com To: Ienup Sung Cc: PSARC-ext@sun.com, i18n-discuss@opensolaris.org Reply-to: John.Fischer@sun.com Message-id: <4B25BD5D.7070202@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200912120212.nBC2C3Q9007798@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.23 (X11/20091124) Status: RO Content-Length: 2674 +1 Ienup Sung wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Date/time conversion specification compatibility > 1.2. Name of Document Author/Supplier: > Author: Ienup Sung > 1.3 Date of This Document: > 11 December, 2009 > 4. Technical Description > > OVERVIEW > > This case extends the support for conversion specifications available at > libc date/time format conversion functions so that they will be more compatible > with other platforms such as glibc based Linux distros, MacOS X, and FreeBSD. > (Related compatibility CRs are shown at [1].) > > In more detail, ascftime(3C), cftime(3C), strftime(3C), and wcsftime(3C) will > recognize and support 5 new conversion specifications (%+, %P, %s, %OB, %OV), > 5 optional flag characters (#, -, 0, ^, _) governing padding and case > conversion behaviors, and optional field width as described in [2]. Also, > getdate(3C) and strptime(3C) will recognize and support 9 new conversion > specifications (%F, %g, %G, %k, %l, %P, %u, %V, %z) as described at [2]. > > > INTERFACE STABILITY AND RELEASE BINDING > > This project imports no notable interfaces. This project exports: > > Interface Stability Note > --------- --------- ---- > ascftime(3C), Committed See strftime.3c at [2] for first 3 API. > cftime(3C), There is no update on the wcsftime(3C) > strftime(3C), and man page; refer to strftime(3C) as > wcsftime(3C) usual. > > getdate(3C) Committed [2] > > strptime(3C) Committed [2] > > This project asks for Micro/Patch release binding. > > > REFERENCES > > [1] Related CRs: > 6486542 strftime(3c) needs to support GNU extension in %-m and %-d > 6794314 strptime() does not parse '%l' > 6597268 strptime() should support %F and %z > [2] Updated man pages in flat text with change bars indicating the changed > portions and also corresponding diff files at the materials directory of > the case: > getdate.3c > getdate.3c.diff > strftime.3c > strftime.3c.diff > strptime.3c > strptime.3c.diff > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > G11N > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc@opensolaris.org From sacadmin Tue Dec 15 18:08:49 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBG28njY025035 for ; Tue, 15 Dec 2009 18:08:49 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id nBG28m0V020918 for <@sunmail2sca.sfbay.sun.com:psarc-record@sun.com>; Tue, 15 Dec 2009 19:08:49 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUQ00H073AO5W00@nwk-avmta-1.sfbay.Sun.COM> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:08:48 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUQ00I7N3AODGF0@nwk-avmta-1.sfbay.Sun.COM> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:08:48 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBG28mWV017086 for ; Tue, 15 Dec 2009 18:08:48 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUQ00J002WV5T00@fe-sfbay-10.sun.com> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:08:48 -0800 (PST) Received: from [192.168.1.93] ([unknown] [129.150.228.103]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUQ00MRP3ANWY80@fe-sfbay-10.sun.com> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:08:48 -0800 (PST) Date: Tue, 15 Dec 2009 18:05:52 -0800 From: Ienup Sung Subject: PSARC/2009/677 Sender: Ienup.Sung@sun.com To: psarc-record@sun.com Reply-to: Ienup.Sung@sun.com Message-id: <4B284080.5050007@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.17 (X11/20081010) Status: RO Content-Length: 2170 I'm forwarding the email from Don for the record. Ienup -------- Original Message -------- Subject: Re: opensolaris-arc Digest, Vol 46, Issue 49 Date: Tue, 15 Dec 2009 17:08:51 -0800 From: Don Cragun To: is@sac.sfbay.sun.com CC: PSARC-ext@sun.com, i18n-discuss@opensolaris.org References: > Date: Fri, 11 Dec 2009 18:12:03 -0800 (PST) > From: Ienup Sung > Subject: Date/time conversion specification compatibility > [PSARC/2009/677 FastTrack timeout 12/18/2009] Hi Ienup, I support the changes in functionality provided by this case. However, I have a few minor quibbles with the references to ISO 8601 in the provided man page updates: 1. A revision to ISO 8601 was adopted in 2004, so ISO 8601:2000 is obsolete. 2. ISO 8601 specifies dozens of "standard date formats" so saying that %F uses "the ISO 8601:2000 standard date format" is misleading. 3. It is strange that %F specifies an ISO 8601 Extended format (with '-' separators between fields) and a %z using Basic format (without a ':' separator). ISO 8601 explicitly disallows any date and time representation where basic and extended formats are mixed; all date, time, and offset fields must be in basic format, or all of the fields must be in extended format. From getdate(3c): %F Equivalent to %Y-%m-%d (the ISO 8601:2000 standard date | format). | should be: %F Equivalent to %Y-%m-%d (the ISO 8601:2004 standard date | in extended format). | and: %z Offset from UTC in ISO 8601:2000 standard format (+hhmm | or -hhmm), or no characters if no time zone is determinable. | should be: %z Offset from UTC in ISO 8601:2004 standard basic format (+hhmm | or -hhmm), or no characters if no time zone is determinable. | The same changes are needed to the %F and %z descriptions in strftime(3c) and strptime(3c). Cheers, Don From sacadmin Tue Dec 15 18:09:50 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBG29oCw025078 for ; Tue, 15 Dec 2009 18:09:50 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBG29ouJ008937 for <@sunmail2sca.sfbay.sun.com:psarc-record@sun.com>; Tue, 15 Dec 2009 18:09:50 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUQ00H053CEEJ00@nwk-avmta-1.sfbay.Sun.COM> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:09:50 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUQ00J4C3CD23D0@nwk-avmta-1.sfbay.Sun.COM> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:09:49 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBG29na3029276 for ; Tue, 15 Dec 2009 18:09:49 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUQ00J002WV5T00@fe-sfbay-10.sun.com> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:09:49 -0800 (PST) Received: from [192.168.1.93] ([unknown] [129.150.228.103]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUQ00MXL3C6WY80@fe-sfbay-10.sun.com> for psarc-record@sun.com (ORCPT psarc-record@sun.com); Tue, 15 Dec 2009 18:09:43 -0800 (PST) Date: Tue, 15 Dec 2009 18:06:47 -0800 From: Ienup Sung Subject: PSARC/2009/677 Sender: Ienup.Sung@Sun.COM To: psarc-record@Sun.COM Reply-to: Ienup.Sung@Sun.COM Message-id: <4B2840B7.1060100@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.17 (X11/20081010) Status: RO Content-Length: 2594 Here's another (and hopefully the last) forwarding for the record. Ienup -------- Original Message -------- Subject: Re: opensolaris-arc Digest, Vol 46, Issue 49 Date: Tue, 15 Dec 2009 17:36:23 -0800 From: Ienup Sung Reply-To: Ienup.Sung@Sun.COM Organization: Sun Microsystems, Inc. To: Don Cragun CC: PSARC-ext@sun.com, i18n-discuss@opensolaris.org References: Don Cragun wrote at 12/15/09 17:08: > Hi Ienup, > I support the changes in functionality provided by this case. > However, I have a few minor quibbles with the references to ISO 8601 > in the provided man page updates: > 1. A revision to ISO 8601 was adopted in 2004, so ISO 8601:2000 is > obsolete. > 2. ISO 8601 specifies dozens of "standard date formats" so saying that > %F uses "the ISO 8601:2000 standard date format" is misleading. > 3. It is strange that %F specifies an ISO 8601 Extended format (with '-' > separators between fields) and a %z using Basic format (without a ':' > separator). ISO 8601 explicitly disallows any date and time > representation where basic and extended formats are mixed; all date, > time, and offset fields must be in basic format, or all of the > fields must be in extended format. > > From getdate(3c): > %F Equivalent to %Y-%m-%d (the ISO 8601:2000 standard date | > format). | > should be: > %F Equivalent to %Y-%m-%d (the ISO 8601:2004 standard date | > in extended format). | > > and: > %z Offset from UTC in ISO 8601:2000 standard format (+hhmm | > or -hhmm), or no characters if no time zone is determinable. | > should be: > %z Offset from UTC in ISO 8601:2004 standard basic format (+hhmm | > or -hhmm), or no characters if no time zone is determinable. | > > The same changes are needed to the %F and %z descriptions in strftime(3c) > and strptime(3c). > > Cheers, > Don Hello Don, Thanks very much for your comment. I updated as you pointed out and placed the updated man pages and diff files at the materials directory of the case. In the previous man pages from me, I didn't update them in this regard since XSH6 specs/man pages also appear still referencing ISO 8601:2000 and in the manner shown in the current man pages (of before this project). Ienup From dcragun@sonic.net Wed Dec 16 01:23:18 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBG9NIgm015809 for ; Wed, 16 Dec 2009 01:23:18 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBG9NGWv000289; Wed, 16 Dec 2009 03:23:17 -0600 (CST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUQ00J0BNET4500@nwk-avmta-1.sfbay.Sun.COM>; Wed, 16 Dec 2009 01:23:17 -0800 (PST) Received: from sca-ea-mail-3.sun.com ([192.18.43.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUQ007H8NESBOE0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 16 Dec 2009 01:23:16 -0800 (PST) Received: from relay42i.sun.com ([192.5.209.72]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id nBG9AtHE013958; Wed, 16 Dec 2009 09:23:16 +0000 (GMT) Received: from mmp43es.mmp.us.syntegra.com ([160.41.221.12] [160.41.221.12]) by relay42i.sun.com with ESMTP id BT-MMP-2886703; Wed, 16 Dec 2009 09:23:16 +0000 (Z) Received: from relay43i.sun.com (relay43i.sun.com [192.5.209.74]) by mmp43es.mmp.us.syntegra.com with ESMTP id BT-MMP-7523208; Wed, 16 Dec 2009 09:23:15 +0000 (Z) Received: from b.mail.sonic.net ([64.142.19.5] [64.142.19.5]) by relay4i.sun.com with ESMTP id BT-MMP-3594489; Wed, 16 Dec 2009 09:23:15 +0000 (Z) Received: from [10.0.0.7] (76-191-129-144.dsl.dynamic.sonic.net [76.191.129.144]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id nBG9MdAI005594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 16 Dec 2009 01:22:39 -0800 Date: Wed, 16 Dec 2009 01:22:38 -0800 From: Don Cragun Subject: Re: Date/time conversion specification compatibility [PSARC/2009/677 FastTrack timeout 12/18/2009] To: Ienup.Sung@sun.com Cc: PSARC-ext@sun.com, i18n-discuss@opensolaris.org Message-id: <900732A9-E5EE-4F92-B0C1-BBCF34A91428@sonic.net> MIME-version: 1.0 X-Mailer: Apple Mail (2.1077) Content-type: text/plain; charset=utf-8 X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=-2.6/5.0, scanned in 0.208sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <69710438-23E1-4A80-ADED-07C9A4996AC6@sonic.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by sac.sfbay.sun.com id nBG9NIgm015809 Status: RO Content-Length: 3896 Sorry about that. Let's try again with the correct subject line... Begin forwarded message: > From: Don Cragun > Date: December 16, 2009 1:08:38 AM PST > To: Ienup.Sung@Sun.COM > Cc: PSARC-ext@Sun.COM, i18n-discuss@opensolaris.org > Subject: Re: opensolaris-arc Digest, Vol 46, Issue 49 > > On Dec 15, 2009, at 5:36 PM, Ienup Sung wrote: > >> Don Cragun wrote at 12/15/09 17:08: >>> Hi Ienup, >>> I support the changes in functionality provided by this case. >>> However, I have a few minor quibbles with the references to ISO 8601 >>> in the provided man page updates: >>> 1. A revision to ISO 8601 was adopted in 2004, so ISO 8601:2000 is >>> obsolete. >>> 2. ISO 8601 specifies dozens of "standard date formats" so saying that >>> %F uses "the ISO 8601:2000 standard date format" is misleading. >>> 3. It is strange that %F specifies an ISO 8601 Extended format (with '-' >>> separators between fields) and a %z using Basic format (without a ':' >>> separator). ISO 8601 explicitly disallows any date and time >>> representation where basic and extended formats are mixed; all date, >>> time, and offset fields must be in basic format, or all of the >>> fields must be in extended format. >>> From getdate(3c): >>> %F Equivalent to %Y-%m-%d (the ISO 8601:2000 standard date | >>> format). | >>> should be: >>> %F Equivalent to %Y-%m-%d (the ISO 8601:2004 standard date | >>> in extended format). | >>> and: >>> %z Offset from UTC in ISO 8601:2000 standard format (+hhmm | >>> or -hhmm), or no characters if no time zone is determinable. | >>> should be: >>> %z Offset from UTC in ISO 8601:2004 standard basic format (+hhmm | >>> or -hhmm), or no characters if no time zone is determinable. | >>> The same changes are needed to the %F and %z descriptions in strftime(3c) >>> and strptime(3c). >>> Cheers, >>> Don >> >> Hello Don, >> >> Thanks very much for your comment. I updated as you pointed out and >> placed the updated man pages and diff files at the materials directory of >> the case. >> >> In the previous man pages from me, I didn't update them in this regard >> since XSH6 specs/man pages also appear still referencing ISO 8601:2000 >> and in the manner shown in the current man pages (of before this project). >> >> Ienup >> > > The description of the F conversion specifier in XSH7 is: > "CX F Equivalent to %+4Y-%m-%d if no flag and no minimum field width > are specified. [tm_year, tm_mon, tm_mday] > > "CX If a minimum field width of x is specified, the year shall be > output as if by the Y specifier (described below) with whatever > flag was given and a minimum field width of x−6. If x is less > than 6, the behavior shall be as if x equalled 6. > > "CX If the minimum field width is specified to be 10, and the year > is four digits long, then the output string produced will match > the ISO 8601:2004 standard subclause 4.1.2.2 complete > representation, extended format date representation of a > specific day. If a + flag is specified, a minimum field width > of x is specified, and x−7 bytes are sufficient to hold the > digits of the year (not including any needed sign character), > then the output will match the ISO 8601: 2004 standard > subclause 4.1.2.4 complete representation, expanded format > date representation of a specific day." > > I was working on the plans for providing SUSv4 conformance to Solaris > next when I was RIFed. Obviously, these functions all need to be > updated if Sun or Oracle intend to get the next UNIX brand for an > upcoming Solaris release. > > - Don From Ienup.Sung@Sun.COM Wed Dec 16 09:23:29 2009 Received: from sunmail6brm.central.sun.com (sunmail6brm.Central.Sun.COM [129.147.4.169]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBGHNSqF023335 for ; Wed, 16 Dec 2009 09:23:28 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail6brm.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.4) with ESMTP id nBGHNSp9022932 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 16 Dec 2009 11:23:28 -0600 (CST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUR003019N4XU00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 16 Dec 2009 09:23:28 -0800 (PST) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUR00MLW9N3PI90@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 16 Dec 2009 09:23:27 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBGHNRQ7029920 for ; Wed, 16 Dec 2009 09:23:27 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUR001009MREV00@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 16 Dec 2009 09:23:27 -0800 (PST) Received: from [192.168.1.93] ([unknown] [129.150.228.186]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUR002T39MX5U60@fe-sfbay-10.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Wed, 16 Dec 2009 09:23:27 -0800 (PST) Date: Wed, 16 Dec 2009 09:20:25 -0800 From: Ienup Sung Subject: Re: Date/time conversion specification compatibility [PSARC/2009/677 FastTrack timeout 12/18/2009] In-reply-to: <900732A9-E5EE-4F92-B0C1-BBCF34A91428@sonic.net> Sender: Ienup.Sung@Sun.COM To: Don Cragun Cc: PSARC-ext@Sun.COM, i18n-discuss@opensolaris.org Reply-to: Ienup.Sung@Sun.COM Message-id: <4B2916D9.3010109@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 8BIT X-PMX-Version: 5.4.1.325704 References: <69710438-23E1-4A80-ADED-07C9A4996AC6@sonic.net> <900732A9-E5EE-4F92-B0C1-BBCF34A91428@sonic.net> User-Agent: Thunderbird 2.0.0.17 (X11/20081010) Status: RO Content-Length: 1611 Don Cragun wrote at 12/16/09 01:22: >> The description of the F conversion specifier in XSH7 is: >> "CX F Equivalent to %+4Y-%m-%d if no flag and no minimum field width >> are specified. [tm_year, tm_mon, tm_mday] >> >> "CX If a minimum field width of x is specified, the year shall be >> output as if by the Y specifier (described below) with whatever >> flag was given and a minimum field width of x−6. If x is less >> than 6, the behavior shall be as if x equalled 6. >> >> "CX If the minimum field width is specified to be 10, and the year >> is four digits long, then the output string produced will match >> the ISO 8601:2004 standard subclause 4.1.2.2 complete >> representation, extended format date representation of a >> specific day. If a + flag is specified, a minimum field width >> of x is specified, and x−7 bytes are sufficient to hold the >> digits of the year (not including any needed sign character), >> then the output will match the ISO 8601: 2004 standard >> subclause 4.1.2.4 complete representation, expanded format >> date representation of a specific day." >> >> I was working on the plans for providing SUSv4 conformance to Solaris >> next when I was RIFed. Obviously, these functions all need to be >> updated if Sun or Oracle intend to get the next UNIX brand for an >> upcoming Solaris release. >> >> - Don Thanks for the information. I'm sure that once we have the SUSv4 for Solaris project going, we will implement the new spec to conform to the new standard. Ienup From Ienup.Sung@sun.com Wed Dec 16 10:15:26 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id nBGIFPTg026866 for ; Wed, 16 Dec 2009 10:15:26 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.4) with ESMTP id nBGIFLk9029584 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 16 Dec 2009 11:15:25 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KUR0071ZC1O0E00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 16 Dec 2009 10:15:24 -0800 (PST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KUR00MUXC1OPEC0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 16 Dec 2009 10:15:24 -0800 (PST) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nBGIFNrU000968 for ; Wed, 16 Dec 2009 10:15:24 -0800 (PST) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0KUR00200AHPJF00@fe-sfbay-10.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 16 Dec 2009 10:15:23 -0800 (PST) Received: from [192.168.1.93] ([unknown] [129.150.228.186]) by fe-sfbay-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0KUR00LE8C1I8B70@fe-sfbay-10.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 16 Dec 2009 10:15:19 -0800 (PST) Date: Wed, 16 Dec 2009 10:12:22 -0800 From: Ienup Sung Subject: Re: Date/time conversion specification compatibility [PSARC/2009/677 FastTrack timeout 12/18/2009] In-reply-to: <4B2916D9.3010109@sun.com> Sender: Ienup.Sung@sun.com To: PSARC-ext@sun.com Cc: i18n-discuss@opensolaris.org Reply-to: Ienup.Sung@sun.com Message-id: <4B292306.9040202@sun.com> Organization: Sun Microsystems, Inc. MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <69710438-23E1-4A80-ADED-07C9A4996AC6@sonic.net> <900732A9-E5EE-4F92-B0C1-BBCF34A91428@sonic.net> <4B2916D9.3010109@sun.com> User-Agent: Thunderbird 2.0.0.17 (X11/20081010) Status: RO Content-Length: 115 This case was approved during today's PSARC review meeting. Thanks, John and Don, for your +1 and comment. Ienup