James Youngman [EMAIL PROTECTED] writes:
Any ideas/suggestions?
Does the following untested patch fix things? It attempts to mimic
what Bash does.
*** fnmatch.c Fri May 13 23:03:58 2005
--- /tmp/fnmatch.c Tue Jun 7 00:02:03 2005
*** fnmatch (const char *pattern, const char
On Tue, Jun 07, 2005 at 09:15:04AM -0400, Karl Berry wrote:
In the C locale, GNU programs should stick to plain ASCII for
quotation characters in messages to users: either 0x60 (`) for left
quotes and 0x27 (') for right quotes, or ' for both opening and
closing, or (0x22) for both opening
Hi James,
It might be worth pointing out that all valid ASCII files are valid
UTF-8 files, but not all valid Latin-1 files are valid UTF-8 files.
Thanks for the suggestion. I'm glad to know this myself (I thought it
was the case, but didn't know the specifics), but since rms does not
I believe that the standard should probably
suggest a preferred alternative.
Yeah, you're probably right. I was trying to avoid dissension I suspect
there are some GNU'ers who will hate the idea of using `), but it's
likely unavoidable :). Guess I'll try changing the first either to
Stepan Kasal wrote:
- We need to document also AS_LITERAL_IF and m4_fatal
(And you could also document m4_warning, when you are at it.)
I'll see about it after I get comments on the first round back.
- we have to document also the fact that AS_TR_SH AS_TR_CPP expand
to literal variable
Paul Eggert wrote:
Derek Price [EMAIL PROTECTED] writes:
What does this mean for Bruno's recent patch for stat lstat which
removed the SunOS 4.1.4 support in addition to some other fixes?
His patch made sense to me, but as far as I know nobody has taken the
time to integrate the
[EMAIL PROTECTED] (Karl Berry) writes:
@node Quote characters
I like that section. Is it possible to discuss how that relate to the
[EMAIL PROTECTED] stuff recommended by gettext to solve the similar problem?
Which method is preferable? Are they mutual exclusive, or should they
be used in
Hi Simon,
Thanks for the note.
Are they mutual exclusive, or should they
be used in combination? Those things aren't clear to me.
They aren't clear to me either, but I *think* they can be used in
combination. That is, if you use the gnulib quote module or equivalent,
then you could
Karl Berry wrote:
@node Quote characters
@section Quote characters
@cindex quote characters
In the C locale, GNU programs should stick to plain ASCII for
quotation characters in messages to users: either 0x60 (`) for left
quotes and 0x27 (') for right quotes, or ' for both opening and
This is misleading.
I know, but I'm not sure what to say. Just delete the sentence about
Latin1, maybe? I guess it's not really necessary.
To represent them, you need Unicode, i.e. the UTF-8 encoding.
Yes, but rms has explicitly rejected (in previous email with me) the
idea of
Hi,
On Tue, Jun 07, 2005 at 10:19:47AM -0400, Derek Price wrote:
- we have to document also the fact that AS_TR_SH AS_TR_CPP expand
to literal variable (symbol) name, if their argument is a literal
I didn't think this was important from the user's perspective.
In the patch I proposed, I
Karl Berry wrote:
Yes, but rms has explicitly rejected (in previous email with me) the
idea of recommending the use of UTF-8 in any context whatsoever. Sigh.
Sigh. What you wrote there:
If you need to use non-ASCII characters, for example to represent
names of contributors, you should
Hi Karl,
Here's a nit:
[EMAIL PROTECTED] (Karl Berry) wrote:
...
The @uref{http://www.gnu.org/software/gnulib/, Gnulib} @code{quote}
and @code{quotearg} modules provide a reasonably straightforward way
support locale-specific quote characters, as well as taking care of
s/support/to support/
to educated people it recommends Unicode, without mentioning it explicitly.
True. I do not know how else to write it. (I'm also not sure rms will
go for it at all.)
That depends on your mailer. Is it a package in Emacs, or is it 'pine'
without Bernhard Kaindl's patches?
My
14 matches
Mail list logo
