On Wed, Oct 24, 2018 at 05:03:58PM +0200, Josef Reidinger wrote:
I want to inform you about change in
yast2-ruby-bindings affecting SLE12 SP4, SLE15 GA and SLE15 SP1, respective related Leap
What changes? It overwrites default ruby mechanism for setting default external/internal
encoding. Now already some parts of ruby-bindings expect UTF-8 strings and in some
scenarios like LC_ALL=C it can be set to ASCII. Result is that UTF-8 string cause
exception. So now with that change it always expect UTF-8 as encoding of external IO.
So do we have to say now that YaST only works on UTF-8 systems?
That would be OK for me and is likely at many places the case
Arvin Schnell, <aschnell(a)suse.com>
Senior Software Engineer, Research & Development
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org