Package: roundup
Version: 1.3.3-3
Severity: wishlist

The _User Guide_ document states that

| Date-and-time stamps are specified with the date in international
| standard format (yyyy-mm-dd) joined to the time (hh:mm:ss) by a
| period ..

AFAICT this is *not* the international standard format; both ISO 8601
and RFC 3339 seem to recommend if not mandate the uppercase roman
letter "T" where Roundup expects a period.

>From <http://en.wikipedia.org/wiki/ISO_8601>:

| Combined representations
| ========================
| 
| <date>T<time> <date>T<time>Z 
| 
| Combining date and time representations is quite simple. It is in
| the format of <date>T<time>. The date and time sections are any
| proper representation of the date and time created by following the
| standard. A common use could be
| [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]±[hh]:[mm].
| "1981-04-05T14:30:30-05:00" or
| [YYYY][MM][DD]T[hh][mm][ss]Z. "19810405T193030Z", for example.
| 
| The date and time representations may sometimes appear in proximity,
| separated by a space or other characters, in which case they occupy
| two separate fields in a data system, rather than a single combined
| representation. This is sometimes done for human readability. Unlike
| the above example, "1981-04-05" "14:30:30-05:00" are two separate
| representations, one for date and the other for time.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.21-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages roundup depends on:
ii  adduser                       3.104      add and remove users and groups
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-central                0.5.14     register and build utility for Pyt

roundup recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to