On Wed, 24 Oct 2018 19:09:00 +0000 Arvin Schnell <[email protected]> wrote:
> On Wed, Oct 24, 2018 at 05:03:58PM +0200, Josef Reidinger wrote: > > > I want to inform you about change[1] in yast2-ruby-bindings affecting SLE12 > > SP4, SLE15 GA and SLE15 SP1, respective related Leap and TW. > > 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 > already. > > ciao Arvin > Yes, it is true. Unless someone have realiable way how to determine enconding of external strings, then using UTF-8 looks like sane default for me. At least I never see any report with non-UTF8 with recent products, but I see bunch of accidental C locale and UTF-8 file content. If there will be enough interest to make it work also in non UTF-8 env then we can make default encoding configurable. Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
