From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-1.sys.kth.se (smtp-1.sys.kth.se [130.237.32.175]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id p4HCOu73015828 for ; Tue, 17 May 2011 08:24:56 -0400 (EDT) Received: from mailscan-1.sys.kth.se (mailscan-1.sys.kth.se [130.237.32.91]) by smtp-1.sys.kth.se (Postfix) with ESMTP id 5FE441558AA; Tue, 17 May 2011 14:24:50 +0200 (CEST) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-1.sys.kth.se ([130.237.32.175]) by mailscan-1.sys.kth.se (mailscan-1.sys.kth.se [130.237.32.91]) (amavisd-new, port 10024) with LMTP id q9p4U9GDpQ41; Tue, 17 May 2011 14:24:47 +0200 (CEST) X-KTH-Auth: kristaps [213.103.216.43] X-KTH-mail-from: kristaps@bsd.lv Received: from macky.local (s213-103-216-43.cust.tele2.se [213.103.216.43]) by smtp-1.sys.kth.se (Postfix) with ESMTP id BA2B61568CB; Tue, 17 May 2011 14:24:46 +0200 (CEST) Message-ID: <4DD2690E.2060300@bsd.lv> Date: Tue, 17 May 2011 14:24:46 +0200 From: Kristaps Dzonsons User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 X-Mailinglist: mdocml-discuss Reply-To: discuss@mdocml.bsd.lv MIME-Version: 1.0 To: Sascha Wildner , discuss@mdocml.bsd.lv Subject: Re: libmandoc References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit > I'm thinking of separating libmandoc and mandoc(1) in DragonFly, > assuming libmandoc will make it easier for us to write custom tools for > checking things in manpages. Am I correct in assuming this? > > The headers that should be publically visible in /usr/include should be > , and (as per mandoc(3) manual page), right? > > One last thing: The mandoc(3) manual page has no > > .Sh LIBRARY > .Lb mandoc > > section. Are there plans to add one? Hi Sascha, Hope you don't mind me cross-posting to discuss@, as this deals with deployment and others may be interested. Yes, mandoc(3) is simple and easy (alloc, parsefd, free). Although making sense of what comes out of it can be tricky... ;) In the Makefile, I stipulate `.../include/mandoc' as the installation prefix for include (and library in .../lib/mandoc) files. This is just because I don't like spewing includes all over. If anybody has strong feelings either way, please let me know and I can adjust the default path (this particular part should be in sync with downstream). In thinking carefully about this, I don't suggest flipping on this installation unless you're Ok with having a WIP in base. E.g., I anticipate adding (separating the "tbl" prefixed stuff) and also. Ingo and I fought about whether to have a single file, but in the end his reasoning made more sense than mine. In general, the mandoc.3 library is still `under development', although it's pretty stable in terms of existing functions. Though if anybody's writing a application using mandoc.3 without contacting me first, they're in for some mean surprises (e.g., binary characters for soft-hyphens and such). There are three utilities to date interfacing with libmandoc: mandoc and makewhatis in the mandoc packages, and mandoc.cgi in http://mdocml.bsd.lv/mandoc-cgi/index.html. The mandoc.3 file should also have some more loving before being widely used. The exported types, for instances, are only partially documented. As for `Sh LIBRARY', that's a bug I just fixed. Thanks! Take care, Kristaps -- To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv