delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <48B0EDE1.80804@users.sourceforge.net> |
Date: | Sun, 24 Aug 2008 00:13:05 -0500 |
From: | "Yaakov (Cygwin Ports)" <yselkowitz AT users DOT sourceforge DOT net> |
User-Agent: | Thunderbird 2.0.0.16 (Windows/20080708) |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: man: cygwin 1.7.0 and special filename chars |
References: | <48AF247F DOT 2050300 AT users DOT sourceforge DOT net> <48AF79A9 DOT AE50661A AT dessent DOT net> <48B0E0FF DOT 1090508 AT users DOT sourceforge DOT net> <48B0E986 DOT 33F5D61 AT dessent DOT net> |
In-Reply-To: | <48B0E986.33F5D61@dessent.net> |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.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 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Brian Dessent wrote: > Oh. I see. That's unfortunate. But I don't understand something: I'm > looking at the documentation for ExtUtils::MM_Cygwin which claims to > contain platform-specific overrides for ExtUtils::MakeMaker, one of > which is replace_manpage_separator that is documented as: > > replaces strings '::' with '.' in MAN*POD man page names > > It seems like this issue has already been considered and solved > upstream. Why does this not kick in? Because gtk2-perl (namely Glib::MakeHelper) uses a custom process for building documentation: first, the PODs are generated from the XS, then the manpages are generated from those PODs. These rules override the ones generally provided by EU:MM. > Well yes, case-sensitivity also has similar set of restrictions. But > the support for illegal chars is implemented by mapping them into a > Unicode private use area. FAT is codepage-based and doesn't support > Unicode so I don't see how this could work. The 1.7 UG mentions no such limitation by special chars, and a bit of experimenting with my FAT-formatted USB stick seems to work. Of course, 1.5 chokes on them, but even Windows Explorer saw the file and was able to delete it. Am I missing something here? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiw7eEACgkQpiWmPGlmQSMEYgCgsrAyzhQc+c4VzIMVdEx7hAzD BcYAoIhJwzFiODmGHvJbY1UzG/8B9zIJ =LIUo -----END PGP SIGNATURE----- -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |