X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 9 Aug 2006 21:59:20 -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/9/06, mwoehlke wrote: > I thought I'd have a crack at fixing the manpage for printf(3) (see > http://cygwin.com/ml/cygwin/2006-08/msg00288.html), but when I opened > it, I was a bit shocked to discover that it is only *MARGINALLY* in > troff format. I do note that other manpages seem more "normal" (man1 > pages, for instance)... So, is this just "how the C lib manpages are"? Yes, it's sort-of my fault. I just have a perl script that chunks the newlib libc.info files into faux man pages. Be careful with Linux man pages, some are licenced from the Open Group. If so the package should come with a copyright file like this: http://packages.debian.org/changelogs/pool/non-free/m/manpages-posix/manpages-posix_1.67-3/manpages-posix.copyright Unfortunately we are not allowed to redistribute those, unless you'd like to do the legwork to get permission to do so. :) Also I just posted for upload a new cygwin-doc package before I read this thread, so there would be more of a delay. -- 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/