Bug? in bash setlocale implementation

2012-02-21 Thread John Kearney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' - -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' - -DCONF_VE

Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.

2012-02-21 Thread Eric Blake
On 02/20/2012 07:42 PM, Chet Ramey wrote: > On 2/18/12 5:39 AM, John Kearney wrote: > >> Bash Version: 4.2 >> Patch Level: 10 >> Release Status: release >> >> Description: >> Current u32toutf8 only encode values below 0x correctly. >> wchar_t can be ambiguous size better in my opi

Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.

2012-02-21 Thread John Kearney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/21/2012 01:34 PM, Eric Blake wrote: > On 02/20/2012 07:42 PM, Chet Ramey wrote: >> On 2/18/12 5:39 AM, John Kearney wrote: >> >>> Bash Version: 4.2 Patch Level: 10 Release Status: release >>> >>> Description: Current u32toutf8 only encode value

Two minor correction to the manual of bash

2012-02-21 Thread Bjarni Ingi Gislason
Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba

Re: excess braces ignored: bug or feature ?

2012-02-21 Thread Chet Ramey
On 2/20/12 2:32 AM, Dan Douglas wrote: >>> That one really is ignored. No variable named xxx... is actually set. >> >> I assume you mean the first one. It doesn't matter whether or not the >> variable is set as a side effect of the redirection -- it's in a >> subshell and disappears. >> >> Chet >

Re: excess braces ignored: bug or feature ?

2012-02-21 Thread Chet Ramey
On 2/20/12 4:17 AM, Dan Douglas wrote: > On Sunday, February 19, 2012 04:25:46 PM Chet Ramey wrote: > >> I assume you mean the first one. It doesn't matter whether or not the >> variable is set as a side effect of the redirection -- it's in a >> subshell and disappears. >> >> Chet > > Forgot to

Re: Fix u32toutf8 so it encodes values > 0xFFFF correctly.

2012-02-21 Thread Chet Ramey
On 2/21/12 8:43 AM, John Kearney wrote: > signed / unsigend isn't really the problem anyway utf-8 only encodes > up to 0x7fff and utf-16 only encodes up to 0x0010 . > > In my latest version I've pretty much removed all reference to wchar_t > in unicode.c. It was unnecessary. It's useful

Initial test code for \U

2012-02-21 Thread John Kearney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Initial code for testing \u functionality. basically uses arrays that look like this jp_JP_SHIFT_JIS=( #Unicode="expected bmstring" [0x0001]=$'\x01' # START OF HEADING [0x0002]=$'\x02' # START OF TEXT ... ) TestCodePage ja_JP.SHIFT_JIS jp_JP_S

Re: Bug? in bash setlocale implementation

2012-02-21 Thread Chet Ramey
On 2/21/12 3:51 AM, John Kearney wrote: > Bash Version: 4.2 > Patch Level: 10 > Release Status: release > > Description: > Basically if setting the locale fails variable should not be changed. I disagree. The assignment was performed correctly and as the user specified. The fact that a side

Here is a diff of all the changed to the unicode

2012-02-21 Thread John Kearney
Here is a diff of all the changed to the unicode This seems to work ok for me. but still needs further testing. My major goal was to make the code easier to follow and clearer. but also generally fixed and improved it. Added warning message ./bash -c 'printf "string 1\\U8fffStromg 2"' ./b

Re: Bug? in bash setlocale implementation

2012-02-21 Thread John Kearney
On 02/22/2012 01:52 AM, Chet Ramey wrote: > On 2/21/12 3:51 AM, John Kearney wrote: > >> Bash Version: 4.2 Patch Level: 10 Release Status: release >> >> Description: Basically if setting the locale fails variable >> should not be changed. > > I disagree. The assignment was performed correctly a

printf "%q" "~" not escaped?

2012-02-21 Thread John Kearney
Bash Version: 4.2 Patch Level: 10 Release Status: release Description: printf "%q" "~" not escaped? which means that this eval echo $(printf "%q" "~") results in your home path not a ~ unlike eval echo $(printf "%q" "*") as far as I can see its the only character that isn't treated as I expected