You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Jack O'Sullivan (Jira)" <ji...@apache.org> on 2020/02/27 11:46:00 UTC
[jira] [Created] (EXEC-112) Extended UTF-8 characters are not
properly handled by the LogOutputStream
Jack O'Sullivan created EXEC-112:
------------------------------------
Summary: Extended UTF-8 characters are not properly handled by the LogOutputStream
Key: EXEC-112
URL: https://issues.apache.org/jira/browse/EXEC-112
Project: Commons Exec
Issue Type: Bug
Environment: This will affect any system where the output of the tool is not in the default character set for the system, but has been seen on Windows where the tool produces UTF-8 output.
Reporter: Jack O'Sullivan
In the processBuffer method of LogOutputStream, "buffer.toString()" is called, before passing the result to processLine. This relies on the default encoding of the system to correctly handle the output.
On Windows, if the CL tool output contains UTF-8 characters, these are mishandled by the toString method of the buffer.
Because the buffer is a private member variable, even if you extend this class, the only way to enforce correct character set handling is to use reflection to access the buffer in an over-ride of the processBuffer method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)