From: Marius Bakke <mbakke@fastmail.com>
To: Alex Vong <alexvong1995@gmail.com>, Kenton Varda <kenton@sandstorm.io>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add capnproto.
Date: Thu, 25 Aug 2016 16:52:30 +0100 [thread overview]
Message-ID: <87poow26dd.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87a8g0vp7a.fsf@gmail.com>
Alex Vong <alexvong1995@gmail.com> writes:
>> PS. regarding the man page, I believe Debian mostly generated this
>> page from the capnp tool's help text. I'd accept a patch to
>> c++/src/kj/main.c++ which adds some code to generate man XML format
>> directly, so that we don't have to maintain the same text in multiple
>> places.
>
> I want to ask what is meant by man XML format? Do you mean to generate
> man page? As far as I know, there are at least 2 ways to generate a man
> page. One way is to use help2man, which is probably the Debian's
> approach. Another way is to write the man page in pod (perl's plain old
> documentation) and use pod2man to translate it into a man page. Would
> you accept any of these approaches?
I think Kenton is referring to the Debian manual, which is in XML
format:
https://github.com/thomaslee/capnproto-debian/blob/master/debian/capnp.1.xml
But you are right, it would be better to convert it to a standard format
and simply add a make target for it.
Cheers,
Marius
next prev parent reply other threads:[~2016-08-25 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 8:04 [PATCH] gnu: Add capnproto Kenton Varda
2016-08-25 14:57 ` Marius Bakke
2016-08-25 17:22 ` Kenton Varda
2016-08-25 15:32 ` Alex Vong
2016-08-25 15:52 ` Marius Bakke [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-13 18:48 Marius Bakke
2016-08-14 17:17 ` Leo Famulari
2016-08-14 18:16 ` Marius Bakke
2016-08-19 22:06 ` Leo Famulari
2016-08-19 22:17 ` Leo Famulari
2016-08-20 12:22 ` Marius Bakke
2016-08-23 16:00 ` Leo Famulari
2016-08-23 18:30 ` Marius Bakke
2016-08-23 18:40 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poow26dd.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=kenton@sandstorm.io \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).