In our previous episode, Michael Van Canneyt said:
> I honestly don't understand this argument: in 99,99% of all cases, the code
> will just
> work if you use RawByteString, since everything will be in the codepage of
> the environment anyway ?
Well, we already convert to target encoding on windo
On Wed, 11 May 2016, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
I don't like that. The 3.x idea is to get rid of manual conversions and
hack-and-convert-it-as-you-go encoding management, not just rebadge the old
practices to rawbytestring.
You may not like
In our previous episode, Michael Van Canneyt said:
> >
> > I don't like that. The 3.x idea is to get rid of manual conversions and
> > hack-and-convert-it-as-you-go encoding management, not just rebadge the old
> > practices to rawbytestring.
>
> You may not like it, but there is simply no other c
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
And in the case it makes an assumption of the code page, regardl
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
And in the case it makes an assumption of the code page, regardless of
environment variables ?
(don't say that
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
And in the case it makes an assumption of the code page, regardless of
environment variables ?
(don't say that doesn't happen. It does, I know a programmer
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Marco van de Voort wrote:
I don't like that. The 3.x idea is to get rid of manual convers
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Marco van de Voort wrote:
I don't like that. The 3.x idea is to get rid of manual conversions and
hack-and-convert-it-as-you-go encod
On Wed, 11 May 2016, Jonas Maebe wrote:
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Marco van de Voort wrote:
I don't like that. The 3.x idea is to get rid of manual conversions and
hack-and-convert-it-as-you-go encoding management, not just rebadge the
old
pract
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Marco van de Voort wrote:
I don't like that. The 3.x idea is to get rid of manual conversions and
hack-and-convert-it-as-you-go encoding management, not just rebadge the old
practices to rawbytestring.
You may not like it,
On Wed, 11 May 2016, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
I'm not sure what you are suggesting as alternative. Saving the encoding at
startup, so it can be reused in cases like this, in case somebody change
defaultsystemcodepage?
Or using defaultsystem
In our previous episode, Michael Van Canneyt said:
> > I'm not sure what you are suggesting as alternative. Saving the encoding at
> > startup, so it can be reused in cases like this, in case somebody change
> > defaultsystemcodepage?
> >
> > Or using defaultsystemcodepage instead of filesystem enc
Michael Van Canneyt wrote on Wed, 11 May 2016:
On Wed, 11 May 2016, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
The filesystem encoding is fine to find the binary on Unix, but the
parameters you specify to that binary will be interpreted by that same
binary once it'
On Wed, 11 May 2016, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
It assumes for windows utf16, and for Unix filesystem encoding (e.g.
unix.pp:254).
If you have more info, please share.
The filesystem encoding is fine to find the binary on Unix, but the
parameters
In our previous episode, Jonas Maebe said:
> >
> > It assumes for windows utf16, and for Unix filesystem encoding (e.g.
> > unix.pp:254).
> >
> > If you have more info, please share.
>
> The filesystem encoding is fine to find the binary on Unix, but the
> parameters you specify to that binary w
15 matches
Mail list logo
