[Stig Bjørlykke <stig@xxxxxxxxxxxxx>]

On Tue, Jun 28, 2011 at 7:01 PM, Guy Harris <guy@xxxxxxxxxxxx> wrote:
> In any case, that means that using strerror() is probably not going to be sufficient to fix the problem.  What we might want to do is use UTF-8 everywhere we can, and, for non-GUI output, convert to the appropriate character encoding - whatever that might be - at the last minute.

Ok, what about trying to convert back to locale when output error
messages from tshark?
Something like the attached patch, maybe?


-- 
Stig Bjørlykke

Attachment: tshark-print-locale.patch
Description: Binary data