X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: mwoehlke <mwoehlke AT tibco DOT com>
Subject:  Re: Um... what format are Cygwin manpages?
Date:  Thu, 10 Aug 2006 15:20:21 -0500
Lines: 36
Message-ID: <ebg4e5$39g$1@sea.gmane.org>
References:  <ebd0om$gjh$1 AT sea DOT gmane DOT org> 	 <cb51e2e0608092159t14175e52jeb656ffd2cc123a1 AT mail DOT gmail DOT com> 	 <ebfiu4$4pn$1 AT sea DOT gmane DOT org> <cb51e2e0608101108g41c88386wd7219aaead8ca396 AT mail DOT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding:  7bit
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060719 Thunderbird/1.5.0.5 Mnenhy/0.7.4.0
In-Reply-To: <cb51e2e0608101108g41c88386wd7219aaead8ca396@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Joshua Daniel Franklin wrote:
> On 8/10/06, mwoehlke wrote:
>> Joshua Daniel Franklin wrote:
>> > Yes, it's sort-of my fault. I just have a Perl script that chunks the
>> > newlib libc.info files into faux man pages.
>>
>> Ah, ok, makes sense. Too bad newlib doesn't have proper manpages, in
>> that case. Although am I understanding that newlib itself doesn't have
>> *any* manpages, meaning a: I need to be fixing their INFO, and b: any
>> manpages should be sent this way after all?
> 
> Well, I'd be for fixing the newlib files rather than replacing them. The 
> issue with replacing them with our own custom versions or with Linux ones
> is that the documentation no longer comes from the actual upstream libc
> (or worse-- in the case of Linux it comes from a possibly incompatible
> *different* upstream libc).

...which is why we're not replacing it with the Linux one. :-) I took 
the Linux one and *edited* it until it seemed to match the actual 
observed-and-tested behavior of Cygwin's newlib. Along the way I 
discovered that newlib is not C99-conformant (see earlier posts).

Anyway, if it turns out I have to patch an info file, then I guess I'm 
stuck doing that. Assuming anyone on newlib pays attention to me. So 
far, zilch.

> If you'd like to add better *roff formatting to the perl script, it's
> in the cygwin-doc src package. A warning, though, it's a mess.

Heh, maybe I'll take a crack, but that's something a lot more 
complicated... there is really not a good LaTeX->roff convertor out 
there? (Or maybe newlib has just-as-poorly-formatted LaTeX... ;-))

-- 
Matthew
vIMprove your life! Now on version 7!


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/