In /usr/src/contrib/mandoc/mandoc.1 we find: macro uses the legacy .Xr man 7 date format .Dq yyyy-dd-mm . Consider using the conventional .Xr mdoc 7 date format when what it means to say is ... yyyy-mm-dd (as parsed by a2time(&t, "%Y-%m-%d", in) mandoc.c)
<https://github.com/freebsd/freebsd-src/blob/75b6c55cb02aaa5d40a725b90ffb672a4c25e2ee/mandoc.1#L839-L851> (2017-07-31) <https://mandoc.bsd.lv/man/mandoc.1.html#legacy> <https://mandoc.bsd.lv/contact.html> Should there be an upstream bug report?
Yeah, there should be an upstream bug report, however you can't report things to their tech@... list unless you're a member. I've subscribed, but will have to wait for an administrator to review it... then I'll send the report, then I'll unsubscribe. What a terrible UX just to submit a simple report!
Submitted upstream @ https://marc.info/?l=mandoc-tech&m=174076536405819&w=2
The patch I sent upstream has been merged.
Fixed in bsd.lv mandoc.1 1.270; i committed your patch unchanged. Thank you for reporting! I also added a paragraph to https://mandoc.bsd.lv/contact.html clarifyong that bug reports can be sent to the private contact address if the reporter does not want to subscribe to a list. While the mandoc developers are easily able to deal with spam, we do not want to expose subscribers of our lists to spam, and we do not want to spend the considerable maintenance effort on our mailing list server that would be required to maintain a more sophisticated spam protection scheme.
Thanks for following up on this. Oddly, I never did get past the "Your request to join the list has been received. However, the gatekeepers are being asked to review it before permitting you to join." response from their list management (and I'm not a subscriber). Glad to hear that they're willing to accept bug reports through other methods.
This fix has been merged to mandoc,