From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Sascha Wildner <saw@online.de>, discuss@mdocml.bsd.lv
Subject: Re: libmandoc
Date: Tue, 17 May 2011 14:24:46 +0200 [thread overview]
Message-ID: <4DD2690E.2060300@bsd.lv> (raw)
In-Reply-To: <op.vvl6mbisr9a2dd@collider.vanilla.local>
> 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
> <man.h>, <mdoc.h> and <mandoc.h> (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 <tbl.h> (separating the "tbl" prefixed stuff) and
<eqn.h> also. Ingo and I fought about whether to have a single
<mandoc.h> 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
parent reply other threads:[~2011-05-17 12:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <op.vvl6mbisr9a2dd@collider.vanilla.local>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD2690E.2060300@bsd.lv \
--to=kristaps@bsd.lv \
--cc=discuss@mdocml.bsd.lv \
--cc=saw@online.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).