From: "Ulrich Spörlein" <uqs@spoerlein.net>
To: Ben Fiedler <bfiedler@asu.edu>
Cc: discuss@mdocml.bsd.lv
Subject: Re: FreeBSD + mandoc (GSoC)
Date: Thu, 27 May 2010 15:13:04 +0200 [thread overview]
Message-ID: <20100527131304.GP88504@acme.spoerlein.net> (raw)
In-Reply-To: <AANLkTiny4fFLqUUEMhJGHfk2d9iYFgYruxEqOaK6j97H@mail.gmail.com>
On Thu, 27.05.2010 at 05:54:39 -0700, Ben Fiedler wrote:
> Hi all,
>
> I'm working on moving mandoc ports to FreeBSD base. Ulrich has informed me
> of related work he's already started; I just wanted to get this list
> notified as well.
>
> Original posting to freebsd-hackers (and several responses) here:
> http://lists.freebsd.org/pipermail/freebsd-hackers/2010-May/031892.htmll
>
> -Ben
Hi Ben, welcome to the mdocml crowd!
Kristaps and gang are aware of my effort of bringing mandoc into FreeBSD
base. You can checkout what has already been done by cloning my
repository:
https://www.spoerlein.net/cgit/cgit.cgi/freebsd.work/?h=mdocml
See clone URLs at the bottom.
Be aware, that I will rebase the mdocml *often*, so you probably don't
want to base work on the mdocml branch itself.
Codewise, there is not that much left to do for the *integration*. We
should look at a man(1)/apropos/whatis replacement and figure out a way
to fallback on groff for broken manpages. Then again, I wanted to wait
till mdocml is more mature and has grown tbl/pic support.
A groff port needs to be done, and we should seriously evaluate the
plan9 troff alternative.
@OpenBSD and NetBSD folks: How good is mandoc at rendering ports/pkgsrc
manpages, ie., how crappy is the markup of pages "out there"?
Cheers,
Uli
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-05-27 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:54 Ben Fiedler
2010-05-27 13:08 ` Ingo Schwarze
2010-05-27 13:13 ` Ulrich Spörlein [this message]
2010-05-28 14:06 ` Kristaps Dzonsons
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=20100527131304.GP88504@acme.spoerlein.net \
--to=uqs@spoerlein.net \
--cc=bfiedler@asu.edu \
--cc=discuss@mdocml.bsd.lv \
/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).