X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 10 Aug 2006 11:08:23 -0700 From: "Joshua Daniel Franklin" To: cygwin@cygwin.com Subject: Re: Um... what format are Cygwin manpages? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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). 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. -- 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/