|
1 /* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */ |
|
2 /* This Source Code Form is subject to the terms of the Mozilla Public |
|
3 * License, v. 2.0. If a copy of the MPL was not distributed with this |
|
4 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ |
|
5 |
|
6 const HOURS_TO_MINUTES = 60; |
|
7 const MINUTES_TO_SECONDS = 60; |
|
8 const SECONDS_TO_MILLISECONDS = 1000; |
|
9 const MINUTES_TO_MILLISECONDS = MINUTES_TO_SECONDS * SECONDS_TO_MILLISECONDS; |
|
10 const HOURS_TO_MILLISECONDS = HOURS_TO_MINUTES * MINUTES_TO_MILLISECONDS; |
|
11 |
|
12 this.EXPORTED_SYMBOLS = ["ISO8601DateUtils"]; |
|
13 |
|
14 debug("*** loading ISO8601DateUtils\n"); |
|
15 |
|
16 this.ISO8601DateUtils = { |
|
17 |
|
18 /** |
|
19 * XXX Thunderbird's W3C-DTF function |
|
20 * |
|
21 * Converts a W3C-DTF (subset of ISO 8601) date string to a Javascript |
|
22 * date object. W3C-DTF is described in this note: |
|
23 * http://www.w3.org/TR/NOTE-datetime IETF is obtained via the Date |
|
24 * object's toUTCString() method. The object's toString() method is |
|
25 * insufficient because it spells out timezones on Win32 |
|
26 * (f.e. "Pacific Standard Time" instead of "PST"), which Mail doesn't |
|
27 * grok. For info, see |
|
28 * http://lxr.mozilla.org/mozilla/source/js/src/jsdate.c#1526. |
|
29 */ |
|
30 parse: function ISO8601_parse(aDateString) { |
|
31 var dateString = aDateString; |
|
32 if (!dateString.match('-')) { |
|
33 // Workaround for server sending |
|
34 // dates such as: 20030530T11:18:50-08:00 |
|
35 // instead of: 2003-05-30T11:18:50-08:00 |
|
36 var year = dateString.slice(0, 4); |
|
37 var month = dateString.slice(4, 6); |
|
38 var rest = dateString.slice(6, dateString.length); |
|
39 dateString = year + "-" + month + "-" + rest; |
|
40 } |
|
41 |
|
42 var parts = dateString.match(/(\d{4})(-(\d{2,3}))?(-(\d{2}))?(T(\d{2}):(\d{2})(:(\d{2})(\.(\d+))?)?(Z|([+-])(\d{2}):(\d{2}))?)?/); |
|
43 |
|
44 // Here's an example of a W3C-DTF date string and what .match returns for it. |
|
45 // |
|
46 // date: 2003-05-30T11:18:50.345-08:00 |
|
47 // date.match returns array values: |
|
48 // |
|
49 // 0: 2003-05-30T11:18:50-08:00, |
|
50 // 1: 2003, |
|
51 // 2: -05, |
|
52 // 3: 05, |
|
53 // 4: -30, |
|
54 // 5: 30, |
|
55 // 6: T11:18:50-08:00, |
|
56 // 7: 11, |
|
57 // 8: 18, |
|
58 // 9: :50, |
|
59 // 10: 50, |
|
60 // 11: .345, |
|
61 // 12: 345, |
|
62 // 13: -08:00, |
|
63 // 14: -, |
|
64 // 15: 08, |
|
65 // 16: 00 |
|
66 |
|
67 // Create a Date object from the date parts. Note that the Date |
|
68 // object apparently can't deal with empty string parameters in lieu |
|
69 // of numbers, so optional values (like hours, minutes, seconds, and |
|
70 // milliseconds) must be forced to be numbers. |
|
71 var date = new Date(parts[1], parts[3] - 1, parts[5], parts[7] || 0, |
|
72 parts[8] || 0, parts[10] || 0, parts[12] || 0); |
|
73 |
|
74 // We now have a value that the Date object thinks is in the local |
|
75 // timezone but which actually represents the date/time in the |
|
76 // remote timezone (f.e. the value was "10:00 EST", and we have |
|
77 // converted it to "10:00 PST" instead of "07:00 PST"). We need to |
|
78 // correct that. To do so, we're going to add the offset between |
|
79 // the remote timezone and UTC (to convert the value to UTC), then |
|
80 // add the offset between UTC and the local timezone //(to convert |
|
81 // the value to the local timezone). |
|
82 |
|
83 // Ironically, W3C-DTF gives us the offset between UTC and the |
|
84 // remote timezone rather than the other way around, while the |
|
85 // getTimezoneOffset() method of a Date object gives us the offset |
|
86 // between the local timezone and UTC rather than the other way |
|
87 // around. Both of these are the additive inverse (i.e. -x for x) |
|
88 // of what we want, so we have to invert them to use them by |
|
89 // multipying by -1 (f.e. if "the offset between UTC and the remote |
|
90 // timezone" is -5 hours, then "the offset between the remote |
|
91 // timezone and UTC" is -5*-1 = 5 hours). |
|
92 |
|
93 // Note that if the timezone portion of the date/time string is |
|
94 // absent (which violates W3C-DTF, although ISO 8601 allows it), we |
|
95 // assume the value to be in UTC. |
|
96 |
|
97 // The offset between the remote timezone and UTC in milliseconds. |
|
98 var remoteToUTCOffset = 0; |
|
99 if (parts[13] && parts[13] != "Z") { |
|
100 var direction = (parts[14] == "+" ? 1 : -1); |
|
101 if (parts[15]) |
|
102 remoteToUTCOffset += direction * parts[15] * HOURS_TO_MILLISECONDS; |
|
103 if (parts[16]) |
|
104 remoteToUTCOffset += direction * parts[16] * MINUTES_TO_MILLISECONDS; |
|
105 } |
|
106 remoteToUTCOffset = remoteToUTCOffset * -1; // invert it |
|
107 |
|
108 // The offset between UTC and the local timezone in milliseconds. |
|
109 var UTCToLocalOffset = date.getTimezoneOffset() * MINUTES_TO_MILLISECONDS; |
|
110 UTCToLocalOffset = UTCToLocalOffset * -1; // invert it |
|
111 date.setTime(date.getTime() + remoteToUTCOffset + UTCToLocalOffset); |
|
112 |
|
113 return date; |
|
114 }, |
|
115 |
|
116 create: function ISO8601_create(aDate) { |
|
117 function zeropad (s, l) { |
|
118 s = s.toString(); // force it to a string |
|
119 while (s.length < l) { |
|
120 s = '0' + s; |
|
121 } |
|
122 return s; |
|
123 } |
|
124 |
|
125 var myDate; |
|
126 // if d is a number, turn it into a date |
|
127 if (typeof aDate == 'number') { |
|
128 myDate = new Date() |
|
129 myDate.setTime(aDate); |
|
130 } else { |
|
131 myDate = aDate; |
|
132 } |
|
133 |
|
134 // YYYY-MM-DDThh:mm:ssZ |
|
135 var result = zeropad(myDate.getUTCFullYear (), 4) + |
|
136 zeropad(myDate.getUTCMonth () + 1, 2) + |
|
137 zeropad(myDate.getUTCDate (), 2) + 'T' + |
|
138 zeropad(myDate.getUTCHours (), 2) + ':' + |
|
139 zeropad(myDate.getUTCMinutes (), 2) + ':' + |
|
140 zeropad(myDate.getUTCSeconds (), 2) + 'Z'; |
|
141 |
|
142 return result; |
|
143 } |
|
144 } |