Re: uuencode: multi-bytes char in remote file name contains bytes >0x80

2011-07-04 Thread Eli Zaretskii
> From: Bruno Haible > Date: Mon, 4 Jul 2011 22:58:43 +0200 > Cc: bug-gnulib@gnu.org, > bug-gnu-ut...@gnu.org, > q24...@gmail.com, > bk...@gnu.org > > > Doesn't the same problem exist with the file's data itself? > > No, there is normally no problem with the contents of the files, because use

Re: good place for blogging on C/POSIX programming?

2011-07-04 Thread Karl Berry
Also: https://savannah.gnu.org/projects/gnu-c-manual/ (not the same Yes, although that's intended to be a reference for the C language only, not the C library, let alone POSIX. So I didn't think it would be appropriate for extensive portability discussions like Bruno's. k

Re: good place for blogging on C/POSIX programming?

2011-07-04 Thread James Youngman
On Sun, Jul 3, 2011 at 2:31 PM, Bruno Haible wrote: > There are currently 3 pieces of documentation that deal with C programming: >  - The glibc manual, >  - The Autoconf manual's section "Portable C and C++ Programming", >  - The gnulib manual. Also: https://savannah.gnu.org/projects/gnu-c-manu

Re: [PATCH] maint: indent with spaces, not TABs, and add a rule to check this

2011-07-04 Thread Bruno Haible
Hi Jim, > m4/po.m4 > *** indent with spaces, not TABs; > ... > Bruno, I didn't change po.m4, since it's from gettext. > If you plan to fix it, I'll leave the failure for now. > Otherwise, let me know and I'll exempt that file, too. The leading tabs in m4/po.m4 are not indentation, but rat

Re: uuencode: multi-bytes char in remote file name contains bytes >0x80

2011-07-04 Thread Bruno Haible
Eli, > > An obvious problem with the patch is that it considers a file name to be a > > byte sequence. But different users may work in different locales, with > > different encodings. And users want to see the original filenames. Users don't want to see mojibake, that is, a mix of garbled charact

[PATCH] maint: indent with spaces, not TABs, and add a rule to check this

2011-07-04 Thread Jim Meyering
With the change below, "make check" prints this: (the cppi lines are legacy; only the m4/po.m4 warning is new) m4/po.m4 *** indent with spaces, not TABs; make: *** [sc_prohibit_leading_TABs] Error 1 make: *** Waiting for unfinished jobs cppi: lib/stdio-read.c: line 107: not

Re: uuencode: multi-bytes char in remote file name contains bytes >0x80

2011-07-04 Thread Eli Zaretskii
> From: Bruno Haible > Date: Sun, 3 Jul 2011 22:43:55 +0200 > Cc: bug-gnu-ut...@gnu.org, 張叁 , > Bruce Korb > > Referring to > : > > An obvious problem with the patch is that it considers a file name to be a > byte sequ

Re: [PATCH]: pselect: new module

2011-07-04 Thread Bruno Haible
Paul, I wrote: > (which is probably why you didn't notice the missing > 'test $HAVE_PSELECT = 0'). This comment was not fair. There was no link error. I apologize. Bruno -- In memoriam Yonatan Netanyahu