[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lmi] What encoding does wx_test console output use?
From: |
Greg Chicares |
Subject: |
[lmi] What encoding does wx_test console output use? |
Date: |
Sat, 8 Sep 2018 09:57:24 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 |
$wine ./wx_test --ash_nazg --data_path=/opt/lmi/data --pyx=only_new_pdf
>../src/lmi/wx_test_output
$file -bi wx_test_output
application/octet-stream; charset=binary
I'd like to filter this, removing expected lines and leaving only
unexpected--much as 'nychthemeral_test.sh' does for other tests
with its '_clutter' sed scripts. I suppose
iconv -t UTF-8 -f SOME_ENCODING wx_test_output
might work, for some value (what?) of SOME_ENCODING. Alternatively,
should I try to call
fwide(stdout, -1);
fwide(stderr, -1);
somewhere early on, or is that doomed because...
https://groups.google.com/forum/#!original/wx-users/rPk1bKmP2sI/HFIQdxmDNNcJ
| This is because in C99 a stream can be either in narrow or wide mode (so
| called orientation), see fwide(3). And the first call to narrow or wide
| character output function sets the orientation and disables the output from
| the functions using the other orientation.
|
| I had absolutely never been able to understand why is it done this way but
| clearly this is not going to change. And the only thing we could do to
| avoid it would be to stop using wide char output functions completely,
| which doesn't look like a great idea.
- [lmi] What encoding does wx_test console output use?,
Greg Chicares <=