Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-12 Thread Steve Mynott via RT
I'm not sure. Probably your idea of warning about detected encoding is better.

S
On Thu, 12 Jul 2018 at 09:58, Kamil Kułaga via RT
 wrote:
>
> Will it work fine for utf-16 users?
> On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
>  wrote:
> >
> > Maybe the Windows port of rakudo should set this automatically on startup?
> > On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
> >  wrote:
> > >
> > > I found resolution. It looks like it is problem windows locale issue than 
> > > perl itself.
> > >
> > > Running command
> > >
> > > chcp utf8
> > >
> > > Makes work just fine. Default is 852. I'm very supprised because I use 
> > > unicode encoding all the the time and never had such issue. For me it 
> > > would be better to detect if codepage is set to 852 and warn user that 
> > > perl6 may not work well. Shall we close it or leave defect for future 
> > > improvement?
> >
> >
> >
> > --
> > Steve Mynott 
> > cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
> >
>
>
> --
> Pozdrawiam
>
> Kamil Kułaga



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-12 Thread Steve Mynott
I'm not sure. Probably your idea of warning about detected encoding is better.

S
On Thu, 12 Jul 2018 at 09:58, Kamil Kułaga via RT
 wrote:
>
> Will it work fine for utf-16 users?
> On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
>  wrote:
> >
> > Maybe the Windows port of rakudo should set this automatically on startup?
> > On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
> >  wrote:
> > >
> > > I found resolution. It looks like it is problem windows locale issue than 
> > > perl itself.
> > >
> > > Running command
> > >
> > > chcp utf8
> > >
> > > Makes work just fine. Default is 852. I'm very supprised because I use 
> > > unicode encoding all the the time and never had such issue. For me it 
> > > would be better to detect if codepage is set to 852 and warn user that 
> > > perl6 may not work well. Shall we close it or leave defect for future 
> > > improvement?
> >
> >
> >
> > --
> > Steve Mynott 
> > cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
> >
>
>
> --
> Pozdrawiam
>
> Kamil Kułaga



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-12 Thread Kamil Kułaga via RT
Will it work fine for utf-16 users?
On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
 wrote:
>
> Maybe the Windows port of rakudo should set this automatically on startup?
> On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
>  wrote:
> >
> > I found resolution. It looks like it is problem windows locale issue than 
> > perl itself.
> >
> > Running command
> >
> > chcp utf8
> >
> > Makes work just fine. Default is 852. I'm very supprised because I use 
> > unicode encoding all the the time and never had such issue. For me it would 
> > be better to detect if codepage is set to 852 and warn user that perl6 may 
> > not work well. Shall we close it or leave defect for future improvement?
>
>
>
> --
> Steve Mynott 
> cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
>


-- 
Pozdrawiam

Kamil Kułaga


Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-12 Thread Kamil Kułaga
Will it work fine for utf-16 users?
On Wed, Jul 11, 2018 at 11:16 AM Steve Mynott via RT
 wrote:
>
> Maybe the Windows port of rakudo should set this automatically on startup?
> On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
>  wrote:
> >
> > I found resolution. It looks like it is problem windows locale issue than 
> > perl itself.
> >
> > Running command
> >
> > chcp utf8
> >
> > Makes work just fine. Default is 852. I'm very supprised because I use 
> > unicode encoding all the the time and never had such issue. For me it would 
> > be better to detect if codepage is set to 852 and warn user that perl6 may 
> > not work well. Shall we close it or leave defect for future improvement?
>
>
>
> --
> Steve Mynott 
> cv25519/ECF8B611205B447E091246AF959E3D6197190DD5
>


-- 
Pozdrawiam

Kamil Kułaga


Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-11 Thread Steve Mynott via RT
Maybe the Windows port of rakudo should set this automatically on startup?
On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
 wrote:
>
> I found resolution. It looks like it is problem windows locale issue than 
> perl itself.
>
> Running command
>
> chcp utf8
>
> Makes work just fine. Default is 852. I'm very supprised because I use 
> unicode encoding all the the time and never had such issue. For me it would 
> be better to detect if codepage is set to 852 and warn user that perl6 may 
> not work well. Shall we close it or leave defect for future improvement?



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


Re: [perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-11 Thread Steve Mynott
Maybe the Windows port of rakudo should set this automatically on startup?
On Wed, 11 Jul 2018 at 10:08, Kamil Kułaga via RT
 wrote:
>
> I found resolution. It looks like it is problem windows locale issue than 
> perl itself.
>
> Running command
>
> chcp utf8
>
> Makes work just fine. Default is 852. I'm very supprised because I use 
> unicode encoding all the the time and never had such issue. For me it would 
> be better to detect if codepage is set to 852 and warn user that perl6 may 
> not work well. Shall we close it or leave defect for future improvement?



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


[perl #128154] [BUG] Cannot use qqx in rakudo star on windows7

2018-07-11 Thread Kamil Kułaga via RT
I found resolution. It looks like it is problem windows locale issue than perl 
itself.

Running command

chcp utf8

Makes work just fine. Default is 852. I'm very supprised because I use unicode 
encoding all the the time and never had such issue. For me it would be better 
to detect if codepage is set to 852 and warn user that perl6 may not work well. 
Shall we close it or leave defect for future improvement?