From: John Spencer <maillist-musl@barfooze.de>
To: mtk.manpages@gmail.com
Cc: John Spencer <maillist-musl@barfooze.de>,
musl@lists.openwall.com, Isaac <idunham@lavabit.com>,
Rob Landley <rob@landley.net>,
Felix Janda <felix.janda@posteo.de>
Subject: Re: Re: status of POSIX man pages?
Date: Mon, 09 Sep 2013 06:44:37 +0200 [thread overview]
Message-ID: <522D5235.4090403@barfooze.de> (raw)
In-Reply-To: <CAKgNAkh85Q22zB3s_+xgzgTB8qFULjgwrBpZuCmvFi9vZQKZAA@mail.gmail.com>
On 09/08/2013 08:05 AM, Michael Kerrisk (man-pages) wrote:
> On Fri, Sep 6, 2013 at 2:23 PM, John Spencer<maillist-musl@barfooze.de> wrote:
>> On 07/26/2013 09:20 PM, Isaac wrote:
>>>
>>> On Tue, Jul 02, 2013 at 03:08:52AM +0200, Michael Kerrisk (man-pages)
>>> wrote:
>>>>
>>>> As of a few days ago, the necessary permissions are granted. I do not
>>>> yet have the source files (and so am unsure of the source format), but
>>>> I expect that they will become available to us in the next couple of
>>>> weeks.
>>>
>>>
>>> I'm curious what the status of this is. Do you have the sources yet?
>>>
>>
>> i am very interested in a status update as well.
>> getting the posix 2008 manpages into my distro is a todo item since a long
>> time
>> https://github.com/rofl0r/sabotage/issues/34
>
> A while back we got permission from the IEEE and The Open Group to use
> the POSIX.1-2013 pages (==POSIX.1-2008 + Technical Corrigendum 1,
> published 2013).
>
> However, the source text that has been provided to us needs massaging
> in a number of ways before it can be published as a set of standalone
> pages. Felix Janda kindly offered to take on that task, and has been
> making very good progress. I expect that in a week or two, we'll have
> a set of pages for public review (to see if there are any remaining
> bugs in the "massaging process" that Felix or I did not spot).
>
that's very good news.
btw, i am currently writing (or improving) a non-bloated man
implementation: https://raw.github.com/rofl0r/hardcore-utils/master/man.c .
in the process i noted that the posix manpages from 2003 make use of
some groff features like the tbl preprocessor (a hideous hack to display
html-like tables in a completely unidiomatic way), for example in man 1p
printf.
those features are not supported by any traditional *roff
implementation, so i wonder if the next iteration of the posix manpages
could stick to the basic nroff function set to improve compatibility...
regards,
--JS
next prev parent reply other threads:[~2013-09-09 4:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 17:44 Request for volunteers Felix Janda
2013-07-02 1:08 ` Michael Kerrisk (man-pages)
2013-07-06 21:52 ` Linux manpages (was Re: [musl] Request for volunteers) Isaac
2013-07-06 22:12 ` Michael Kerrisk (man-pages)
2013-07-06 23:04 ` Justin Cormack
2013-07-07 0:03 ` Rich Felker
2013-07-09 0:18 ` Michael Kerrisk
2013-07-09 2:36 ` Kurt H Maier
2013-07-09 2:53 ` Rich Felker
2013-07-09 5:28 ` Michael Kerrisk (man-pages)
2013-07-10 19:39 ` Rob Landley
2013-07-09 16:42 ` Rob Landley
2013-07-09 16:50 ` Rich Felker
2013-07-26 19:20 ` status of POSIX man pages? (was: " Isaac
2013-09-06 12:23 ` Re: status of POSIX man pages? John Spencer
2013-09-08 6:05 ` Michael Kerrisk (man-pages)
2013-09-09 4:44 ` John Spencer [this message]
2013-09-09 5:29 ` Anthony J. Bentley
2013-09-09 5:40 ` Daniel Cegiełka
2013-09-19 2:58 ` Rob Landley
2013-09-19 9:54 ` John Spencer
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=522D5235.4090403@barfooze.de \
--to=maillist-musl@barfooze.de \
--cc=felix.janda@posteo.de \
--cc=idunham@lavabit.com \
--cc=mtk.manpages@gmail.com \
--cc=musl@lists.openwall.com \
--cc=rob@landley.net \
/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.vuxu.org/mirror/musl/
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).