Deal better with time zones and non-specific dates

[ietf-svn-bot]

owner:henrik@levkowetz.com resolution_fixed type_defect | by martin.thomson@gmail.com

---

When xml2rfc is used through a web service or as part of the datatracker submission tool, the client may be in a different time zone than the server, which can cause trouble with the element when the month shifts:

From the automated draft submission:

Validation Error: {'document_date': [u'Document date must be within 3 days of submission date']}

It's December in this part of the planet, soon to be all of the planet, but clearly it's still November whereever the server is running. The draft contains a date field as so:

<date year="2017" month="December"/>

Arguably the date is correct.

---

Issue migrated from trac:337 at 2022-02-05 12:43:51 +0000

[ietf-svn-bot]

@henrik@levkowetz.com changed status from new to closed

[ietf-svn-bot]

@henrik@levkowetz.com changed resolution from `` to fixed

[ietf-svn-bot]

@henrik@levkowetz.com commented

---

Fixed in 573a8bd:

Changed the way defaults are calculated. Previously, today's
date were used to populate missing day if month and year matched, and
to populate month if year matched. However, if today's date lay in an
adjoining month, even if it was within days of that month, the day
would be set to the first of the given month. This commit changes that,
to use the last day of the month instead of the first of the month, if
the month is the previous month to today's date. This will result in
a different derived date than earlier, closer to today's date. This
fixes issue #337.