Re: an introduction to gnulib

[Bruno Haible]

Karl Berry wrote:
> I fixed a few Texinfo niglets.

ChangeLog entry? Diffs to this mailing list?

These were a little more than Texinfo niglets:

> @@ -144,18 +146,18 @@
>  @subsection Enhancements of ISO C or POSIX functions
>  
>  These are sometimes POSIX functions with GNU extensions also found in
> -glibc -- examples: @samp{getopt}, @samp{fnmatch} --, and often new APIs
> --- for example, for all functions that allocate memory in one way or the
> -other, we have variants which also include the error checking against the
> -out-of-memory condition.
> +glibc--examples: @samp{getopt}, @samp{fnmatch}---and often new
> +APIs---for example, for all functions that allocate memory in one way
> +or the other, we have variants which also include the error checking
> +against the out-of-memory condition.
 
I don't like the omission of spaces here. It looks like a single word
'glibc--examples' and a single word 'APIs---for'. I add back these spaces.

> -it works on Unix and Windows
> +it works on GNU/Unix and Windows

Now this is ridiculous. Do you consider a Solaris or a Tru64 system a
"GNU/" system? This is not even correct if you buy into RMS' arguments,
see http://www.gnu.org/gnu/gnu-linux-faq.html#why

If you consider it important to emphasize that "GNU is not Unix", then
it'd be more logical to write "Unix, GNU and Windows" (listed in the order
of historical appearance: Unix around 1980, GNU around 1986, Windows around
1995).

Bruno