Handle weird characters in page names

[weinholt]

We have some Scheme procedures that contain a /, like call/cc, but / can't be used in filenames on Unix. So these pages are currently missing. We could use a convention like call_cc.

[lassik]

You mean man call/cc won't work even locally, since man will interpret that as a relative filename and won't search MANPATH (or will search MANPATH, but will look for a call subdirectory in each dir listed in MANPATH)?

[lassik]

Underscore is a reasonable placeholder for weird chars. I guess + * < = > ? ! can all be used on Unix. Windows forbids / ? < > : * which are relevant to Scheme. That probably means Cygwin and Msys can't use filenames with those characters either (does @johnwcowan know?)

[johnwcowan]

Cygwin can use any character: the Windows-forbidden ones are mapped into the Private Use Area, I believe. Msys is stuck with Windows rules. You omitted ? from the list of Windows-forbidden characters. There is also a list of forbidden names: a Windows pathname cannot contain a component CON, PRN, AUX, NUL, COMd, or LPTd, where d is a digit, or any of these followed by a period and any other characters, or ends in a period (the period is dropped).

…