bug#39693: Sv: bug#39693: Any chance of fixing --rfc-3339 to conform to the standard?

2020-02-21 Thread Paul Eggert
On 2/20/20 11:56 PM, Mads Bondo Dydensborg wrote: Your statement is in conflict with the message exchange, referenced by the bug I linked to, with, as I understand it, the authors of the standard: Not really. In that email exchange one of the authors of the RFC mentioned a goal of the RFC.

bug#39693: Sv: bug#39693: Any chance of fixing --rfc-3339 to conform to the standard?

2020-02-21 Thread Mads Bondo Dydensborg
Hi again Your statement is in conflict with the message exchange, referenced by the bug I linked to, with, as I understand it, the authors of the standard: https://debbugs.gnu.org/cgi/bugreport.cgi?msg=11;filename=rfc3339+is+the+T+mandatory%3F.eml;att=1;bug=6132 The date-time production in

bug#39693: Any chance of fixing --rfc-3339 to conform to the standard?

2020-02-20 Thread Paul Eggert
On 2/20/20 4:39 AM, Mads Bondo Dydensborg wrote: As have been established in 2006 and again in 2010, the rfc-3339 mandates the use of "T" in a single field timestamp. No, RFC 3339 explicitly allows the use of space. It says: NOTE: ISO 8601 defines date and time separated by "T".

bug#39693: Any chance of fixing --rfc-3339 to conform to the standard?

2020-02-20 Thread Mads Bondo Dydensborg
Hi there As have been established in 2006 and again in 2010, the rfc-3339 mandates the use of "T" in a single field timestamp. This is currently not output by date (version 8.28) Actual (example) output by "date --rfc-3339=ns" 2020-02-20 13:32:19.315773856+01:00 Expected output by above: