lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] UTF-16 output from automated GUI test?


From: Greg Chicares
Subject: Re: [lmi] UTF-16 output from automated GUI test?
Date: Thu, 20 Oct 2016 22:30:21 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.3.0

On 2016-10-20 19:06, Greg Chicares wrote:
[...]
> 2) Don't revert. Whenever we would do:
>      ./wx_test.exe --data_path=/opt/lmi/data >eraseme 2>&1
>    instead do this:
>      ./wx_test.exe --data_path=/opt/lmi/data 2>&1 |tr --delete '\r' >eraseme

Incorrect. "Don't revert" means UTF-16 output [but see below]
with LF (not CRLF) delimiters, so "tr --delete '\r'" would fix
the wrong problem. Instead, we just want get rid of the NULs,
thus:
  ./wx_test.exe --ash_nazg --data_path=/opt/lmi/data 2>&1 |tr --delete '\000' 
>eraseme
until we can replace std::wcout with std::cout.

It might seem that we really ought to convert to UTF-8, thus:
  ./wx_test.exe --data_path=/opt/lmi/data 2>&1 |iconv -f UTF-16LE -t UTF-8 
>eraseme
That actually works in cygwin, but not in GNU/Linux. The
problem is that the output isn't actually UTF-16: it's a
mixture of UTF-16 and something else resembling ASCII. Maybe
that's just because 'wine' spits out some diagnostics that
aren't UTF-16.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]