From: mwoehlke <mwoehlke@tibco.com>
To: cygwin-talk@cygwin.com
Cc: newlib@sources.redhat.com
Subject: Re: What's wrong with *roff, anyway? (Was: Um... what format are Cygwin manpages?)
Date: Fri, 11 Aug 2006 15:30:00 -0000 [thread overview]
Message-ID: <ebi7p0$3bv$1@sea.gmane.org> (raw)
In-Reply-To: <20060811083354.GA4521@calimero.vinschen.de>
(Time to take this to the newlib list...)
Corinna Vinschen wrote:
> On Aug 10 17:25, mwoehlke wrote:
>> Christopher Faylor wrote:
>>> Actually, on some further digging it is, most likely, in sprintf.c
>>> So, no texinfo editing required.
>> Hey! Now I found that /all//by//myself/, thank you! ;-)
>> (See, I told you I'd keep looking.)
>>
>> And... now I understand why the ->nroff converter works so poorly. Eek.
>> Do you really do the indentation and line length *by hand*, or am I
>> missing something?
>
> Hey, you could just sit down and generate a patch which pulls all
> documentation out of the source files, changes it to texinfo format and
> integrates them in a structured way into the newlib/doc subdirectory.
> Then you just have to add the Makefiles changes so that generation and
> installation as man pages, info pages, html pages, tex documentation,
> pdf files... is possible. I'm *sure* Jeff would like the idea and
> happily take the patch.
Well, the *real* question was 'will the newlib folks tolerate their doc
being in a more useful but harder-to-understand format?'. It sounds like
you're fairly convinced the answer is "yes"... so maybe I'll keep this
on my list after all.
Although I must be honest and say I'm more familiar with nroff then
LaTeX; I'm tempted to make an nroff->LaTeX convertor. ;-) But probably I
will go with SGML because I know there are SGML->nroff/LaTeX converters.
And yes, if *I* start tinkering I will probably set things up so the
makefile will generate at minimum info doc and man pages. I'll leave
PDF, HTML, etc to someone else, but my understanding is that PDF is
easily generated from either LaTeX or nroff, and HTML is easily
generated from nroff (*I* don't know about LaTeX, but that doesn't mean
it can't be done). And of course SGML->HTML is probably easy, too. :-)
Anyway, thanks for the pointers! ...And I hope you're right about Jeff. ;-)
--
Matthew
"We're all mad here. I'm mad. You're mad... You must be, or you wouldn't
have come here." -- The Cheshire Cat
prev parent reply other threads:[~2006-08-11 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ebd0om$gjh$1@sea.gmane.org>
[not found] ` <cb51e2e0608092159t14175e52jeb656ffd2cc123a1@mail.gmail.com>
[not found] ` <ebfiu4$4pn$1@sea.gmane.org>
[not found] ` <cb51e2e0608101108g41c88386wd7219aaead8ca396@mail.gmail.com>
[not found] ` <ebg4e5$39g$1@sea.gmane.org>
[not found] ` <20060810202721.GC935@trixie.casa.cgf.cx>
2006-08-10 20:45 ` Um... what format are Cygwin manpages? mwoehlke
2006-08-10 20:54 ` Christopher Faylor
2006-08-10 21:21 ` mwoehlke
2006-08-10 21:31 ` Christopher Faylor
2006-08-10 22:26 ` What's wrong with *roff, anyway? (Was: Um... what format are Cygwin manpages?) mwoehlke
2006-08-11 8:34 ` Corinna Vinschen
2006-08-11 15:30 ` mwoehlke [this message]
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='ebi7p0$3bv$1@sea.gmane.org' \
--to=mwoehlke@tibco.com \
--cc=cygwin-talk@cygwin.com \
--cc=newlib@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).