patch fixed for Jenkin Client Console output encoding(charset) issue

[qxo]

No description provided.

[cloudbees-pull-request-builder]

core » jenkins_main_trunk #865 SUCCESS
This pull request looks good

[qxo]

https://issues.jenkins-ci.org/browse/JENKINS-17881

This patch solve client-server encoding convert issue:

1. server(master node) file.encoding=UTF-8 and jenkin client jvm file.encoding=GBK
2. or jenkins slave file.encoding=GBK and jenkins client jvm file.encoding=UTF-8

test shell script: echo "测试"

[qxo]

https://issues.jenkins-ci.org/browse/JENKINS-17881

This patch solve client-server encoding convert issue:

1. server(master node) file.encoding=UTF-8 and jenkin client jvm file.encoding=GBK
2. or jenkins slave file.encoding=GBK and jenkins client jvm file.encoding=UTF-8

test shell script: echo "测试"

[kutzi]

Is it possible to write a unit test for the issue?

[qxo]

Yes

[qxo]

Where? for the unit test,Can you give a example?

2013/5/7 Christoph Kutzinski notifications@github.com

Is it possible to write a unit test for the issue?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/775#issuecomment-17538725
.

[cloudbees-pull-request-builder]

core » jenkins_main_trunk #868 SUCCESS
This pull request looks good

[cloudbees-pull-request-builder]

core » jenkins_main_trunk #869 SUCCESS
This pull request looks good

[jglick]

Bits of the patch might be usable but I think this pull request is too garbled to ever be accepted.