From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from danbala.ifoer.tuwien.ac.at (danbala.ifoer.tuwien.ac.at [128.130.168.64]) by krisdoz.my.domain (8.14.5/8.14.5) with ESMTP id s2VLUNlY026918 for ; Mon, 31 Mar 2014 17:30:23 -0400 (EDT) Received: by danbala.ifoer.tuwien.ac.at (Postfix, from userid 116) id 95FFF390369; Mon, 31 Mar 2014 23:30:20 +0200 (CEST) Date: Mon, 31 Mar 2014 23:30:20 +0200 From: Thomas Klausner To: discuss@mdocml.bsd.lv Subject: Re: pod2mdoc, docbook2mdoc Message-ID: <20140331213020.GD29643@danbala.tuwien.ac.at> References: <53386109.9000504@bsd.lv> <20140331090912.GW26456@danbala.tuwien.ac.at> <533943B9.5080901@bsd.lv> <20140331161315.GC31866@iris.usta.de> <5339C49A.7020502@bsd.lv> <20140331205736.GJ31866@iris.usta.de> X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140331205736.GJ31866@iris.usta.de> On Mon, Mar 31, 2014 at 10:57:36PM +0200, Ingo Schwarze wrote: > > My general thought on pod2mdoc was to avoid invoking perl(1) just to > > run pod2man(1) in the normal chain of looking at POD documents. I > > also thought that, with a few more pod2mdoc smarts, we'll be able to > > deeply mine those documents with mandocdb. From what I understand, > > they're kinda opaque right now. > > All true. I didn't mean to call pod2mdoc useless, no doubt it can > bring us benefits when it will be polished. Actually, I think it can be very useful. NetBSD regularly imports openssl, and the documentation for that is written in .pod files. So for me the most interesting input files are these :) *hinthint* Just in case you don't have enough test cases yet :) Thanks, Thomas -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv