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 23:15:52 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.3.0

On 2016-10-20 22:47, Vadim Zeitlin wrote:
> On Thu, 20 Oct 2016 22:34:23 +0000 Greg Chicares <address@hidden> wrote:
> 
> GC> On 2016-10-20 19:55, Vadim Zeitlin wrote:
> GC> [...]
> GC> >  We could get rid of all of them and use std::cout for output. This 
> would
> GC> > require relatively many changes, but is quite straightforward, so, as 
> much
> GC> > as I dislike it, this is probably the best solution.

^^^ what we want

> GC> I assume you can change the group-quote wxString stuff much more easily
> GC> than I can, so would you please make this change from wcout to cout?

^^^ inaccurate, misleading paraphrasis

>  Sorry, I'm a bit confused: what does this have to do with group quotes? I
> thought the problem was only in the GUI tests, is there something else/more
> to it?

You're right. If (contrary to fact) we wanted to build wx with --utf-whatever,
then we'd need to modify the switch on wxString[n] in the group quote code.
However, in reality we want to change from std::wcout to std::cout, right?
But now I'm confused about that, too, because grepping for 'wcout' finds
nothing--maybe 'wcout' is implicitly used by wxPuts(). I'm having an acute
sinus attack and can't focus on anything else, so please ignore whatever I
say--you know the right thing to do.




reply via email to

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