FAQ Proposed Updates Summary and Preview Diff

Corinna Vinschen corinna-cygwin@cygwin.com
Fri Jul 17 11:17:18 GMT 2020

Hi Brian,

On Jul 16 21:35, Brian Inglis wrote:
> Just want to get feedback on how these FAQ changes should be packaged as patches
> (separate, series, single) and whether some of the changes should not be applied
> at all.
> Summary
> General:
> change setup references to use the Cygwin Setup program;
> change Win32 references to Windows;

Please, no.  At least not where Win32 refers to the API.  While this is
called "Windows API" these days, the word Windows alone doesn't really
cut it.  At leats use "Windows API" then, or IMHO even better, use the
informal "WinAPI" abbreviation.

> reword net release or distribution references;

Uhm... example?  I'm not sure what you mean here.

> emphasize 64-bit Cygwin and setup-x86_64 over 32-bit;
> change see <ulink/> to place links around available wording;
> change <literal> for <filename> or <command> where appropriate;
> change bash .{ext1,ext2} usage to .ext1/.ext2;

Using comma separated lists within curly braces is the offical
shell way to express alternatives:

  $ echo a.{b,c}
  a.b a.c

Please keep them as is.

> trim trailing spaces highlighted by git diff.


Corinna Vinschen
Cygwin Maintainer

More information about the Cygwin-patches mailing list