>>> now UTF-8 is set but MB_CUR_MAX is 1
That sounds bad.
On 06/01/2012 02:40 PM, Stephen J. Butler wrote:
> on darwin we're stuck with the compiled in table that defines "*"
> as "UTF-8". Yet, that's not true on any other platform.
Currently the code has this comment:
/* To avoid the tro
On Fri, Jun 1, 2012 at 4:09 PM, Pádraig Brady wrote:
> So this is the third time this change has been proposed:
>
> If you following the previous one:
> http://lists.gnu.org/archive/html/bug-gnulib/2012-03/threads.html#00104
> it will refer to Bruno's argument for not changing this:
> http://lists
On 06/01/2012 08:52 PM, Paolo Bonzini wrote:
> Here is a report from a GNU sed user.
>
> Paolo
>
>> SETUP:
>> $ sw_vers
>> ProductName: Mac OS X
>> ProductVersion: 10.7.4
>> BuildVersion:11E53
>>
>> $ ~/gnu/bin/sed --version
>> GNU sed version 4.2.1
>>
>> PROBLEM: With UTF-8 input, b
Here is a report from a GNU sed user.
Paolo
> SETUP:
> $ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.7.4
> BuildVersion: 11E53
>
> $ ~/gnu/bin/sed --version
> GNU sed version 4.2.1
>
> PROBLEM: With UTF-8 input, but LANG and LC_ALL set to C, sed regular
> expressions break on mu
