Revert "Update the tests (ISO-8859-1 => windows-1252)"

Revert "Update the tests (ISO-8859-1 => windows-1252)"

This reverts commit 9c188b20fbb4d4c2006ab1a611ed8a9b971e7cee.

Broke several browser_tests which depended on the previous behavior:
BrowserEncodingTest.TestOverrideEncoding
EncodingAliases/BrowserEncodingTest.TestEncodingAliasMapping/16
BrowserEncodingTest.TestEncodingAutoDetect
EncodingAliases/BrowserEncodingTest.TestEncodingAliasMapping/3

E.g.
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=BrowserEncodingTest.TestOverrideEncoding&testType=browser_tests

TBR=jshin@chromium.org
BUG=412053
NOTRY=true

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=183822

[cbiesinger, 2014-10-16 15:47:43]

Committed patchset #1 (id:1) manually as 183822 (presubmit successful).

[jungshik at Google, 2014-10-16 16:16:18]

On 2014/10/16 15:47:43, cbiesinger wrote:
> Committed patchset #1 (id:1) manually as 183822 (presubmit successful).

Sorry that I forgot to note that they're expected to fail. The CL you just
reverted and
https://codereview.chromium.org/649413002/ have to go hand in hand. 
I'll mark those tests as failing for now on the Cr-side. Then, I'll reland the
reverted CL followed by
the Chromium CL (mentioned above) that will also re-enable those tests.

[cbiesinger, 2014-10-16 16:27:12]

Jungshik, we haven't had a blink roll in the last 10 hours because these tests
were failing. It is not acceptable to burn the tree for so long, *especially*
when you knew this was going to happen.

[jungshik at Google, 2014-10-16 17:32:46]

On 2014/10/16 16:27:12, cbiesinger wrote:
> Jungshik, we haven't had a blink roll in the last 10 hours because these tests
> were failing. It is not acceptable to burn the tree for so long, *especially*
> when you knew this was going to happen.

My apology. When I landed the reverted Blink CL last night, I overlooked it
because my tree had both of them. Unfortunately, I did not realize that it'd
break Chrome's tests until this morning and rushed to fix only to find that the
CL had already been reverted. Anyway,I should have been more careful.

[jungshik at Google, 2014-10-17 06:23:06]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/648163003/ by jshin@chromium.org.

The reason for reverting is: The failing browser tests (Chromium) were
temporarily disabled (or made robust against the difference introduced by this
Blink CL) in the following Cr CL (that got landed) :

https://codereview.chromium.org/643993004/

.