From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 5605 invoked from network); 4 Jan 2023 07:29:15 -0000 Received: from bsd.lv (HELO mandoc.bsd.lv) (66.111.2.12) by inbox.vuxu.org with ESMTPUTF8; 4 Jan 2023 07:29:15 -0000 Received: from fantadrom.bsd.lv (localhost [127.0.0.1]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id 1b67ccbe for ; Wed, 4 Jan 2023 02:29:14 -0500 (EST) Received: from mx.stare.cz (uvt.stare.cz [185.63.96.79]) by mandoc.bsd.lv (OpenSMTPD) with ESMTP id a181993d for ; Wed, 4 Jan 2023 02:29:12 -0500 (EST) Received: from localhost (stare.cz [local]) by stare.cz (OpenSMTPD) with ESMTPA id a2dba029 for ; Wed, 4 Jan 2023 08:29:11 +0100 (CET) Date: Wed, 4 Jan 2023 08:29:11 +0100 From: Jan Stary To: discuss@mdocml.bsd.lv Subject: docbook2mdoc Dd Message-ID: X-Mailinglist: mandoc-discuss Reply-To: discuss@mandoc.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, it seems that docbook2mdoc simply uses the content of as the text content of Dd. That's fine I guess, but mandoc -Tlint warns that e.g. STYLE: legacy man(7) date format: Dd 2022-11-16 if that's what is. Is this intentionaly left to the human editor to tweak, or would it be worth it to massage such "dates" into the canonical "Dd November 16, 2022"? (I assume docbook2mdoc only does what it has to do to get out the docbook hell, not touching text content.) Jan -- To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv